On Apr 04, Vincent Lefevre <vinc...@vinc17.net> wrote: > > > > If the system is not completely dead then you can see what happens by > > > > booting with init=/bin/bash, opening a second console with openvt and > > > > running the first few rcS.d scripts. > > > Are there any news about this alleged bug? > > No, closing. > What news do you need? On my machine, the bug occurred only once for > the moment, so that I don't think booting with init=/bin/bash will > help (I suppose that one would see that everything is fine). Why don't Determining what causes the deadlock (?). But if you cannot reproduce this then there is not much you can do.
> you provide more logs on the screen? (This could be optional, e.g. by > setting some environment variable.) Actually udevadm is supposed to print which events have not completed when the timeout is reached. I think that more complex analysis require human judgement. -- ciao, Marco
signature.asc
Description: Digital signature
