![]() | |||||||||||||
Messages in this thread |
> This modprobe process does try to log an error, accesses /dev/console, > which is not initialized in the kernel at that time, and the kernel > module loader tries the load a module to support dev_t 5:1, which > again runs modprobe, and ... So we have a buggy modprobe... > > Setting CONFIG_CRYPTO_MANAGER=y makes it disapper. The patch I sent > seems to fix it. > > The bug is handled here: http://bugzilla.kernel.org/show_bug.cgi?id=12153 We cannot go re-ordering random chunks of kernel init with unpredictable effects including possibly making other stuff less reliable (because you set up the console device before the console driver is loaded on a PCI bus device). And we certainly can't do it this close to a release. Alan | ||||||||||||
| Last update: 2008-12-07 12:25 [from the cache] ©2003-2008 | |||||||||||||