From: bugzilla-daemon@bugzilla.kernel.org
To: linux-scsi@vger.kernel.org
Subject: [Bug 13783] udev causes high cpu usage
Date: Thu, 23 Jul 2009 00:22:54 GMT [thread overview]
Message-ID: <200907230022.n6N0MsaH001657@demeter.kernel.org> (raw)
In-Reply-To: <bug-13783-11613@http.bugzilla.kernel.org/>
http://bugzilla.kernel.org/show_bug.cgi?id=13783
Andrew Morton <akpm@linux-foundation.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |akpm@linux-foundation.org
--- Comment #10 from Andrew Morton <akpm@linux-foundation.org> 2009-07-23 00:22:52 ---
(In reply to comment #9)
> I guess something goes crazy with the media-changed detection.
> Sometimes not-tested-in-such-setup/broken firmware for optical drives
> does not like us.
Seems a reasonable guess.
Do we know which device driver is being used for that drive?
In the ubuntu report at least three people are seeing the same problem. Is
there a common point where we can address this? Maybe a blacklist? Or are we
dealing with three separate low-level drivers?
Thanks.
--
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next prev parent reply other threads:[~2009-07-23 0:22 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-16 7:36 [Bug 13783] New: udev causes high cpu usage bugzilla-daemon
2009-07-16 7:36 ` [Bug 13783] " 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 [this message]
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
[not found] <bug-13783-11613@https.bugzilla.kernel.org/>
2013-12-10 16:41 ` 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=200907230022.n6N0MsaH001657@demeter.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.