On Wed, Dec 10, 2008 at 01:15, Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> wrote: > On Wed, 10 Dec 2008 01:06:47 +0100 > "Kay Sievers" <kay.sievers@xxxxxxxx> wrote: >> On Wed, Dec 10, 2008 at 00:34, Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> wrote: >> > On Tue, 9 Dec 2008 18:52:37 +1100 >> > Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx> wrote: >> > >> >> I have created today's linux-next tree at >> >> git://git.kernel.org/pub/scm/linux/kernel/git/sfr/linux-next.git >> > >> > udevd is sitting there chewing up 100% of a CPU all the time. >> > >> > The machine is x86_64, running FC6. It still happens with >> > CONFIG_SELINUX=n. >> > >> > config: http://userweb.kernel.org/~akpm/config-akpm2.txt >> > dmesg: http://userweb.kernel.org/~akpm/dmesg-akpm2.txt >> > strace of udevd: http://userweb.kernel.org/~akpm/strace.out.txt >> > >> > excerpt: >> > >> > close(9) = 0 >> > open("/proc/21707/stat", O_RDONLY) = 9 >> > read(9, "21707 (hald-addon-stor) S 21033 "..., 255) = 240 >> > close(9) = 0 >> > open("/proc/22340/stat", O_RDONLY) = 9 >> > read(9, "22340 (smartd) S 1 22339 22339 0"..., 255) = 245 >> > close(9) = 0 >> >> Maybe an event loop, caused by something. >> >> Are you still able to run: >> udevmonitor --kernel >> and see if we get events, maybe in a loop, from the kernel? > > akpm2:/home/akpm# udevmonitor --kernel > unknown option Ok, it was just -k that time. :) > akpm2:/home/akpm# udevmonitor > udevmonitor prints the received event from the kernel [UEVENT] > and the event which udev sends out after rule processing [UDEV] > > UDEV [1228867146.103334] add@/class/bdi/9:0 > UDEV [1228867146.107566] remove@/block/md0 > UDEV [1228867146.111969] remove@/class/bdi/9:0 > UEVENT[1228867146.119889] add@/block/md0 > UEVENT[1228867146.119964] add@/class/bdi/9:0 > UEVENT[1228867146.120162] remove@/class/bdi/9:0 > UEVENT[1228867146.120205] remove@/block/md0 > UDEV [1228867146.122839] add@/block/md0 > UDEV [1228867146.129125] add@/class/bdi/9:0 > UDEV [1228867146.133459] remove@/block/md0 > UDEV [1228867146.137813] remove@/class/bdi/9:0 > UEVENT[1228867146.145652] add@/block/md0 Weird loop, something is accessing /dev/md0, i guess, which creates the kernel device, and the event, which accesses /dev/md0 again and it goes crazy. Maybe caused by changes Neil did. Do you use md devices on that box? Thanks, Kay -- To unsubscribe from this list: send the line "unsubscribe linux-next" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
