Bug 708648 - USB 3.0 errors, same drive works on 2.0
Summary: USB 3.0 errors, same drive works on 2.0
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 14
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-05-28 15:24 UTC by Mike Lindner
Modified: 2011-08-29 14:18 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-08-29 14:18:46 UTC
Type: ---

Attachments (Terms of Use)
output of dmesg, /var/log/messages showing failure on 3.0 port, success on 2.0 port (86.12 KB, application/octet-stream)
2011-05-28 15:24 UTC, Mike Lindner 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Mike Lindner 2011-05-28 15:24:30 UTC 
Created attachment 501489 [details]
output of dmesg, /var/log/messages showing failure on 3.0 port, success on 2.0 port

Description of problem:

USB 3.0 external drive mounts, then fails if connected to USB 3.0 port. Drive works when connected to USB 2.0 port.

Among the errors in /var/log/messages is "xhci_hcd 0000:03:00.0: HC died; cleaning up"

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

How reproducible: Always

Steps to Reproduce:
1. Connect drive
2. watch it fail
  
Actual results:

Failure usually happens pretty quickly - sometimes can get it to display files in file manager before it dies.

Expected results:

File should mount and be usable.

Additional info:

See attached dmesg and messages files
Comment 1 Chuck Ebbert 2011-06-22 11:00:34 UTC 
USB 3.0 is very buggy on 2.6.35; I wouldn't expect this to get fixed. Fedora 15 has kernel 2.6.38.8 now and seems to work pretty well.
Comment 2 Josh Boyer 2011-08-29 14:18:46 UTC 
We aren't going to fix this in F14 at this point.  Please try F15 or newer.
Note You need to log in before you can comment on or make changes to this bug.