From: Andrew Morton <akpm@linux-foundation.org>
To: "Kay Sievers" <kay.sievers@vrfy.org>
Cc: sfr@canb.auug.org.au, linux-next@vger.kernel.org,
linux-kernel@vger.kernel.org, adobriyan@gmail.com,
greg@kroah.com
Subject: Re: linux-next: Tree for December 9
Date: Tue, 9 Dec 2008 16:15:11 -0800 [thread overview]
Message-ID: <20081209161511.15fe8cdb.akpm@linux-foundation.org> (raw)
In-Reply-To: <ac3eb2510812091606k5615135fn87d35aaa16834ea8@mail.gmail.com>
On Wed, 10 Dec 2008 01:06:47 +0100
"Kay Sievers" <kay.sievers@vrfy.org> wrote:
> On Wed, Dec 10, 2008 at 00:34, Andrew Morton <akpm@linux-foundation.org> wrote:
> > On Tue, 9 Dec 2008 18:52:37 +1100
> > Stephen Rothwell <sfr@canb.auug.org.au> 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
(lol)
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
UEVENT[1228867146.145709] add@/class/bdi/9:0
UEVENT[1228867146.145895] remove@/class/bdi/9:0
UEVENT[1228867146.145941] remove@/block/md0
UDEV [1228867146.148606] add@/block/md0
UDEV [1228867146.154832] add@/class/bdi/9:0
UDEV [1228867146.159299] remove@/block/md0
UDEV [1228867146.163750] remove@/class/bdi/9:0
UEVENT[1228867146.171354] add@/block/md0
UEVENT[1228867146.171391] add@/class/bdi/9:0
UEVENT[1228867146.171546] remove@/class/bdi/9:0
UEVENT[1228867146.171566] remove@/block/md0
UDEV [1228867146.174242] add@/block/md0
UDEV [1228867146.180730] add@/class/bdi/9:0
UDEV [1228867146.185137] remove@/block/md0
UDEV [1228867146.189435] remove@/class/bdi/9:0
UEVENT[1228867146.197278] add@/block/md0
UEVENT[1228867146.197330] add@/class/bdi/9:0
UEVENT[1228867146.197503] remove@/class/bdi/9:0
UEVENT[1228867146.197545] remove@/block/md0
UDEV [1228867146.200025] add@/block/md0
UDEV [1228867146.206571] add@/class/bdi/9:0
UDEV [1228867146.210940] remove@/block/md0
UDEV [1228867146.215359] remove@/class/bdi/9:0
UEVENT[1228867146.223278] add@/block/md0
UEVENT[1228867146.223336] add@/class/bdi/9:0
UEVENT[1228867146.223524] remove@/class/bdi/9:0
UEVENT[1228867146.223571] remove@/block/md0
UDEV [1228867146.226163] add@/block/md0
UDEV [1228867146.232415] add@/class/bdi/9:0
UDEV [1228867146.236739] remove@/block/md0
UDEV [1228867146.241042] remove@/class/bdi/9:0
UEVENT[1228867146.248895] add@/block/md0
UEVENT[1228867146.249012] add@/class/bdi/9:0
UEVENT[1228867146.249306] remove@/class/bdi/9:0
UEVENT[1228867146.249409] remove@/block/md0
next prev parent reply other threads:[~2008-12-10 0:15 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-09 7:52 linux-next: Tree for December 9 Stephen Rothwell
2008-12-09 8:53 ` Al Viro
2008-12-09 13:57 ` byteorder headers on parisc Alexey Dobriyan
2008-12-09 23:12 ` Harvey Harrison
2008-12-09 23:34 ` linux-next: Tree for December 9 Andrew Morton
2008-12-10 0:06 ` Kay Sievers
2008-12-10 0:15 ` Andrew Morton [this message]
2008-12-10 0:31 ` Kay Sievers
2008-12-10 1:30 ` Andrew Morton
2008-12-10 1:36 ` Kay Sievers
2008-12-10 1:42 ` NeilBrown
2008-12-10 1:58 ` Andrew Morton
2008-12-10 19:16 ` Andrew Morton
2008-12-10 22:15 ` Neil Brown
2008-12-10 11:57 ` [BUG] linux-next: 20081209 - kernel bug at __rcu_process_callbacks, while booting up Kamalesh Babulal
2008-12-10 14:54 ` Paul E. McKenney
2008-12-10 16:30 ` Kamalesh Babulal
2008-12-10 17:53 ` Paul E. McKenney
2008-12-10 18:09 ` Kamalesh Babulal
2008-12-10 18:33 ` Paul E. McKenney
2008-12-12 19:40 ` Kamalesh Babulal
2008-12-12 22:16 ` Paul E. McKenney
2008-12-16 14:30 ` Kamalesh Babulal
2008-12-16 14:37 ` Jens Axboe
2008-12-17 11:12 ` Kamalesh Babulal
2008-12-17 11:18 ` Jens Axboe
-- strict thread matches above, loose matches on Subject: below --
2009-12-09 6:47 linux-next: Tree for December 9 Stephen Rothwell
2010-12-09 4:41 Stephen Rothwell
2010-12-09 11:46 ` Zimny Lech
2010-12-09 15:49 ` Greg KH
2010-12-09 16:42 ` Zimny Lech
2010-12-09 19:35 ` Jing Huang
2010-12-09 20:29 ` Zimny Lech
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=20081209161511.15fe8cdb.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=adobriyan@gmail.com \
--cc=greg@kroah.com \
--cc=kay.sievers@vrfy.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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