Bug 759267 - Attaching a new USB device causes USB bus to crash hard (requiring reboot).
Summary: Attaching a new USB device causes USB bus to crash hard (requiring reboot).
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 16
Hardware: x86_64
OS: Unspecified
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-12-01 19:56 UTC by Lars Kellogg-Stedman
Modified: 2012-03-01 16:00 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-03-01 16:00:28 UTC
Type: ---


Attachments (Terms of Use)

Description Lars Kellogg-Stedman 2011-12-01 19:56:12 UTC
Description of problem:

Occasionally, when attaching a new USB device to my F16 system, I see the following trace in dmesg:

[175324.687177] ehci_hcd 0000:00:1d.0: fatal error
[175324.687186] DRHD: handling fault status reg 2
[175324.687196] DMAR:[DMA Read] Request device [00:1d.0] fault addr 0 
[175324.687203] DMAR:[fault reason 06] PTE Read access is not set
[175324.691091] ehci_hcd 0000:00:1d.0: HC died; cleaning up
[175324.693560] ehci_hcd 0000:00:1d.0: force halt; handshake ffffc90000c78024 00004000 00004000 -> -110
[175324.693566] ehci_hcd 0000:00:1d.0: HC died; cleaning up
[175324.698035] usb 2-1.7: device descriptor read/all, error -108
[175324.698045] hub 2-1:1.0: cannot disable port 7 (err = -19)
[175324.698067] hub 2-1:1.0: cannot reset port 7 (err = -19)
[175324.698074] hub 2-1:1.0: cannot disable port 7 (err = -19)
[175324.698084] hub 2-1:1.0: cannot reset port 7 (err = -19)
[175324.698089] hub 2-1:1.0: cannot disable port 7 (err = -19)
[175324.698098] hub 2-1:1.0: cannot reset port 7 (err = -19)
[175324.698103] hub 2-1:1.0: cannot disable port 7 (err = -19)
[175324.698108] hub 2-1:1.0: unable to enumerate USB device on port 7
[175324.698113] hub 2-1:1.0: cannot disable port 7 (err = -19)
[175324.698118] hub 2-1:1.0: hub_port_status failed (err = -19)
[175324.698129] usb 2-1: USB disconnect, device number 2
[175324.698134] usb 2-1.3: USB disconnect, device number 3
[175324.698138] usb 2-1.3.1: USB disconnect, device number 7
[175324.699098] scsi: killing requests for dead queue
[175324.699469] usb 2-1.3.2: USB disconnect, device number 8
[175324.700504] usb 2-1.4: USB disconnect, device number 4
[175324.753927] usb 2-1.5: USB disconnect, device number 5
[175324.783162] scsi: killing requests for dead queue
[175324.783305] usb 2-1.6: USB disconnect, device number 6
[175324.783307] usb 2-1.6.1: USB disconnect, device number 9
[175324.783309] usb 2-1.6.1.1: USB disconnect, device number 10
[175324.783507] scsi: killing requests for dead queue
[175324.783684] scsi: killing requests for dead queue
[175324.783840] usb 2-1.6.1.4: USB disconnect, device number 11

At this point, all USB attached devices become unusable.  The system is otherwise up and running -- I can log in remotely, or connect a PS/2 keyboard, but there does not appear to be a way to revice USB connectivity other than rebooting.

I am running kernel 3.1.1-1.fc16.x86_64.

Comment 1 Josh Boyer 2012-03-01 16:00:28 UTC
Odd.  Seems like an IOMMU issue on your machine.  We disabled the intel IOMMU by default in the 3.1.5 kernel so you shouldn't be seeing that any longer.

I'm going to close this bug out for now.  If you are seeing this with the 3.2.7 or newer kernel, please reopen this and attach the full dmesg from when the problem happens.


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