Bug 705925 - USB bus chokes up when attaching devices
Summary: USB bus chokes up when attaching devices
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 15
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-05-18 21:31 UTC by Jakub Steiner
Modified: 2012-06-21 17:41 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-06-21 17:41:45 UTC
Type: ---


Attachments (Terms of Use)
dmesg output of a typical session (86.67 KB, text/plain)
2011-05-18 21:31 UTC, Jakub Steiner
no flags Details
lspci output (1.93 KB, text/plain)
2011-05-18 21:32 UTC, Jakub Steiner
no flags Details

Description Jakub Steiner 2011-05-18 21:31:47 UTC
Created attachment 499700 [details]
dmesg output of a typical session

Description of problem:

When attaching USB devices, it takes over a minute for a device to show up and in some cases they never do. There is a lot of  "device descriptor read/8, error -110" in the syslog.

In addition to attaching new devices, the system boots in over 4 minutes instead of a few seconds it used to.

This has not been a problem with F14.

Version-Release number of selected component (if applicable):

Fedora release 15 (Lovelock), 
2.6.38.6-26.rc1.fc15.x86_64 #1 SMP Mon May 9 20:45:15 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux

How reproducible:
Every time.

Additional info:

Attaching dmesg output (attached a usb headset at the end that took a while to find) and lspci, ready to provide what's needed.

Comment 1 Jakub Steiner 2011-05-18 21:32:18 UTC
Created attachment 499702 [details]
lspci output

Comment 2 Josh Boyer 2012-06-06 13:00:12 UTC
Jakub, are you still seeing this with the 2.6.43/3.3 updates in F15/F16?

Comment 3 Jakub Steiner 2012-06-21 16:28:30 UTC
I've updated that particular system to F17 that doesn't seem to suffer from this anymore, but I can't say about F16.

Comment 4 Josh Boyer 2012-06-21 17:41:45 UTC
F16 and F17 are on the same base kernel now.  Thanks for letting us know.


Note You need to log in before you can comment on or make changes to this bug.