xhci_hcd error

I can report that I'm not seeing the problem any more with 6.5.11-4

Edit: False alarm. It was running stable for about a day without the error but once again throwing the error.
 
Last edited:
Still no luck. I disabled the WIFI driver in Proxmox via blacklist. So the driver + firmware only loads from the VM.

I have no success. The driver can't enter Accesss Point mode.

So crazy. Same stick - same driver works on my Intel NUC (no proxmox). The stick also works with Pi/aarm64 and openwrt.
 
OMFG :)

It's working.... I added a 5€ USB Hub.

  1. It worked with Proxmox 7
  2. I have the feeling that the Ryzen / AMD / AM4 USB 3.1 Hub has some issues with the new Kernel (I can't prove it)
  3. I tried all bios settings that are possible.

Edit: I also had to blacklist the driver in proxmox:

Code:
#/etc/modprobe.d/mt76-blacklist.conf 
blacklist mt76x0u
blacklist mt76x0_common
blacklist mt76x02_usb
blacklist mt76_usb
blacklist mt76x02_lib
blacklist mt76


1705354923396.png
 
Last edited:
i am experiencing the same issue on a virtualized OpenWRT (VM) when Modem is passthrough USB 3. proxmox version is 8.1.4 , its a fresh reinstall, i used the same hardware setup on proxmox 7.x for a long time with no issue. after reading all the previous comments i am pretty sure we are dealing with a proxmox 8 bug affecting USB 3 passthrough. or it might be bug in Linux kernel. either way we need to submit a bug report and proxmox people should also take this seriously because USB passthrough is a key functionality in Virtual environment.
 
  • Like
Reactions: XabiX
Hello, I'm on Proxmox 8.1.4 and have a VM running OpenMediaVault on an Intel NUC. I have 4 HDDs in a USB 3.0 enclosure attached to a USB port on the NUC and passed through to the VM in Proxmox. Works great- except for when I initiate any high read/write activity between drives. So basically when transferring files between drives within the enclosure it causes the "xhci hcd error transfer event rb dma ptr not part of current td ep_index 2 comp_code 4" error and the system crashes. Does anyone have any suggestions?
 
Hi there,
As far as I know, Vmware workstations have a similar problem. If the host PC supports USB 3.0 and you have a client that only supports USB 2.0 like Windows XP, the only way to solve this problem is to use a USB 2.0 hub in between.

I'm having the same problem in Proxmox V8.1.10 (xhci_hcd 0000:01:1b.0: ERROR transfer event TRB DMA ptr not part of current TD ep_index 8 comp_code 13)

But my client is Debian Bookwork, which should support USB 3.0 with a USB 3.0 hub in between.
But after connecting the USB 2.0 hub, the messages disappear.
Unfortunately, I don't know of any software switch in Proxmox that does a downscaling to USB 2.0.
 
As I don't have this error on my other DM 800 G3's in the cluster, I thought I'd replace the Lenovo M700 giving this error.

Still same xchi_error. Really annoying.

It's impossible to run the 3D-printer control software (MainSail or OctoPrint), and a the service to running CNC control software (CNCjs) drops out every now and then... :/
 
So still no solution for this problem? just chiming in that I also have an openwrt VM with a usb modem being passed through and get the same xhci errors.
 

Attachments

  • Screenshot 2024-10-01 at 7.05.10 AM.png
    Screenshot 2024-10-01 at 7.05.10 AM.png
    714.9 KB · Views: 7
I saw that. what kind of usb hub did you use? just any usb 3.0 hub will work?
There is no generic answer to that question. If you have USB issues - there are no logical solutions!

I learned how to fix USB problems that makes no sense (because I do electronic music).

- Try a usb hub with power, without power, try 3 different ones.
- Try a cheap one - try one with 3 ports, one with 7 ports
- There are even hubs that have 3 USB3.0 ports and 4 USB 2.0 ports
- There are usb hubs of the same brand / model / case that have 7 ports and all 7 are USB 3.0 ports

> there is no answer to your question.

I have hardware, where a disk works with a PC - but not with a specific raspberry pi - but with a Mac and not with a recent PC Laptop. That makes no sense. It's usb.
 
There is no generic answer to that question. If you have USB issues - there are no logical solutions!

I learned how to fix USB problems that makes no sense (because I do electronic music).

- Try a usb hub with power, without power, try 3 different ones.
- Try a cheap one - try one with 3 ports, one with 7 ports
- There are even hubs that have 3 USB3.0 ports and 4 USB 2.0 ports
- There are usb hubs of the same brand / model / case that have 7 ports and all 7 are USB 3.0 ports

> there is no answer to your question.

I have hardware, where a disk works with a PC - but not with a specific raspberry pi - but with a Mac and not with a recent PC Laptop. That makes no sense. It's usb.
right. understood.
let me rephrase my question: did you use a usb3 hub or a usb2 hub as someone else mentioned:
"If the host PC supports USB 3.0 and you have a client that only supports USB 2.0 like Windows XP, the only way to solve this problem is to use a USB 2.0 hub in between."
 
right. understood.
let me rephrase my question: did you use a usb3 hub or a usb2 hub as someone else mentioned:

I can't answer your question.

I noticed - sometimes - x works - and y doesn't work.

There is no pattern, logic or initial guestimation.

I have an USB 3.0 WiFi Dongle and a USB 3.0 Hub in a USB 3.0 port on my proxmox PC. I use OpenWRT.

(Maybe the most recent OpenWRT fixes that problem - but I have no idea - I don't care / never tried) The Dongle/Wifi combo works - and I will never touch it.
 
  • Like
Reactions: wlewvia
Kudos for that but I'd say thats a workaround, not a solution.

Some dev Proxmox fix is still needed but I'm running the free community license so I can't complain
That is the wrong answer :)

Early 8.2.x Proxmox Versions had a big issue with the 6.8.x kernel.I begged here in the forums for help, to setup a custom kernel for proxmox. There are multiple projects fromt he past. Basically the pve kernel is an ubuntu kernel ("their patches") and proxmox added a few patches (that are usually not needed on homelab hardware).

Nobody cared - and - I don't work for charty / do donnations to the world (I support a lot of other opensource projects).

So again :) if you don't like my workaround - are you willing to put in sweat and tears and time and you skills to fix the problem by a custom kernel? Fun fact - I don't have the USB problems with a vanilla Debian 12 Kernel on the same hardware.

I bet - your answer is "no" for the request for a custom kernel :)


But thanks for not complaining.
 
Yes, I think you covered it all. :)
If I recall right, this started with Ubuntu 21 or 22.

My solution/workaround/forfeit was to not run Proxmox on that node.

Thanks for not taking it the wrong way.
 
Last edited: