Hello StJohn,
Thank you for your patience whilst I was on holidays.
On the latest log you provided, the USB device is NOT connected.
This issue cannot technically come from the host driver.
If you don't care why, skip this reply to TL;DR.
# DETAILS
Here is how it works:
1. You plug a device on the computer
2. The computer USB Host Controller talks with the USB device which introduces itself: Hello, I device 4320 from vendor 17e9. Here are my endpoints... It's called enumeration.
3. The operating system, so Windows here, from the vendor and device ID and the features, choses drivers from its driver store, or goes to Windows Update.
4. Windows has attaches the DisplayLink drivers and it goes.
In your logs, you will see the device is not recognised by Windows. It is absent from Device Manager. If Windows doesn't see the device, it's not even invoking the device drivers... So the issue is elsewhere. It can technically only be at:
A. The OS level. I doubt it, we would have heard more occurrences.
B. The USB Host Controller & driver. That happens if there are some drivers/hardware slightly out of spec, especially with low power modes. Could be.
C. The USB hub inside the docking station. Could be. I don't have logs of that as we don't do hubs.
D. The DisplayLink chip firmware within the docking station. Could happen, but we wouldn't pass USB compliance and we wouldn't be part of the USB known good devices in the gold tree used to test the tester if we were not compliant...
E. The DisplayLink chip hardware. Most unlikely as it works for hours.
When I look in your HOST driver logs, the part on Windows, it says there is a Plug and Play event of device removal. So Windows won't talk to it and the drivers have nothing to talk to. I think Windows throw it off of the bus because of the communication issues. The error code is reported by the USB Host Controller.
When I look in the DisplayLink chip logs, the part within the dock, communication is lost suddenly with the host so we stop getting events from the dock. Other events are captured as USB Disconnects, so they chip doesn't just stop.
# TL;DR
1. Would you please be able to force the device in USB2 mode, by either using a USB2 port, or a USB2 cable?
2. Could you please try to disable USB Selective Suspend to see if the issue happens with low power modes? This could be explaining why it takes a couple of hours to kick in.
3. I see the title of this thread is that the software crash. What led you to believe this was a software crash?
4. What did you do for the 2 docks to suddenly work on these machines? May I get the logs from one so I can see if firmware differs? If so, we can try and force the firmware on the non-working one and see.
Kind regards,
Alban
|