From: Harald Dunkel <harald.dunkel@aixigo.de>
To: Kay Sievers <kay.sievers@vrfy.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Greg KH <greg@kroah.com>
Subject: Re: 2.6.34 on Samsung P460: reset after "Waiting for /dev to be fully populated"
Date: Wed, 26 May 2010 15:18:11 +0200 [thread overview]
Message-ID: <4BFD1F93.7080000@aixigo.de> (raw)
In-Reply-To: <AANLkTil_-pV3jBkdBrWlz6iKr_lo2b3ZUFUvP8MFoByg@mail.gmail.com>
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
next prev parent reply other threads:[~2010-05-26 13:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-25 9:12 2.6.34 on Samsung P460: reset after "Waiting for /dev to be fully populated" Harald Dunkel
2010-05-26 1:46 ` Andrew Morton
2010-05-26 8:50 ` Kay Sievers
2010-05-26 13:18 ` Harald Dunkel [this message]
2010-05-26 13:20 ` Kay Sievers
2010-08-03 7:02 ` Harald Dunkel
2010-08-03 15:14 ` Greg KH
2010-08-04 6:56 ` Harald Dunkel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4BFD1F93.7080000@aixigo.de \
--to=harald.dunkel@aixigo.de \
--cc=akpm@linux-foundation.org \
--cc=greg@kroah.com \
--cc=kay.sievers@vrfy.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox