From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev cpu usage on FC2
Date: Wed, 10 Nov 2004 02:11:00 +0000 [thread overview]
Message-ID: <1100052660.7880.5.camel@localhost.localdomain> (raw)
In-Reply-To: <8f1a5cec04110917576d1e4e05@mail.gmail.com>
On Tue, 2004-11-09 at 17:57 -0800, Muralidhar Ganga wrote:
> Hi,
>
> Running Fedora Core 2. (2.6.6-1.435.2.3)
>
> The process udev takes 98% of the CPU all the time.
> I have only one USB mouse.
>
> How do I fix this ?
Try:
rm -f /dev/.udevdb
killall udevd
Remove and reinsert your mouse and look if udevd is started again and
back to normal cpu usage.
Kay
-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_idU88&alloc_id\x12065&op=click
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
prev parent reply other threads:[~2004-11-10 2:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-10 1:57 udev cpu usage on FC2 Muralidhar Ganga
2004-11-10 2:11 ` Kay Sievers [this message]
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=1100052660.7880.5.camel@localhost.localdomain \
--to=kay.sievers@vrfy.org \
--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).