Failed to re-enumerate USB3.0 plug

[Simon (PassMark)]

Hi Simon (PassMark),

Thanks for your support.

I have tried the debug Build. However it easily happens the BSoD as below.
In some cases, the error screen shows up after opening the program, before any test is executed.

The environment is as below.
Platform: Intel® Xeon® D-1746TER Processor
OS: Windows Server 2019 build 1809

I also tried to re-install a clean OS. It can also meet the error.

Can you give this build a try:
https://www.passmark.com/downloads/t...dbg_250618.exe

[David (PassMark)]

Pretty sure this is not related to the USB changes.

Can you post a debug log (or EMail it to us)
https://www.passmark.com/support/bitdebug.php

[Mark_Huang]

Hi Simon (PassMark),

Thanks for your support.

I have tried the debug Build. However it easily happens the BSoD as below.
In some cases, the error screen shows up after opening the program, before any test is executed.


The environment is as below.
Platform: Intel® Xeon® D-1746TER Processor
OS: Windows Server 2019 build 1809

I also tried to re-install a clean OS. It can also meet the error.

[Simon (PassMark)]

Hi David (PassMark),

I found another issue with BurnIn test v11. I think it could be a similar issue.
In BurnIn test v11, there is a new optional test(Enumeration Test) in USB test setting.

I have tried three platforms.(Intel® Xeon® D-1746TER Processor, AMD V2000, Intel® Core™ i5-1335UE Processor)
No matter with or without USB hub, all three platforms can meet the issue.
=> Once three or more USB3 loopback are connected, below errors tend to occur easily.

We are trying to get the data by protocol analyzer. But the file size would be very big. Is there a way to upload it?
Thanks.

Besides I found a weird behavior during the test running.
After entering Enumeration Loop phase, the middle S/N may be changed from time to time.(refer to below figures)
Is it normal?

It could happen below display. 2 of 3 becomes the same as 3 of 3.

https://vimeo.com/manage/videos/1092700462/811f904d5b

We were able to reproduce the issue - can you give below build a try which should address this:
https://www.passmark.com/downloads/t...dbg_250617.exe

[Mark_Huang]

We tried to download the file, but it's locked on Dropbox (so we don't have access to the file at the moment).

We'll attempt to reproduce the problem anyway.

Yes, I didn't set it open for all.
Please click the button "Request access". I will approve it.

[David (PassMark)]

We tried to download the file, but it's locked on Dropbox (so we don't have access to the file at the moment).

We'll attempt to reproduce the problem anyway.

[Mark_Huang]

Hi David (PassMark),

I captured the data with error (Data packet transmission failed) during Enumeration Loop test.
Please download it from https://www.dropbox.com/scl/fi/swsjq...=hbseac4o&dl=0
I was using Total Phase Beagle USB 5000 to capture the data.
Please download its software (Data Center Software) to view the data.

[Mark_Huang]

Hi David (PassMark),

I found another issue with BurnIn test v11. I think it could be a similar issue.
In BurnIn test v11, there is a new optional test(Enumeration Test) in USB test setting.

I have tried three platforms.(Intel® Xeon® D-1746TER Processor, AMD V2000, Intel® Core™ i5-1335UE Processor)
No matter with or without USB hub, all three platforms can meet the issue.
=> Once three or more USB3 loopback are connected, below errors tend to occur easily.



We are trying to get the data by protocol analyzer. But the file size would be very big. Is there a way to upload it?
Thanks.

Besides I found a weird behavior during the test running.
After entering Enumeration Loop phase, the middle S/N may be changed from time to time.(refer to below figures)
Is it normal?

It could happen below display. 2 of 3 becomes the same as 3 of 3.


https://vimeo.com/manage/videos/1092700462/811f904d5b

[Mark_Huang]

Hi David (PassMark),

We tried it with another platform, AMD V2000.
With TI USB hub EVM, it can see this issue as well. But it needs to run for a much longer time.

There is a problem to use the protocol analyzer to debug.
The issue only happened after many the restart booting.
The memory buffer of protocol analyzer is not enough to store the whole data.
We are still thinking how to get the data at the failed point.

[David (PassMark)]

Does it only happen with the combination of the Xeon CPU and the TI Hub?
(can you try the hub on another more common desktop machine)

[Mark_Huang]

Hi David (PassMark),
We are trying to get a protocol analyzer.
FYI, recently we got the EVM of TI TUSB8041. (https://www.ti.com/tool/TUSB8041EVM)
We plug it on Intel® Xeon® D-1746TER Processor platform and run the same test.
The same error can happen.
So if possible, you can try to get one TUSB8041EVM to see whether you can see the issue.
Thanks a lot.

[David (PassMark)]

Enumeration is a low level process, that occurs without any interaction at the application level. (i.e. it is at the level of electrical signalling and integrated circuits).

That timeout you mentioned was not for enumeration step, it was for how long the application level waits for data to be fully transmitted.

If you really want to get to the bottom of it you are probably going to need a protocol analyzer.

[Mark_Huang]

David (PassMark),

Thanks for your information.
We do have an USB2.0 device on the other downstream port.
However after disconnecting that USB2.0 device, the issue is still existed.

I found another post which discussed a similar issue.
It mentioned a timeout setting of USB test which could avoid this re-enumerate error.
I can only find below similar setting.
Is it the same setting for USB3.0 loopback plugs?

[David (PassMark)]

If this doesn't happen with any other hubs / port, it might be an issue with the hub.

Also are any other devices connected to the hub (e.g. keyboard / mouse)? Years ago there were sometimes issues if a mix of USB2 and USB3 devices were connected to the same hub.

Is the hub you are using available as a commercial standalone product we can buy?

[Mark_Huang]

Hi David (PassMark),
Thanks for your support.

We have tried the new firmware v2.8 today.
Unfortunately it didn't fix our issue. The situation is still the same.

- Would you think it is worth to try the FW v2.1? (But there is no download link for it)

- Below information for your reference.
During the restart test, it detects all USB loopback plugs at the first step in Windows OS, and then running Burn In test.
All loopback plugs were found at the detection step.
However when Burn In test starts running, it could happen "Failed to re-enumerate" error. And the loopback on downstream ports of hub is missing in Burn In test.
(P.S. If the system doesn't restart, there is no error at all for 24h running.)