On Fri, 06 Aug 2010 16:34:43 +0100
David Howells <dhowells@redhat.com> wrote:

quoted text
> Make /dev/console get initialised before any initialisation routine that
> invokes modprobe because if modprobe fails, it's going to want to open
> /dev/console, presumably to write an error message to.
> 
> The problem with that is that if the /dev/console driver is not yet
> initialised, the chardev handler will call request_module() to invoke modprobe,
> which will fail, because we never compile /dev/console as a module.
> 
> This will lead to a modprobe loop, showing the following in the kernel log:
> 
> 	request_module: runaway loop modprobe char-major-5-1
> 	request_module: runaway loop modprobe char-major-5-1
> 	request_module: runaway loop modprobe char-major-5-1
> 	request_module: runaway loop modprobe char-major-5-1
> 	request_module: runaway loop modprobe char-major-5-1

Boy, that's a familiar message.

quoted text
> This can happen, for example, when the built in md5 module can't find the built
> in cryptomgr module (because the latter fails to initialise).  The md5 module
> comes before the call to tty_init(), presumably because 'crypto' comes before
> 'drivers' alphabetically.
> 
> Fix this by calling tty_init() from chrdev_init().

http://www.google.com/search?sclient=psy&hl=en&site=&source=hp&q=%22request_module%3A+...
gets 10000 hits.  How many of those do you reckon this patch will fix? 

--
unsubscribe notice
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/