[TRACKING] USB-A an ongoing problem?

I appreciate the update. If you’re not already, let’s get this into a ticket.

1 Like

Not sure if this is the same issue, but I’m also getting

kernel: xhci_hcd 0000:c1:00.3: Refused to change power state from D0 to D3hot
kernel: xhci_hcd 0000:c1:00.3: Refused to change power state from D0 to D3hot
kernel: xhci_hcd 0000:c1:00.3: Refused to change power state from D0 to D3hot
kernel: xhci_hcd 0000:c1:00.3: Refused to change power state from D0 to D3hot

spam in my logs on my Framework 13 AMD.

It was happening when I had an HDMI module in my front left port. Removing it stopped the messages. I moved a USB module to the front left, and the HDMI module to the front right port, and so far everything seems fine without the messages.

Not ideal since I’d prefer the HDMI port on the left side, but workable for now. Also in case it’s helpful, the two back ports are USB-C.

1 Like

@shazow I have the same issue, but only after a “powertop --auto-tune” run… if i restore the setting for the corresponding device, the messages stop occuring…

edit: it happens here when i have a usb-a module in the front left port, instead of hdmi, like you’re running…

1 Like

Which distro and kernel?

Which distro and kernel?

NixOS with 6.6.8 Kernel.

Which distro and kernel?

Same here, NixOS and 6.6.8 Kernel.

I did stumble on this diagram which says that HDMI should not be in slot 2 (front left), which is where I was having the issue: Expansion Card Functionality on Framework Laptop 13 (AMD Ryzen™ 7040 Series)

Jumping in here to report similar issues that have just started for me. I’ve got an intel 11th gen, running Fedora 39 with 6.6.9 linux kernel. I am on BIOS 3.17, waiting on UEFI installer for 3.19. I’ve just opened a ticket, and posting here to add to the rabble and track updates.

For a few more details, it seems like this is more dependent on the device than the specific port location or the actual USB-A expansion port. I’ve got a Sandisk 3.2 USB-A drive that works via the expansion port just fine, no matter the expansion port’s position, and it also works when I use an adapter to plug it into any of my USB-C ports. However, several other USB-A devices (a wi-fi dongle, a serial connector to an arduino board, other USB-A storage devices) consistently don’t work no matter if they’re directly in the USB-A expansion port or USB-C (with adapter).

I also confirmed the USB-A expansion port works just fine plugged into my desktop. Based on everything I’ve seen so far my best guess is this is related to how the mainboard is handling USB, but I’m no hardware/firmware expert ¯_(ツ)_/¯

@Matt_Hartley FWIW, i’m now on linux 6.7.0 and the problem as described in [1] appears to have gone. That is, i’m running the updated kernel for a few hours now, haven’t yet resumed from suspend, etc… But so far it’s looking good… Furthermore, the front right USB-A port now appears to recognize some devices which, iirc, it did not before ( in this specific port)…

[1] [TRACKING] USB-A an ongoing problem? - #36 by sydney

1 Like

Appreciate the update and delighted to hear you found a path forward.

I batch write lots of video files to external drives on a weekly basis, usually around 140GB, and occasionally transfer between external drives up to 1TB. I had tons of issues with drives disconnecting or dropping speeds to dismal levels (had some help from my post here).

USB Tree View helped me figure out that one brand of external drive enclosure wasn’t communicating properly, and wouldn’t get the correct amount of power as a result, but properly working drives had connection issues too. However, using a powered USB hub has solved all my issues on my batch 5 framework 13. Sure, the problem is still there, but at least there is a reliable work around.

That was the exact setup I had:
HDMI lower left and USB-A lower right.

Swapped them and the error stopped.
I’m on NixOS with kernel 6.6.30

I’m running Arch Linux on an AMD 7840U. With kernel 6.9.1-zen (and regular 6.9.1), I get this exact error whenever I try to just power a device with a USB-A port, no matter where it is placed. Devices like flash drives are recognized and work just fine, but this error shows up whenever I want to charge a device or if I want to power an SBC.

Everything works perfectly if I use linux-lts (6.6.31-1-lts)

I think I have the issue you are describing here. I have the USB A port connected to a fully populated 7 port USB hub with an auxiliary power supply. The current draw from the framework-16 is 0.19 to 0.22 milliamps.

jeffs@frmwk16:~$ lsusb --tree
/:  Bus 08.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 10000M
/:  Bus 07.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 480M
/:  Bus 06.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 10000M
/:  Bus 05.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 480M
/:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 10000M
/:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 480M
    |__ Port 1: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M
    |__ Port 1: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M
/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 10000M
    |__ Port 2: Dev 2, If 0, Class=Hub, Driver=hub/3p, 10000M
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/5p, 480M
    |__ Port 1: Dev 2, If 0, Class=, Driver=, 12M
    |__ Port 1: Dev 2, If 1, Class=Human Interface Device, Driver=usbhid, 12M
    |__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/4p, 480M
        |__ Port 3: Dev 34, If 0, Class=Hub, Driver=hub/4p, 480M
            |__ Port 1: Dev 35, If 0, Class=Hub, Driver=hub/4p, 480M
                |__ Port 2: Dev 37, If 0, Class=Hub, Driver=hub/4p, 480M
                |__ Port 4: Dev 40, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M
            |__ Port 2: Dev 36, If 0, Class=Hub, Driver=hub/4p, 480M
                |__ Port 3: Dev 39, If 0, Class=Hub, Driver=hub/4p, 480M
                |__ Port 4: Dev 42, If 0, Class=Printer, Driver=usblp, 12M
            |__ Port 3: Dev 38, If 0, Class=Hub, Driver=hub/4p, 480M
                |__ Port 1: Dev 43, If 0, Class=Hub, Driver=hub/4p, 480M
                    |__ Port 1: Dev 47, If 0, Class=, Driver=, 480M
                    |__ Port 1: Dev 47, If 1, Class=, Driver=, 480M
                    |__ Port 1: Dev 47, If 2, Class=, Driver=, 480M
                    |__ Port 1: Dev 47, If 3, Class=Mass Storage, Driver=usb-storage, 480M
                    |__ Port 2: Dev 50, If 0, Class=Audio, Driver=snd-usb-audio, 12M
                    |__ Port 2: Dev 50, If 1, Class=Audio, Driver=snd-usb-audio, 12M
                    |__ Port 2: Dev 50, If 2, Class=Audio, Driver=snd-usb-audio, 12M
                    |__ Port 2: Dev 50, If 3, Class=Human Interface Device, Driver=usbhid, 12M
                |__ Port 2: Dev 46, If 0, Class=Video, Driver=uvcvideo, 480M
                |__ Port 2: Dev 46, If 1, Class=Video, Driver=uvcvideo, 480M
                |__ Port 2: Dev 46, If 2, Class=Audio, Driver=snd-usb-audio, 480M
                |__ Port 2: Dev 46, If 3, Class=Audio, Driver=snd-usb-audio, 480M
            |__ Port 4: Dev 41, If 0, Class=Hub, Driver=hub/4p, 480M
    |__ Port 3: Dev 4, If 0, Class=Hub, Driver=hub/3p, 480M
    |__ Port 4: Dev 5, If 0, Class=Hub, Driver=hub/4p, 480M
        |__ Port 1: Dev 7, If 0, Class=Vendor Specific Class, Driver=, 12M
        |__ Port 3: Dev 8, If 0, Class=Human Interface Device, Driver=usbhid, 12M
        |__ Port 3: Dev 8, If 1, Class=Human Interface Device, Driver=usbhid, 12M
        |__ Port 3: Dev 8, If 2, Class=Human Interface Device, Driver=usbhid, 12M
        |__ Port 3: Dev 8, If 3, Class=Human Interface Device, Driver=usbhid, 12M
    |__ Port 5: Dev 6, If 0, Class=Wireless, Driver=btusb, 480M
    |__ Port 5: Dev 6, If 1, Class=Wireless, Driver=btusb, 480M
    |__ Port 5: Dev 6, If 2, Class=Wireless, Driver=, 480M
jeffs@frmwk16:~$ type or paste code here

If I attempt to boot with the 7 port hub plugged in, nothing happens. No error message, no boot text, nothing. However, if I unplug the hub from the framework-16, there is a normal boot. If I plug in the hub after linux has started but before mate or gnome start, then the USB bus starts normally.

[Thu Jun 13 17:24:38 2024] usb 1-2.3: new high-speed USB device number 34 using xhci_hcd
[Thu Jun 13 17:24:38 2024] usb 1-2.3: New USB device found, idVendor=214b, idProduct=7250, bcdDevice= 1.00
[Thu Jun 13 17:24:38 2024] usb 1-2.3: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[Thu Jun 13 17:24:38 2024] usb 1-2.3: Product: USB2.0 HUB
[Thu Jun 13 17:24:38 2024] hub 1-2.3:1.0: USB hub found
[Thu Jun 13 17:24:38 2024] usb 1-2.3.1: new high-speed USB device number 35 using xhci_hcd
[Thu Jun 13 17:24:39 2024] usb 1-2.3.1: New USB device found, idVendor=214b, idProduct=7250, bcdDevice= 1.00
[Thu Jun 13 17:24:39 2024] usb 1-2.3.1: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[Thu Jun 13 17:24:39 2024] usb 1-2.3.1: Product: USB2.0 HUB
[Thu Jun 13 17:24:39 2024] hub 1-2.3.1:1.0: USB hub found
[Thu Jun 13 17:24:39 2024] usb 1-2.3.2: new high-speed USB device number 36 using xhci_hcd
[Thu Jun 13 17:24:39 2024] usb 1-2.3.2: New USB device found, idVendor=05e3, idProduct=0608, bcdDevice= 9.01
[Thu Jun 13 17:24:39 2024] usb 1-2.3.2: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[Thu Jun 13 17:24:39 2024] usb 1-2.3.2: Product: USB2.0 Hub
[Thu Jun 13 17:24:39 2024] hub 1-2.3.2:1.0: USB hub found
[Thu Jun 13 17:24:39 2024] usb 1-2.3.1.2: new high-speed USB device number 37 using xhci_hcd
[Thu Jun 13 17:24:39 2024] usb 1-2.3.1.2: New USB device found, idVendor=0451, idProduct=8043, bcdDevice= 1.00
[Thu Jun 13 17:24:39 2024] usb 1-2.3.1.2: New USB device strings: Mfr=0, Product=0, SerialNumber=1
[Thu Jun 13 17:24:39 2024] usb 1-2.3.1.2: SerialNumber: 7B0108517C41
[Thu Jun 13 17:24:39 2024] hub 1-2.3.1.2:1.0: USB hub found
[Thu Jun 13 17:24:39 2024] usb 1-2.3.3: new high-speed USB device number 38 using xhci_hcd
[Thu Jun 13 17:24:39 2024] usb 1-2.3.3: New USB device found, idVendor=1a40, idProduct=0101, bcdDevice= 1.11
[Thu Jun 13 17:24:39 2024] usb 1-2.3.3: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[Thu Jun 13 17:24:39 2024] usb 1-2.3.3: Product: USB 2.0 Hub
[Thu Jun 13 17:24:39 2024] hub 1-2.3.3:1.0: USB hub found
[Thu Jun 13 17:24:39 2024] usb 1-2.3.2.3: new high-speed USB device number 39 using xhci_hcd
[Thu Jun 13 17:24:39 2024] usb 1-2.3.2.3: New USB device found, idVendor=05e3, idProduct=0608, bcdDevice= 9.01
[Thu Jun 13 17:24:39 2024] usb 1-2.3.2.3: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[Thu Jun 13 17:24:39 2024] usb 1-2.3.2.3: Product: USB2.0 Hub
[Thu Jun 13 17:24:39 2024] hub 1-2.3.2.3:1.0: USB hub found
[Thu Jun 13 17:24:39 2024] usb 1-2.3.1.4: new low-speed USB device number 40 using xhci_hcd
[Thu Jun 13 17:24:40 2024] usb 1-2.3.1.4: New USB device found, idVendor=046d, idProduct=c077, bcdDevice=72.00
[Thu Jun 13 17:24:40 2024] usb 1-2.3.1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[Thu Jun 13 17:24:40 2024] usb 1-2.3.1.4: Product: USB Optical Mouse
[Thu Jun 13 17:24:40 2024] usb 1-2.3.1.4: Manufacturer: Logitech
[Thu Jun 13 17:24:40 2024] usb 1-2.3.4: new high-speed USB device number 41 using xhci_hcd
[Thu Jun 13 17:24:40 2024] input: Logitech USB Optical Mouse as /devices/pci0000:00/0000:00:08.1/0000:c1:00.3/usb1/1-2/1-2.3/1-2.3.1/1-2.3.1.4/1-2.3.1.4:1.0/0003:046D:C077.000A/input/input18
[Thu Jun 13 17:24:40 2024] hid-generic 0003:046D:C077.000A: input,hidraw6: USB HID v1.11 Mouse [Logitech USB Optical Mouse] on usb-0000:c1:00.3-2.3.1.4/input0
[Thu Jun 13 17:24:40 2024] usb 1-2.3.4: New USB device found, idVendor=2148, idProduct=7022, bcdDevice= 1.00
[Thu Jun 13 17:24:40 2024] usb 1-2.3.4: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[Thu Jun 13 17:24:40 2024] usb 1-2.3.4: Product: USB2.0 HUB
[Thu Jun 13 17:24:40 2024] hub 1-2.3.4:1.0: USB hub found
[Thu Jun 13 17:24:40 2024] usb 1-2.3.2.4: new full-speed USB device number 42 using xhci_hcd
[Thu Jun 13 17:24:40 2024] usb 1-2.3.3.1: new high-speed USB device number 43 using xhci_hcd
[Thu Jun 13 17:24:40 2024] usb 1-2.3.2.4: New USB device found, idVendor=04f9, idProduct=000d, bcdDevice= 1.00
[Thu Jun 13 17:24:40 2024] usb 1-2.3.2.4: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[Thu Jun 13 17:24:40 2024] usblp0: Disabling reads from problematic bidirectional printer
[Thu Jun 13 17:24:40 2024] usblp 1-2.3.2.4:1.0: usblp3: USB Unidirectional printer dev 42 if 0 alt 0 proto 2 vid 0x04F9 pid 0x000D
[Thu Jun 13 17:24:40 2024] usb 1-2.3.3.1: New USB device found, idVendor=1a40, idProduct=0101, bcdDevice= 1.11
[Thu Jun 13 17:24:40 2024] usb 1-2.3.3.1: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[Thu Jun 13 17:24:40 2024] usb 1-2.3.3.1: Product: USB 2.0 Hub
[Thu Jun 13 17:24:41 2024] hub 1-2.3.3.1:1.0: USB hub found
[Thu Jun 13 17:24:42 2024] usb 1-2.3.4-port1: Cannot enable. Maybe the USB cable is bad?
[Thu Jun 13 17:24:43 2024] usb 1-2.3.4-port1: Cannot enable. Maybe the USB cable is bad?
[Thu Jun 13 17:24:43 2024] usb 1-2.3.4-port1: attempt power cycle
[Thu Jun 13 17:24:43 2024] usb 1-2.3.3.2: new high-speed USB device number 46 using xhci_hcd
[Thu Jun 13 17:24:43 2024] usb 1-2.3.3.2: New USB device found, idVendor=046d, idProduct=0991, bcdDevice= 0.08
[Thu Jun 13 17:24:43 2024] usb 1-2.3.3.2: New USB device strings: Mfr=0, Product=0, SerialNumber=2
[Thu Jun 13 17:24:43 2024] usb 1-2.3.3.2: SerialNumber: 8251C524
[Thu Jun 13 17:24:43 2024] usb 1-2.3.3.2: Found UVC 1.00 device <unnamed> (046d:0991)
[Thu Jun 13 17:24:43 2024] usb 1-2.3.3.1.1: new high-speed USB device number 47 using xhci_hcd
[Thu Jun 13 17:24:43 2024] usb 1-2.3.3.1.1: config 1 interface 1 altsetting 0 has a duplicate endpoint with address 0x81, skipping
[Thu Jun 13 17:24:43 2024] usb 1-2.3.3.1.1: config 1 interface 1 altsetting 0 has a duplicate endpoint with address 0x1, skipping
[Thu Jun 13 17:24:43 2024] usb 1-2.3.3.1.1: config 1 interface 1 altsetting 1 has a duplicate endpoint with address 0x81, skipping
[Thu Jun 13 17:24:43 2024] usb 1-2.3.3.1.1: config 1 interface 1 altsetting 1 has a duplicate endpoint with address 0x1, skipping
[Thu Jun 13 17:24:43 2024] usb 1-2.3.3.1.1: New USB device found, idVendor=1d5c, idProduct=2000, bcdDevice= 2.00
[Thu Jun 13 17:24:43 2024] usb 1-2.3.3.1.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[Thu Jun 13 17:24:43 2024] usb-storage 1-2.3.3.1.1:1.3: USB Mass Storage device detected
[Thu Jun 13 17:24:43 2024] scsi host0: usb-storage 1-2.3.3.1.1:1.3
[Thu Jun 13 17:24:44 2024] usb 1-2.3.3.2: set resolution quirk: cval->res = 384
[Thu Jun 13 17:24:45 2024] usb 1-2.3.4-port1: Cannot enable. Maybe the USB cable is bad?
[Thu Jun 13 17:24:46 2024] usblp3: removed
[Thu Jun 13 17:24:46 2024] usblp0: Disabling reads from problematic bidirectional printer
[Thu Jun 13 17:24:46 2024] usb 1-2.3.4-port1: Cannot enable. Maybe the USB cable is bad?
[Thu Jun 13 17:24:46 2024] usb 1-2.3.4-port1: unable to enumerate USB device
[Thu Jun 13 17:24:46 2024] usblp 1-2.3.2.4:1.0: usblp3: USB Unidirectional printer dev 42 if 0 alt 0 proto 2 vid 0x04F9 pid 0x000D
[Thu Jun 13 17:24:46 2024] usb 1-2.3.3.1.2: new full-speed USB device number 50 using xhci_hcd
[Thu Jun 13 17:24:46 2024] usb 1-2.3.3.1.2: New USB device found, idVendor=0d8c, idProduct=013c, bcdDevice= 1.00
[Thu Jun 13 17:24:46 2024] usb 1-2.3.3.1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[Thu Jun 13 17:24:46 2024] usb 1-2.3.3.1.2: Product: USB PnP Sound Device
[Thu Jun 13 17:24:46 2024] usb 1-2.3.3.1.2: Manufacturer: C-Media Electronics Inc.      
[Thu Jun 13 17:24:46 2024] input: C-Media Electronics Inc.       USB PnP Sound Device as /devices/pci0000:00/0000:00:08.1/0000:c1:00.3/usb1/1-2/1-2.3/1-2.3.3/1-2.3.3.1/1-2.3.3.1.2/1-2.3.3.1.2:1.3/0003:0D8C:013C.000B/input/input19
[Thu Jun 13 17:24:46 2024] hid-generic 0003:0D8C:013C.000B: input,hidraw7: USB HID v1.00 Device [C-Media Electronics Inc.       USB PnP Sound Device] on usb-0000:c1:00.3-2.3.3.1.2/input3
[Thu Jun 13 17:25:19 2024] usb 1-2.3.3.1.1: reset high-speed USB device number 47 using xhci_hcd
[Thu Jun 13 17:25:51 2024] usb 1-2.3.3.1.1: reset high-speed USB device number 47 using xhci_hcd
jeffs@frmwk16:~$ 

