From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: hotplug/usb.agent consumes all CPU
Date: Tue, 01 Feb 2005 22:33:39 +0000 [thread overview]
Message-ID: <1107297219.21669.21.camel@localhost.localdomain> (raw)
In-Reply-To: <dd54e0e05020113225e614de6@mail.gmail.com>
On Tue, 2005-02-01 at 16:22 -0500, Simon Wu wrote:
> Hello,
>
> I am using udev with hotplug on kernel 2.6.5 and 2.6.9 (Fedora2 and 3). When I
> plug one single cdc_acm device (Nokia wireless cellphones/modem) into
> the USB port, dozens of hotplug usb.agent processes invoked and took
> away all CPU for 7 to 8 seconds. During this time, the computer
> doesn't even accept keyboard input.
>
> If I plug N Nokia phones in the USB ports at the same time, there seem
> to have N times of usb.agent processes and Nx7 seconds delay.
>
> Any way to improve it?
How can you be sure, that the hotplug processes are taking your
cpu and that it's not the kernel with the cdc_acm driver that blocks?
Are you using other USB devices on the system? Any chance to try maybe
a storage device on the same port, if that works as expected?
It would be nice to know if you get the same behavior with a 2.6.10
kernel, if you can get one for your system.
Thanks,
Kay
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
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
next prev parent reply other threads:[~2005-02-01 22:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-01 21:22 hotplug/usb.agent consumes all CPU Simon Wu
2005-02-01 22:33 ` Kay Sievers [this message]
2005-02-03 19:15 ` Simon Wu
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=1107297219.21669.21.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).