On 2011-04-05 03:00:29 +0200, Marco d'Itri wrote:
If the boot does not continue then it looks like that udev loaded a
module which crashed your system (so this would be a kernel bug).
It is sometimes completely frozen. A 3-minute freeze or complete
freeze always seem to occur with
Next reboot, still with udev_log=info, I got a 3-minute timeout again.
The last 4 lines displayed on the screen were something like:
udevd-work[419]: passed -1 bytes to netlink monitor 0x...
udevd-work[419]: seq 1531 processed with 0
udevd[407]: seq 1510 done with 0
udevd[407]: seq 1531 done with
On Apr 05, Vincent Lefevre vinc...@vinc17.net wrote:
Three minutes, so I still do not know what happened to your system.
I've done a first reboot, and I got this 3-minute timeout (apparently).
The next reboot is completely frozen (see attached image, not very
readable, though).
If the boot
On 2011-04-04 01:08:39 +0200, Marco d'Itri wrote:
On Jan 19, Marco d'Itri m...@linux.it 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
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,
On 2011-04-04 02:05:43 +0200, Marco d'Itri wrote:
On Apr 04, Vincent Lefevre vinc...@vinc17.net wrote:
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
On Apr 04, Vincent Lefevre vinc...@vinc17.net wrote:
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.
What is the timeout? I switched off the machine after more than
10 minutes,
On Jan 05, Marco d'Itri m...@linux.it wrote:
What does freeze mean exactly? Is the system completely dead or just
waiting for udevadm settle to return? If so, what happens if you wait
for the 3 minutes timeout?
If the system is not completely dead then you can see what happens by
booting
user release.debian@packages.debian.org
usertag 606192 squeeze-can-defer
tag 606192 squeeze-ignore
kthxbye
On Wed, Jan 5, 2011 at 17:10:28 +0100, Marco d'Itri wrote:
On Dec 07, Bo Forslund bo.forsl...@abc.se wrote:
The system freeze saying Waiting for /dev to be fully populated.
On Dec 07, Bo Forslund bo.forsl...@abc.se wrote:
The system freeze saying Waiting for /dev to be fully populated.
There is a possible hmm,... quirk. I have an USB digital piano attached.
And if the piano is turned off at boot, system freeze waiting for
/dev... It can work with the piano off
Package: possibly initscripts
Severity: grave
--- Please enter the report below this line. ---
The system freeze saying Waiting for /dev to be fully populated.
There is a possible hmm,... quirk. I have an USB digital piano attached.
And if the piano is turned off at boot, system freeze waiting
11 matches
Mail list logo