What other information would be helpful for troubleshooting? Many thanks.

Do the same limitations apply to the Intel 12th gen board? Interesting that this article is specific to the AMD release.

@Jeff_Silverman
Does the problem change depending on which of the 6 slots on the FW16 you plug the “fully populated 7 port USB hub” into? I.e. in some slots it works, in others it fails.

Slot 1, 2, 3, 4, 5, or 6 ?

Sorry for the delay in getting back to you. I try the experiment tomorrow.

Jeff

I am trying to reproduce the problem and failing. What I do get is that there is an overcurrent condition, but that’s if I grossly overload it. My understanding of the USB standard is that it will shut down a port if it attempts to draw too much current. I know that the system will boot properly if I draw .40 amps.

At the moment, I have my 7-port USB hub plugged into the slot closest to me on the left side. The HDMI adapter is plugged into the middle socket in the left side.
The power is plugged into the right side on the slot farthest away from me. All of the other sockets are empty. How are the slots numbered, please?

For numbering of slots:
Framework 13 slots:

Framework 16 slots:

This, or similar issue just hit me as well, so adding to the flock, 3.19 BIOS.

  • AMD 7640
  • Switching expansion slot does not change the observed behaviour
  • Does not seem to happen on non-Framework computers
  • Used “Other World Computing Thunderbolt Hub”
  • Just created a ticket with more details as suggested

Happens on both Alpine Linux and Chimera, messages like

xhci_hcd 0000:c1:00.3: Refused to change power state from D0 to D3hot
ucsi_acpi USBC000:00: unknown error 0
ucsi_acpi USBC000:00: UCSI_GET_PDOS failed (-5)

are seen when connecting an USB device (in this case, a portable display) fails.

I have one of four acting up but, also the first person to seriously use it and ride it all day long. i gave them proper usb a to c cable vs a micro to c adapter and micro cable they were using but, the issue can happen with a myriad of other devices they use. none of the other FW16s have been acting up. swapping cards around fixes it for a short period of time.

just delving in to this. i hope its not a mobo hardware issue that isn’t discovered till after warranty expires. (with dell i can get 4 year warranty just can’t buy new dell batteries after 4 years)

fw16 latest bios as of several weeks ago when i deployed it.

EDIT: I have another user with similar setup trying to duplicate the first users usb issues. both have a FW16. the one trying to reproduce the issue has not had issues before.