Skip to contentSkip to conversation

2.6.34 on Samsung P460: reset after "Waiting for /dev to be fully populated"

DISCUSSION Harald Dunkel 4 participants 8 messages May 25, 2010 – Aug 4, 2010

lore
Share & tools
lore
#0 lore raw

Hi folks,

Problem: At boot time I see a final message

Waiting for /dev to be fully populated

then my laptop (Samsung P460) does a reset. The next boot doesn't work, so I have to power-cycle the laptop.

If I boot with "acpi=off", then 2.6.34 gets stuck instead. The last 2 lines are

TCP reno registered
Net: Registered protocol family 1

Any helpful comment would be highly appreciated.

Regards

Harri

#1 lore raw
Quoted 9 lines · On Tue, 25 May 2010 11:12:30 +0200 Harald Dunkel <[email protected]>…

Hi folks,

Problem: At boot time I see a final message

Waiting for /dev to be fully populated

then my laptop (Samsung P460) does a reset. The next boot doesn't work, so I have to power-cycle the laptop.

Quoted 8 lines

If I boot with "acpi=off", then 2.6.34 gets stuck instead. The last 2 lines are

TCP reno registered
Net: Registered protocol family 1

Any helpful comment would be highly appreciated.

ow, hard.

I assume that the "Waiting for /dev to be fully populated" comes from udev? Greg, do you know what might trigger that?

Harald, I think the best (only?) way to fix this is for you to do a bisection search. http://landley.net/writing/git-quick.html has some instructions.

It's a bit of a pain to do, sorry.

#2 lore raw
Quoted 18 lines · Andrew Morton
Quoted 7 lines · On Tue, 25 May 2010 11:12:30 +0200 Harald Dunkel <[email protected]>…

Problem: At boot time I see a final message

      Waiting for /dev to be fully populated

then my laptop (Samsung P460) does a reset. The next boot doesn't work, so I have to power-cycle the laptop.

Quoted 7 lines

If I boot with "acpi=off", then 2.6.34 gets stuck instead. The last 2 lines are

      TCP reno registered
      Net: Registered protocol family 1

Any helpful comment would be highly appreciated.

ow, hard.

Quoted 8 lines

I assume that the "Waiting for /dev to be fully populated" comes from udev?  Greg, do you know what might trigger that?

Harald, I think the best (only?) way to fix this is for you to do a bisection search.  http://landley.net/writing/git-quick.html has some instructions.

It's a bit of a pain to do, sorry.

A behavior like this is usually a kernel module that gets loaded which hangs the box. The message comes from distro specific stuff, and not from udev itself, so we can't know what exactly it is doing.

Did you wait for 3 minutes at least to let the boot processes run into their timeouts?

Are you using an initramfs? If not, does init=/bin/sh work?

For current -git kernels it could be the FIONREAD bug, which breaks all sorts of services using inotify. They all hang in a loop, it's not only udevd:
http://lkml.org/lkml/2010/5/23/100

Kay

#3 lore raw
Quoted 8 lines · Kay Sievers

A behavior like this is usually a kernel module that gets loaded which hangs the box. The message comes from distro specific stuff, and not from udev itself, so we can't know what exactly it is doing.

Did you wait for 3 minutes at least to let the boot processes run into their timeouts?

I waited for 10 minutes, but there was no additional action. Its stuck.

Quoted 2 lines

Are you using an initramfs? If not, does init=/bin/sh work?

I am using an initrd. init=/bin/sh did not work; it complained about a missing boot disk.

To get rid of some autodetected devices I also disabled USB support in the BIOS, as far as possible. No luck.

Quoted 5 lines

For current -git kernels it could be the FIONREAD bug, which breaks all sorts of services using inotify. They all hang in a loop, it's not only udevd:
http://lkml.org/lkml/2010/5/23/100

The most recent kernel I tried is 2.6.34. I built it and installed it on USB. The same USB stick boots fine in other PCs (e.g. a Dell XPS M1300).

Of course I will keep on trying.

Regards

Harri

#4 lore raw
Quoted 10 lines · Harald Dunkel
Quoted 8 lines · Kay Sievers

A behavior like this is usually a kernel module that gets loaded which hangs the box. The message comes from distro specific stuff, and not from udev itself, so we can't know what exactly it is doing.

Did you wait for 3 minutes at least to let the boot processes run into their timeouts?

Quoted 8 lines

I waited for 10 minutes, but there was no additional action. Its stuck.

Quoted 2 lines

Are you using an initramfs? If not, does init=/bin/sh work?

I am using an initrd. init=/bin/sh did not work; it complained about a missing boot disk.

Try rdinit=/bin/sh and you should/might get a shell from the initramfs image?

Kay

#5 lore raw
In reply to Harald Dunkel

Hi Kay,

Sorry for the delay.

It crashes when the "processor" acpi module is loaded. If I blacklist this module, then the laptop boots fine.

The same problem exists for 2.6.35 and older kernels.

Of course I would be glad to help to track this down.

Regards

Harri

#6 lore raw
Quoted 5 lines · Harald Dunkel

Hi Kay,

Sorry for the delay.

It crashes when the "processor" acpi module is loaded.

Sounds like an ACPI bug. The ACPI developers use the bugzilla.kernel.org site to track things like this. Try filing a bug there and they can take care of it.

thanks,

greg k-h