#15161 closed bug (invalid)
Cannot boot from USB 3 port: Device check-sum error & ring locks up
| Reported by: | probono | Owned by: | waddlesplash |
|---|---|---|---|
| Priority: | normal | Milestone: | Unscheduled |
| Component: | Drivers/USB/XHCI | Version: | R1/Development |
| Keywords: | Cc: | ||
| Blocked By: | Blocking: | #15162 | |
| Platform: | All |
Description
Devices used: TravelMate B117 notebook, left (USB 3) port, firmware set to use UEFI for booting (not CSM/Legacy).
Cannot boot from 120 GB Kingston A400 SSD attached to a ASMedia ASM2115 SATA to USB 3 adapter, attached to the USB 3 port of a TravelMate B117 notebook.
- The bootany image is not booting at all, the notebook firmware does not recognize a bootable device
- A manually partitioned drive boots "sometimes": Usually it boots into the Haiku bootloader, which does not find a boot volume. Rebooting from the bootloader menu a couple of times does not change this
- While in this state, pressing Ctrl-Alt-Delete does more "deeply" reboot the system (Acer splash scren appears) and then usually Haiku begins to boot into the kernel, without showing any Haiku bootloader screens
KDL screenshots made by pressing Alt+PrntScrn+D when the boot screen is stalling for a long time, and then entering
syslog | grep usb
lspci information: https://paste.debian.net/plain/1091516 lsusb information: https://paste.debian.net/plain/1091515
Attachments (1)
Change History (10)
comment:1 by , 5 years ago
| Blocking: | 15162 added |
|---|
comment:2 by , 5 years ago
| Component: | - General → Drivers/USB/XHCI |
|---|---|
| Owner: | changed from to |
| Summary: | Cannot boot from USB 3 port: usb_disk: read failed: Operation timed out → Cannot boot from USB 3 port: Device check-sum error & ring locks up |
comment:3 by , 5 years ago
comment:4 by , 5 years ago
120 GB Kingston A400 SSD attached to a ASMedia ASM2115 SATA to USB 3 adapter, attached to the USB 3 port of a TravelMate B117 notebook.
As of hrev53313+1 it boots all the way up to the "rocket" symbol becoming red, but then the desktop never appears.
Gan I grep for something special in the error output so that I don't have to upload multiple images?
comment:5 by , 5 years ago
it boots all the way up to the "rocket" symbol becoming red, but then the desktop never appears.
This may or may not be an XHCI problem, then (a video driver initialization failure would usually have the same result.) As per your original ticket description, it never got that far before, right?
A picture of the final page of syslog output should be more than enough to diagnose what is going on.
by , 5 years ago
| Attachment: | IMG_20190731_164350852_HDR.jpg added |
|---|
comment:6 by , 5 years ago
OK, so it's still the ring lockup, it just seems to occur a bit later than before now.
comment:9 by , 2 years ago
(I think this was fixed, anyway, with the changes to device initialization earlier this year, if not in the changes 2 years ago.)
I think my refactors to CancelQueuedTransfers should fix the ring lockups. There will still probably be Check-sum-errors, but please retest and see if this is any better.