USB storage devices disappear after reboot/power failure

[miczyg1]

Dasharo version v0.1.0

Dasharo variant Dasharo compatible with MSI PRO Z690-A WIFI DDR4

Affected component(s) or functionality USB storage devices

Brief summary USB storage devices disappear from UEFI boot options after reboot/power failure

How reproducible 100%

How to reproduce

Steps to reproduce the behavior:

1. Plug the USB device and boot from it.
2. Reboot the system or simply remove power.
3. Attach power again and power on the platform if power was removed. Wait for boot logo.
4. Enter boot menu and notice there is not USB storage attached.

Expected behavior USB storage devices always appear when attached.

Actual behavior USB devices do not get detected after reboot power/failure.

Screenshots None

Additional context USB configuration may to be complete yet.

Solutions you've tried Detaching and reattaching to to the same or different port allows to detect the device after reset again. Resetting or disconnect/reconnect the emulated storage on PiKVM also works as a workaround. PiKVM HID device do not need a reset though.

[miczyg1]

It seems MSI v1.0 firmware suffers from similar problems. I often have to reset the composite device from PiKVM. Physical USB stick is not detected at all. I have found Inte lighting report about USB stick not being detected. It occurred to be a PMC issue. TODO: check newer ME version and PMC firmware

[mkopec]

@miczyg1 Could this be related to the issue described here? https://review.coreboot.org/c/coreboot/+/63552/4..6

[mkopec]

I have observed a similar issue on one of the platforms: while in UEFI, one of the XHCI ports gets reset over and over, causing a 30 second lockup every time, causing logspam and slowing down boot time to a halt. In my case a complete shutdown and cold boot from G3 would not help.

Here's a portion of the logs that would appear repeatedly:

XhcSetRootHubPortFeature: status Success
XhcClearRootHubPortFeature: status Success
XhcClearRootHubPortFeature: status Success
XhcSetRootHubPortFeature: status Success
UsbEnumerateNewDev: hub port 4 is reset
XhcClearRootHubPortFeature: status Success
UsbEnumerateNewDev: No device present at port 4
XhcClearRootHubPortFeature: status Success
UsbEnumeratePort: port 4 state - 00, change - 01 on 75193018
UsbEnumeratePort: Device Connect/Disconnect Normally
UsbEnumeratePort: device disconnected event on port 4
XhcClearRootHubPortFeature: status Success
UsbEnumeratePort: port 4 state - 00, change - 01 on 75193018
UsbEnumeratePort: Device Connect/Disconnect Normally
UsbEnumeratePort: device disconnected event on port 4
XhcClearRootHubPortFeature: status Success
XhcClearRootHubPortFeature: status Success
XhcClearRootHubPortFeature: status Success
UsbEnumeratePort: port 4 state - 00, change - 01 on 75193018
UsbEnumeratePort: Device Connect/Disconnect Normally
UsbEnumeratePort: device disconnected event on port 4
XhcClearRootHubPortFeature: status Success
XhcClearRootHubPortFeature: status Success
XhcClearRootHubPortFeature: status Success
UsbEnumeratePort: port 4 state - 201, change - 01 on 75193018
UsbEnumeratePort: Device Connect/Disconnect Normally
UsbEnumeratePort: new device connected at port 4
XhcUsbPortReset!

Reducing two of the timeouts in this section from 10s (XHC_GENERIC_TIMEOUT) to 50ms made the machine at least usable.

[miczyg1]

I have seen similar reset loops of the USB device. Question is what is the device at port 4?

[mkopec]

I wanted to test again to see which device it was, but now I can't reproduce the issue anymore :|

[deeplow]

I have this exact situation in version v1.1.1 and v1.1.2. I must have forced shut-down the system and from then on I could not boot from a USB drive. Only in rare occasions could I get it to work. This is particularly annoying when reinstalling the system.

In the end I had to burn the OS installer into a SATA SSD to do the job of USB.