Hi, >On Wed, May 4, 2011 at 16:57, Johannes Schauer <j.schauer@xxxxxxxx> wrote: >> 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 bisected the commits from 167 to 168 and I found that this commit is the culprit introducing the error I see: commit ff2c503df091e6e4e9ab48cdb6df6ec8b7b525d0 Author: Kay Sievers <kay.sievers@xxxxxxxx> Date:  Tue, 12 Apr 2011 23:17:09 +0000 You can find a strace of the whole udev execution here: http://mister-muffin.de/p/vPMW basically it's these two messages repeating infinitely: [pid 2353] epoll_wait(0xb, 0xbeb4d3b8, 0x8, 0xbb8) = 1 [pid 2353] SYS_366(0x4, 0, 0, 0x80000, 0) = -1 ENOSYS (Function not implemented) Note, that the ENOSYS errors didnt show up when i just attached strace to the udev process. What is this SYS_366 message telling me? Why is it called and why is it missing? My kernel has CONFIG_EPOLL=y and as you can see in the strace epoll_create1 and epoll_ctl work just fine. It kinda looks like an error on my side but shouldnt udev nevertheless check for whatever it is and quit instead of running wild like that? thanks for helping! cheers, josch -- To unsubscribe from this list: send the line "unsubscribe linux-hotplug" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
