I guess it's debatable whether or not this is a bug, but request_module
before kmod is started causes the kernel to stop booting (presumably
waiting for the kmod thread to do something about it, which hasn't yet
been started).
An example of this is configuring CONFIG_PARPORT=y and CONFIG_PRINTER=y,
but CONFIG_PARPORT_PC=m. Now, first of all, no, this configuration
doesn't make a lot of sense at the moment, because the printer driver sets
itself up with a lowlevel parport driver when it first initialises, so
when there isn't one configured the printer driver is useless.
However, I believe that before kmod replaced kerneld, the symptom was "the
printer driver doesn't work" rather than "the kernel doesn't boot".
I don't believe that preventing that configuration in the first place is
an answer, because maybe one day we'll have the printer driver trying to
set itself up with a lowlevel parport driver each time an open() is done
on an lp device if it failed at initialisation time.
Tim.
*/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu