Arch Linux

Fingel

Member

Registered: 2009-02-28

Posts: 98

Usb3 Ports dead after resume from suspend

Hello all,
I am running Arch Linux with kernel 2.6.37-ARCH on a Lenovo W510 that has 2 usb3 ports. Upon waking from resume, the usb3 ports are dead, although the regular usb2 ports work fine. Dmesg produces some interesting output, notably the line that reads:

usb usb3: root hub lost power or was reset

Here is the rest:

ACPI: Waking up from system sleep state S3
ehci_hcd 0000:00:1a.0: restoring config space at offset 0xf (was 0x400, writing 0x40b)
ehci_hcd 0000:00:1a.0: restoring config space at offset 0x4 (was 0x0, writing 0xf2628000)
ehci_hcd 0000:00:1a.0: restoring config space at offset 0x1 (was 0x2900000, writing 0x2900102)
ehci_hcd 0000:00:1a.0: power state changed by ACPI to D0
ehci_hcd 0000:00:1a.0: power state changed by ACPI to D0
ehci_hcd 0000:00:1d.0: restoring config space at offset 0xf (was 0x400, writing 0x40b)
ehci_hcd 0000:00:1d.0: restoring config space at offset 0x4 (was 0x0, writing 0xf2628400)
ehci_hcd 0000:00:1d.0: restoring config space at offset 0x1 (was 0x2900000, writing 0x2900102)
ehci_hcd 0000:00:1d.0: power state changed by ACPI to D0
ehci_hcd 0000:00:1d.0: power state changed by ACPI to D0
ahci 0000:00:1f.2: restoring config space at offset 0x1 (was 0x2b00007, writing 0x2b00407)
nvidia 0000:01:00.0: restoring config space at offset 0x3 (was 0x800010, writing 0x800000)
nvidia 0000:01:00.0: restoring config space at offset 0x1 (was 0x100107, writing 0x100007)
HDA Intel 0000:01:00.1: restoring config space at offset 0x1 (was 0x100106, writing 0x100102)
iwlagn 0000:03:00.0: restoring config space at offset 0x1 (was 0x100106, writing 0x100506)
xhci_hcd 0000:0f:00.0: restoring config space at offset 0xf (was 0x100, writing 0x10b)
xhci_hcd 0000:0f:00.0: restoring config space at offset 0x4 (was 0x4, writing 0xf2200004)
xhci_hcd 0000:0f:00.0: restoring config space at offset 0x3 (was 0x0, writing 0x10)
xhci_hcd 0000:0f:00.0: restoring config space at offset 0x1 (was 0x100000, writing 0x100502)
PM: early resume of devices complete after 57.965 msecs
pci 0000:00:03.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
pci 0000:00:03.0: setting latency timer to 64
HDA Intel 0000:00:1b.0: PCI INT B -> GSI 17 (level, low) -> IRQ 17
HDA Intel 0000:00:1b.0: setting latency timer to 64
pci 0000:00:1c.0: PCI INT A -> GSI 20 (level, low) -> IRQ 20
pci 0000:00:1c.1: PCI INT B -> GSI 21 (level, low) -> IRQ 21
pci 0000:00:1c.0: setting latency timer to 64
pci 0000:00:1c.3: PCI INT D -> GSI 23 (level, low) -> IRQ 23
pci 0000:00:1c.1: setting latency timer to 64
pci 0000:00:1c.3: setting latency timer to 64
pci 0000:00:1c.4: PCI INT A -> GSI 20 (level, low) -> IRQ 20
pci 0000:00:1c.6: PCI INT C -> GSI 22 (level, low) -> IRQ 22
pci 0000:00:1c.4: setting latency timer to 64
pci 0000:00:1c.7: PCI INT D -> GSI 23 (level, low) -> IRQ 23
pci 0000:00:1c.6: setting latency timer to 64
HDA Intel 0000:00:1b.0: irq 46 for MSI/MSI-X
pci 0000:00:1c.7: setting latency timer to 64
pci 0000:00:1e.0: setting latency timer to 64
HDA Intel 0000:01:00.1: PCI INT A -> GSI 16 (level, low) -> IRQ 16
ahci 0000:00:1f.2: setting latency timer to 64
sdhci-pci 0000:0d:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
HDA Intel 0000:01:00.1: setting latency timer to 64
e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
xhci_hcd 0000:0f:00.0: setting latency timer to 64
sdhci-pci 0000:17:00.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19
usb usb3: root hub lost power or was reset
sd 0:0:0:0: [sda] Starting disk
ehci_hcd 0000:00:1a.0: power state changed by ACPI to D0
ehci_hcd 0000:00:1d.0: power state changed by ACPI to D0
xhci_hcd 0000:0f:00.0: irq 47 for MSI/MSI-X
xhci_hcd 0000:0f:00.0: irq 48 for MSI/MSI-X
xhci_hcd 0000:0f:00.0: irq 49 for MSI/MSI-X
xhci_hcd 0000:0f:00.0: irq 50 for MSI/MSI-X
xhci_hcd 0000:0f:00.0: irq 51 for MSI/MSI-X
xhci_hcd 0000:0f:00.0: irq 52 for MSI/MSI-X
xhci_hcd 0000:0f:00.0: irq 53 for MSI/MSI-X
xhci_hcd 0000:0f:00.0: irq 54 for MSI/MSI-X
ehci_hcd 0000:00:1a.0: power state changed by ACPI to D0
ehci_hcd 0000:00:1a.0: PCI INT D -> GSI 23 (level, low) -> IRQ 23
ehci_hcd 0000:00:1a.0: setting latency timer to 64
ehci_hcd 0000:00:1d.0: power state changed by ACPI to D0
ehci_hcd 0000:00:1d.0: PCI INT D -> GSI 19 (level, low) -> IRQ 19
ehci_hcd 0000:00:1d.0: setting latency timer to 64
firewire_ohci 0000:17:00.3: irq 56 for MSI/MSI-X
firewire_core: skipped bus generations, destroying all nodes
usb 1-1.6: reset high speed USB device using ehci_hcd and address 5
ata5: SATA link down (SStatus 0 SControl 300)
ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata2.00: ACPI cmd e3/00:1f:00:00:00:a0 (IDLE) succeeded
ata2.00: ACPI cmd e3/00:02:00:00:00:a0 (IDLE) succeeded
ata6: SATA link down (SStatus 0 SControl 300)
ata2.00: ACPI cmd e3/00:1f:00:00:00:a0 (IDLE) succeeded
ata2.00: ACPI cmd e3/00:02:00:00:00:a0 (IDLE) succeeded
ata2.00: configured for UDMA/100
usb 1-1.3: reset full speed USB device using ehci_hcd and address 3
sdhci-pci 0000:17:00.0: Will use DMA mode even though HW doesn't fully claim to support it.
sdhci-pci 0000:17:00.0: setting latency timer to 64
sdhci-pci 0000:0d:00.0: Will use DMA mode even though HW doesn't fully claim to support it.
sdhci-pci 0000:0d:00.0: setting latency timer to 64
usb 2-1.8: reset full speed USB device using ehci_hcd and address 3
firewire_core: rediscovered device fw0
ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded
ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out
ata1.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out
ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded
ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out
ata1.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out
ata1.00: configured for UDMA/100
PM: resume of devices complete after 5625.718 msecs
PM: Finishing wakeup.

Can't seem to find anything relevant on google, anyone have any suggestions?
Thanks.

eldragon

Member

From: Buenos Aires

Registered: 2008-11-18

Posts: 1,029

Re: Usb3 Ports dead after resume from suspend

considering usb3 is quite new, id suggest you wait a bit for a fix if you dont feel confident enough to file a bug upstream.

you could try as a workaround, to rmmod the modules before suspend, and insert them again uppon awaking.

Fingel

Member

Registered: 2009-02-28

Posts: 98

Re: Usb3 Ports dead after resume from suspend

Thanks Eldragon, I was figuring it would be one of those "matter of time" issues. I figured I should post anyways, just so theres something out there on google so other people with the problem know they aren't alone. I'll post back if I ever find a solution/workaround.