Failed to re-enumerate USB3.0 plug

[Mark_Huang]

Hi

We are running a restart test. The periodic procedure is as below.
1. boot into Windows OS
2. auto-run BurnInTest for 5 minutes, then stop and exit.
3. shutdown the system and then boot up

= Test environment =
OS: Win Server 2019 64bit
Test Program: BurnInTest 10.2 1010 (64-bit)
USB Plug: Firmware 2.7, Driver 1.2.3
Duty Cycle: 50%
Test items: CPU, RAM, USB

After running hours(could be 1 hour or 8 hours), it shows the error message (Failed to re-enumerate USB3.0 plug) for a few times.
I can't find the description for this error in the manual.

Would you advise what does this error mean?
Thanks a lot.

[David (PassMark)]

USB 3.0 enumeration is the process where a host discovers and configures a newly connected USB device. The key steps include:

1. Device connection detection via VBUS power and differential pair connection
2. Reset and speed negotiation (SuperSpeed uses separate differential pairs). Part of this step is link training sequences.
3. Device descriptor request to identify basic information
4. Address assignment to uniquely identify the device
5. Configuration descriptor request to understand device capabilities
6. Configuration selection by the host
7. Interface and endpoint setup for data transfer

So a failure of any of these steps can result in the device failing to re-enumerate. Several of these steps also have tight timing constraints. So the device or host failing to response quickly enough can also cause a failure. Software issues (like missing device drivers) can also cause problems, but that is less likely here as it works most of the time.

The really get to the bottom of it a protocol trace on the USB bus would normally be required.

What USB host controller are you using?

[Mark_Huang]

We are using this CPU Intel® Xeon® D-1746TER Processor as the USB3.0 host.

Unfortunately we don't have an USB protocol analyzer to debug.
Does the loopback driver support Win Server 2019? (I can't see it in the supported list.)

[David (PassMark)]

The CPU doesn't contain the USB host controller. It is part of the motherboard chipset, or when a lot of ports are required, or higher speed ports, a separate controller chip on the motherboard is used. (For Intel this is sometimes called the PCH, Platform Controller Hub chipset)

We are not aware of any problems with Windows Server 2019.

Update: Xeon D are system on a chip CPUs, so they do contain some of the PCH functionality. So might be worth checking if there is a device driver update available.