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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 26 May 2010 15:18:11 +0200
From:	Harald Dunkel <harald.dunkel@...igo.de>
To:	Kay Sievers <kay.sievers@...y.org>
CC:	Andrew Morton <akpm@...ux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Greg KH <greg@...ah.com>
Subject: Re: 2.6.34 on Samsung P460: reset after "Waiting for /dev to be fully
 	populated"

On 05/26/10 10:50, Kay Sievers wrote:
> 
> 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.

> 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.

> 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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/