Re: Runaway loop with the current git.

From: Kay Sievers
Date: Sat Dec 06 2008 - 13:12:01 EST

On Sat, Dec 6, 2008 at 17:56, Evgeniy Polyakov <zbr@xxxxxxxxxxx> wrote:
> On Sat, Dec 06, 2008 at 05:16:06PM +0100, Kay Sievers (kay.sievers@xxxxxxxx) wrote:
>> So the loop is probably a modprobe itself that tries to access
>> /dev/console. Is there a different argument for the very first
>> modprobe which is called? Which may be the one that triggers the loop.
> Hard to tell, I did not see anything but modprobe before and after
> runaway loop message, but it could be missed though, I will tell
> for sure only this Monday.

Sounds good.

It seems the /dev/console driver is registered only after all the pci,
video, acpi, ... drivers, so it's not surprising, that if any of these
driver in these subsystems calls request_module(), or a process in
initramfs tries to access the "dead" /dev/console node, things will go

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at