USB 3.0 ports aren't working properly

Lindenk · 2016-11-17 21:30:28

Hello!

So I have 2 possibly related problems that I can't seem to solve.

I have 2 usb 3.0 buses (bus2 and bus3) on my motherboard with two ports each. Both show up when using `lsusb` however bus2 is showing as 2.0 (bus2, device 1, 2.0 root hub) and I'm only getting usb 2.0 speeds from it's ports. The second problem is bus3, which does show as a usb 3.0 hub, only provides power to devices connected to it's ports, but nothing connected to it registers with `lsusb` or `dmesg`. I'm a bit stumped on what else to try.

TLDR;

Problem 1: USB Bus 2 should be usb 3.0, but is only being registered as a 2.0 hub.

Problem 2: USB Bus 3 only provides power and no connected devices seem to be registered with the system.

Other info

- Bus 2 seems to be using the same xhci_hcd driver as Bus 3
- `lsusb -v 2:1` shows iSerial as `0000:08:00.0` which is the same device number for Bus 3
- Only `0000:08:00.0` shows as a device under `/sys/bus/pci/drivers/xhci_hcd` and unbinding it removes both buses
- `rmmod`ing `xhci_hcd` remove both buses
- Bus 2 is on the motherboard's rear IO panel while Bus 3 is a header on the motherboard connected to the case
- Both Buses seem to be using the usb controller `ASMedia Technology Inc. ASM1042 SuperSpeed USB Host Controller`, according to lspci

Motherboard info (output of `dmidecode -t 2`)

Getting SMBIOS data from sysfs.
SMBIOS 2.7 present.

Handle 0x0002, DMI type 2, 15 bytes
Base Board Information
	Manufacturer: ASUSTeK COMPUTER INC.
	Product Name: M5A99FX PRO R2.0
	Version: Rev 1.xx
	Serial Number: 130511529300573
	Asset Tag: To be filled by O.E.M.
	Features:
		Board is a hosting board
		Board is replaceable
	Location In Chassis: To be filled by O.E.M.
	Chassis Handle: 0x0003
	Type: Motherboard
	Contained Object Handles: 0

Last edited by Lindenk (2016-11-17 21:35:17)

seth · 2016-11-18 21:56:23

Did you ask dmesg about the situation?

Lindenk · 2016-11-18 22:38:40

Yes. dmesg doesn't log anything being connected to bus 3, but does log bus 2 (surprisingly using the xhci_hcd driver). Everything connected to bus 2 ports still runs at usb 2.0 speeds.

seth · 2016-11-19 08:46:15

"dmesg | grep hci" reveals no errors at all?

Try to blacklist xchi_hcd (ensure it's not loaded from the initrmfs) and whether that "revives" bus 3 (on USB 2.0, of course)
If so, there're various quirks, try passing "quirks=4294967295" to the module (setting all bits) and sometimes usb issues are caused by the pci bus, try "iommu=soft" on the kenel - but that's all voodoo.

Did you try the HW on some other OS to ensure it's not a HW issue; for this - as general troubles w/ usb 3.0 - is rather common :-(

Arch Linux

#1 2016-11-17 21:30:28