From: "Nick Zeljkovic" <nzeljkovic@site5.com>
To: linux-hotplug@vger.kernel.org
Subject: udevd going crazy
Date: Wed, 09 Sep 2009 23:14:35 +0000 [thread overview]
Message-ID: <000301ca31a3$4d5c5f10$e8151d30$@com> (raw)
Hello,
I'm experiencing an issue with udev and hotplugging on number of servers I
administer so I'm hoping someone can shed some light on this. Apparently it
keeps reading /proc/stat over and over again, invoking hundreds of processes
like:
root 22362 0.0 0.0 2232 1052 ? S 13:50 0:00 /bin/sh
/sbin/hotplug uids
root 22365 0.0 0.0 1552 396 ? S 13:50 0:00
/etc/hotplug.d/default/20-hal.hotplug uids
root 22367 0.0 0.0 2232 1052 ? S 13:50 0:00 /bin/sh
/sbin/hotplug uids
root 22370 0.0 0.0 1552 396 ? S 13:50 0:00
/etc/hotplug.d/default/20-hal.hotplug uids
root 22372 0.0 0.0 2232 1052 ? S 13:50 0:00 /bin/sh
/sbin/hotplug uids
root 22373 0.0 0.0 2232 1052 ? S 13:50 0:00 /bin/sh
/sbin/hotplug uids
root 22378 0.0 0.0 1552 396 ? S 13:50 0:00
/etc/hotplug.d/default/20-hal.hotplug uids
root 22381 0.0 0.0 1552 396 ? S 13:50 0:00
/etc/hotplug.d/default/20-hal.hotplug uids
root 22382 0.0 0.0 2232 1052 ? S 13:50 0:00 /bin/sh
/sbin/hotplug uids
root 22386 0.0 0.0 1552 396 ? S 13:50 0:00
/etc/hotplug.d/default/20-hal.hotplug uids
root 22390 0.0 0.0 2232 1052 ? S 13:50 0:00 /bin/sh
/sbin/hotplug uids
root 22395 0.0 0.0 1552 396 ? S 13:50 0:00
/etc/hotplug.d/default/20-hal.hotplug uids
root 22400 0.0 0.0 2232 1052 ? S 13:50 0:00 /bin/sh
/sbin/hotplug uids
root 22403 0.0 0.0 1552 396 ? S 13:50 0:00
/etc/hotplug.d/default/20-hal.hotplug uids
root 22407 0.0 0.0 2232 1052 ? S 13:50 0:00 /bin/sh
/sbin/hotplug uids
root 22411 0.0 0.0 1552 396 ? S 13:50 0:00
/etc/hotplug.d/default/20-hal.hotplug uids
root 22415 0.0 0.0 2232 1052 ? S 13:50 0:00 /bin/sh
/sbin/hotplug uids
root 22420 0.0 0.0 1552 396 ? S 13:50 0:00
/etc/hotplug.d/default/20-hal.hotplug uids
root 22421 0.0 0.0 2232 1052 ? S 13:50 0:00 /bin/sh
/sbin/hotplug uids
root 22424 0.0 0.0 2232 1052 ? S 13:50 0:00 /bin/sh
/sbin/hotplug uids
root 22427 0.0 0.0 1552 396 ? S 13:50 0:00
/etc/hotplug.d/default/20-hal.hotplug uids
root 22430 0.0 0.0 1552 396 ? S 13:50 0:00
/etc/hotplug.d/default/20-hal.hotplug uids
root 22434 0.0 0.0 2232 1052 ? S 13:50 0:00 /bin/sh
/sbin/hotplug uids
root 22438 0.0 0.0 1552 396 ? S 13:50 0:00
/etc/hotplug.d/default/20-hal.hotplug uids
root 22439 0.0 0.0 2232 1052 ? S 13:50 0:00 /bin/sh
/sbin/hotplug uids
root 22443 0.0 0.0 2232 1052 ? S 13:50 0:00 /bin/sh
/sbin/hotplug uids
root 22447 0.0 0.0 1552 396 ? S 13:50 0:00
/etc/hotplug.d/default/20-hal.hotplug uids
root 22450 0.0 0.0 1552 396 ? S 13:50 0:00
/etc/hotplug.d/default/20-hal.hotplug uids
root 22453 0.0 0.0 2232 1052 ? S 13:50 0:00 /bin/sh
/sbin/hotplug uids
root 22457 0.0 0.0 1552 396 ? S 13:50 0:00
/etc/hotplug.d/default/20-hal.hotplug uids
root 22460 0.0 0.0 2232 1052 ? S 13:50 0:00 /bin/sh
/sbin/hotplug uids
root 22467 0.0 0.0 1552 396 ? S 13:50 0:00
/etc/hotplug.d/default/20-hal.hotplug uids
Strace for couple of seconds shows following:
http://pastebin.org/16521
/var/log/messages is full of only this:
Sep 6 18:41:13 ki udevd[29080]: udev done!
Sep 6 18:41:16 ki udevd[29080]: udev done!
Sep 6 18:41:18 ki udevd[29080]: udev done!
Sep 6 18:41:18 ki udevd[29080]: udev done!
Sep 6 18:41:19 ki udevd[29080]: udev done!
Sep 6 18:41:22 ki udevd[29080]: udev done!
/proc/stat
# cat /proc/stat
cpu 11458835 600250 4801260 34738235 3061241 17237 1368609 0 0
cpu0 1168306 41683 488778 4863945 285438 634 157006 0 0
cpu1 1150829 43370 487201 4873639 292977 720 157055 0 0
cpu2 1608174 45898 706976 4197142 289228 1409 156841 0 0
cpu3 1616953 44795 705236 4210027 269132 573 158955 0 0
cpu4 1066992 43732 464962 4927574 324869 1108 176520 0 0
cpu5 1146562 43855 491779 4860184 287530 678 175139 0 0
cpu6 2082830 291156 752676 2639122 1045792 11467 182594 0 0
cpu7 1618185 45756 703648 4166599 266270 645 204496 0 0
intr 206548530 43 2 0 5 12 0 0 0 44 0 0 0 7 0 622614 0 0 0 0 0 0 3178 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 13018109 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 209663 34722627
ctxt 349750043
btime 1252449906
processes 10483879
procs_running 3
procs_blocked 7
I'm at loss why is this happening, could it be hardware malfunction of some
kind ? It should be important to note that this happens across multiple
servers (10+) almost daily.
With anticipation,
Nick
next reply other threads:[~2009-09-09 23:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-09 23:14 Nick Zeljkovic [this message]
2009-09-09 23:24 ` udevd going crazy Kay Sievers
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='000301ca31a3$4d5c5f10$e8151d30$@com' \
--to=nzeljkovic@site5.com \
--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).