From mboxrd@z Thu Jan  1 00:00:00 1970
From: "Johannes Schauer" <j.schauer@email.de>
Date: Wed, 04 May 2011 14:57:54 +0000
Subject: udev regression from 167 to 168 on notion ink adam
Message-Id: <809580245.144501.1304521074555.JavaMail.fmail@mwmweb069>
List-Id: <linux-hotplug.vger.kernel.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
To: linux-hotplug@vger.kernel.org

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