I'm having strange issues with a USB controller card.
It is picked up by lspci as:
Code:
03:00.0 USB controller: Fresco Logic FL1100 USB 3.0 Host Controller (rev 10)
It delivers power to devices plugged into it. Power lights turn on for attached devices. That may be because the card has a SATA power input.
Attached devices do NOT show up under lsusb. I haven't been able to find any error messages from the kernel when a device is plugged in; though it's *possible* that I could be looking the wrong places for the error messages. I, like probably most users, don't have a fully accurate understanding of which messages go to which logs.
From dmesg I get:
Code:
$ dmesg -H | grep 0000:03:00.0
[ +0.000050] pci 0000:03:00.0: [1b73:1100] type 00 class 0x0c0330
[ +0.000020] pci 0000:03:00.0: reg 0x10: [mem 0xdfb00000-0xdfb0ffff 64bit]
[ +0.000012] pci 0000:03:00.0: reg 0x18: [mem 0xdfb11000-0xdfb11fff 64bit]
[ +0.000011] pci 0000:03:00.0: reg 0x20: [mem 0xdfb10000-0xdfb10fff 64bit]
[ +0.000051] pci 0000:03:00.0: supports D1
[ +0.000003] pci 0000:03:00.0: PME# supported from D0 D1 D3hot
[ +0.000247] pci 0000:03:00.0: Adding to iommu group 28
[ +0.002742] xhci_hcd 0000:03:00.0: xHCI Host Controller
[ +0.002533] xhci_hcd 0000:03:00.0: new USB bus registered, assigned bus number 3
[ +0.002721] xhci_hcd 0000:03:00.0: hcc params 0x200071e1 hci version 0x100 quirks 0x0000000000000450
[ +0.002689] usb usb3: SerialNumber: 0000:03:00.0
[ +0.002794] xhci_hcd 0000:03:00.0: xHCI Host Controller
[ +0.002627] xhci_hcd 0000:03:00.0: new USB bus registered, assigned bus number 4
[ +0.002650] xhci_hcd 0000:03:00.0: Host supports USB 3.0 SuperSpeed
[ +0.002761] usb usb4: SerialNumber: 0000:03:00.0
[ +10.274399] xhci_hcd 0000:03:00.0: xHCI host not responding to stop endpoint command.
[ +0.004493] xhci_hcd 0000:03:00.0: xHCI host controller not responding, assume dead
[ +0.004425] xhci_hcd 0000:03:00.0: HC died; cleaning up
From google-fu, I know that the "endpoint command" line can have something to do with power management. This particular timestamp occurs during boot. It's probably some sort of test that results in the controller failing and being disabled?
Some relevant backstory. I previously had a different USB 3.0 controller card installed. It was also an FL1100 chipset. It worked for years. I wasn't sure exactly when the card had failed since I may not have noticed it immediately. I made the mistake of assuming it has a hardware failure, so I replaced the card. I didn't shop for a card with the same chipset; that was accidental. I just shopped for a card with similar specs, and this is apparently a really common chipset. Still assuming it was a hardware failure, I swapped the cards first. Same problem. Next I thought it might be the motherboard, so I swapped the new card into a known good PCIE slot. Same problem. So now I've got two similar controller cards. They probably both work just fine. The motherboard doesn't seem to be the cause. It must actually be software.
Ubuntu 20.04 LTS. Kernel 5.4.0 if that helps. Cards with this chipset are reported working by other Ubuntu 20.04 users. That's probably not important in my case because this card used to work for me too.
The only recent change I've found via searching that might be even remotely related is:
https://lkml.kernel.org/lkml/2022010...ndation.org/#r
Any ideas on anything else to try?
