From: "Johannes Schauer" <j.schauer@email.de>
To: linux-hotplug@vger.kernel.org
Subject: udev regression from 167 to 168 on notion ink adam
Date: Wed, 04 May 2011 14:57:54 +0000 [thread overview]
Message-ID: <809580245.144501.1304521074555.JavaMail.fmail@mwmweb069> (raw)
hi,
I'm running debian unstable on the notion ink adam tablet.
It was all working fine until debian upgraded udev to 168.
From then on the following three things happen with new rootfs
builds:
1.) upon each boot udev would take 180 seconds to finish and
allow the boot process to continue after the "waiting for /dev to
be fully populated" message.
2.) when the system is booted doing "ps -e | grep udevd | wc -l"
yields that I have 24 udevd processes running.
3.) when i start "top" I see that there is a udevd process running
constantly consuming 100% cpu power.
I had still an older rootfs of mine lying around with udev 167 which
was working fine. After I upgraded it to 168 it showed the exact
same behaviour as explained above.
now my question is: how do I debug this? how do I find out
what is wrong? It is probably already helping that I know that 167
worked and 168 is not?
cheers, josch
next reply other threads:[~2011-05-04 14:57 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-04 14:57 Johannes Schauer [this message]
2011-05-04 15:20 ` udev regression from 167 to 168 on notion ink adam Marco d'Itri
2011-05-04 16:03 ` Kay Sievers
2011-05-04 16:31 ` Gabor Z. Papp
2011-05-04 16:36 ` Kay Sievers
2011-05-04 18:39 ` Johannes Schauer
2011-05-05 8:33 ` Johannes Schauer
2011-05-05 9:33 ` Kay Sievers
2011-05-05 9:38 ` Kay Sievers
2011-05-05 9:56 ` Marco d'Itri
2011-05-05 10:06 ` Kay Sievers
2011-05-05 10:18 ` Marco d'Itri
2011-05-05 11:32 ` Johannes Schauer
2011-05-05 12:04 ` Johannes Schauer
2011-05-05 15:13 ` Kay Sievers
2011-05-05 15:37 ` Johannes Schauer
2011-05-05 15:42 ` Marco d'Itri
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=809580245.144501.1304521074555.JavaMail.fmail@mwmweb069 \
--to=j.schauer@email.de \
--cc=linux-hotplug@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;
as well as URLs for NNTP newsgroup(s).