linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-scsi@vger.kernel.org
Subject: [Bug 13783] New: udev causes high cpu usage
Date: Thu, 16 Jul 2009 07:36:03 GMT	[thread overview]
Message-ID: <bug-13783-11613@http.bugzilla.kernel.org/> (raw)

http://bugzilla.kernel.org/show_bug.cgi?id=13783

           Summary: udev causes high cpu usage
           Product: IO/Storage
           Version: 2.5
    Kernel Version: 2.6.31-rc3
          Platform: All
        OS/Version: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: SCSI
        AssignedTo: linux-scsi@vger.kernel.org
        ReportedBy: AndreasFackler@web.de
        Regression: No


Created an attachment (id=22372)
 --> (http://bugzilla.kernel.org/attachment.cgi?id=22372)
Output of "udevadm monitor --environment" with udev-141-1.2 and kernel 2.6.30

Before I upgraded the udev version of Ubuntu 9.04 from 141-1 to 141-1.1 (and
141-1.2), top reported about 2% total cpu usage when idle. After the update, it
rarely drops below 35%. Though top lists udevd among the more cpu hungry
processes, it is only listed with about 3%, while system (in line 3) almost
never drops below 20%.

"udevadm monitor --environment" after the upgrade reports many additional
events with "SUBSYSTEM=scsi" and "ACTION=change".

I am using the amd64 version of Xubuntu 9.04 on a Acer Extensa 5230 laptop with
a 2 GHz Intel Celeron processor. The problem occurs with all the kernel
versions I tried: The Ubuntu kernel 2.6.28 and the mainline kernels 2.6.30 and
2.6.31-rc3.

See also the Ubuntu bug report:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/379780

-- 
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

             reply	other threads:[~2009-07-16  7:36 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-16  7:36 bugzilla-daemon [this message]
2009-07-16  7:36 ` [Bug 13783] udev causes high cpu usage bugzilla-daemon
2009-07-16  7:37 ` bugzilla-daemon
2009-07-16  7:38 ` bugzilla-daemon
2009-07-16  7:38 ` bugzilla-daemon
2009-07-16  7:56 ` bugzilla-daemon
2009-07-16 17:26 ` bugzilla-daemon
2009-07-17 11:43 ` bugzilla-daemon
2009-07-17 15:36 ` bugzilla-daemon
2009-07-17 15:58 ` bugzilla-daemon
2009-07-23  0:22 ` bugzilla-daemon
2009-07-23  7:58 ` bugzilla-daemon
2009-07-25  3:33 ` bugzilla-daemon
2009-07-31 15:33 ` bugzilla-daemon
2009-07-31 15:37 ` bugzilla-daemon
2009-07-31 15:44 ` bugzilla-daemon
2009-10-17  4:01 ` bugzilla-daemon
2009-10-17  4:06 ` bugzilla-daemon
2009-10-18  3:06 ` bugzilla-daemon
2009-10-19  3:46 ` bugzilla-daemon
2009-10-22  7:00 ` bugzilla-daemon
2009-10-26 15:08 ` bugzilla-daemon
2009-11-20  8:15 ` bugzilla-daemon
2009-11-27  9:52 ` bugzilla-daemon
2010-01-03  1:42 ` bugzilla-daemon
2010-01-17 21:15 ` bugzilla-daemon
2010-02-01 23:35 ` bugzilla-daemon
2010-02-08 19:45 ` bugzilla-daemon
2010-02-09  3:37 ` bugzilla-daemon
2010-02-10 10:27 ` bugzilla-daemon
2010-02-15 16:42 ` bugzilla-daemon

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=bug-13783-11613@http.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=linux-scsi@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).