linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andries Brouwer <aebr@win.tue.nl>
To: Thomas Molina <tmolina@cox.net>
Cc: "Martin J. Bligh" <mbligh@aracnet.com>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [Bug 328] New: The computer seems to hang after the kernel has uncompressed and starts to boot.
Date: Sat, 8 Feb 2003 23:18:44 +0100	[thread overview]
Message-ID: <20030208221844.GA3206@win.tue.nl> (raw)
In-Reply-To: <Pine.LNX.4.44.0302081456180.3031-100000@localhost.localdomain>

On Sat, Feb 08, 2003 at 03:00:43PM -0600, Thomas Molina wrote:

> I began to see this bug this weekend myself.  I'm not sure of the cause, 
> but it can be worked around by configuring the kernel for built-in (not 
> modular) support of virtual terminals (CONFIG_VT) and support for console 
> on virtual terminals (CONFIG_VT_CONSOLE).  

Maybe unrelated, but there is some really ugly code in
char_dev.c:get_chrfops().

There, if one needs a character device that is not present
a request_module("char-major-%d") is done.
However, if the character device has TTY_MAJOR or TTYAUX_MAJOR
and a driver for this major is requested, and we already have
one, but it is the wrong one, then we also do the request_module.
Yecch.

The reason is of course that entirely different drivers cover
different fragments of the major space (4,1 is /dev/tty1 and
4,65 is /dev/ttyS1)

So, I could imagine that if one has neither module, and needs
one, get_chrfops() loads the wrong one. Speculation.

Andries

      reply	other threads:[~2003-02-08 22:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-08 20:36 [Bug 328] New: The computer seems to hang after the kernel has uncompressed and starts to boot Martin J. Bligh
2003-02-08 21:00 ` Thomas Molina
2003-02-08 22:18   ` Andries Brouwer [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20030208221844.GA3206@win.tue.nl \
    --to=aebr@win.tue.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mbligh@aracnet.com \
    --cc=tmolina@cox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).