On 31.5.2023 14.56, Christian Schaubschläger wrote:
Hi,
Attached is a patch that adds more debugging, adds a minimum
"power on to power good" delay, (as hub reports 0ms), and checks port link
states during hub initialization.
Does it help? Could you take logs with that patch applied.
Only dmesg with xhci and usbcore dynamic debug are needed.
xhci traces won't help as issue seems to be between the hub inthe dock and the NIC
patch applied, see logs in the attachment. The behaviour is unchanged.
Thanks,
Christian
Thanks,
In the failed case the hub in the dock doesn't show any activity
on port4 where the NIC is connected. No changes, link isn't in any
error state. It looks just like any empty port.
I don't have any idea what's going on.
I guess it's not possible to connect a protocol analyzer between the
hub in the dock and the NIC?
ok success case:
[ 1.712754] usb 6-2-port1: status 02a0 change 0000
[ 1.713070] usb 6-2-port2: status 02a0 change 0000
[ 1.713567] usb 6-2-port3: status 0203 change 0010 <- another hub
[ 1.714184] usb 6-2-port4: status 0203 change 0010 <- NIC
nok failed case:
[ 1.716756] usb 6-2-port1: status 02a0 change 0000
[ 1.717036] usb 6-2-port2: status 02a0 change 0000
[ 1.717395] usb 6-2-port3: status 0203 change 0010 <- another hub
[ 1.717976] usb 6-2-port4: status 02a0 change 0000
Thanks
Mathias
