Opened 3 years ago
Last modified 2 years ago
#17110 new bug
Haiku fails to boot with XHCI
Reported by: | nephele | Owned by: | waddlesplash |
---|---|---|---|
Priority: | normal | Milestone: | Unscheduled |
Component: | Drivers/USB/XHCI | Version: | R1/beta3 |
Keywords: | boot-failure | Cc: | |
Blocked By: | Blocking: | ||
Platform: | All |
Description (last modified by )
After trying to install Haiku for hours to a usb drive and failing I switched the usb slot, after which it worked. Thus is suspect this is related to usb3, the thumb drive and port are usb3.
The KDL displays "did not to find any boot partitions"
Attachments (3)
Change History (16)
by , 3 years ago
Attachment: | 2003D9A0-B95F-4AFB-A595-85798BFFC9AD.jpeg added |
---|
comment:1 by , 3 years ago
I don't have a syslog of the failed boot since it did not find the partition to write it, so let me know what more information I can extract from the KDL, the thumb drive isn't going anywhere. :)
comment:2 by , 3 years ago
Description: | modified (diff) |
---|
comment:3 by , 3 years ago
There is actually an EHCI (USB2) error in the log snippet displayed in the picture, followed by a usb_disk failure. Are you really sure it is a USB3 port?
comment:4 by , 3 years ago
It appears you have two EHCI controllers and one XHCI controller. Unfortunately from your syslog I cannot tell who owns what ports. It may be that the boot failure occurs on one EHCI controller but not the other.
comment:5 by , 3 years ago
From physical hardware that I can see:
- One SD Card Reader
- One Fingerprint Reader
- One black usb2 port
- Two Blue usb3 ports
The Touchpad seems connected via PS/2, don't know about the keyboard
application/Devices indeed shows two EHCI and one XHCI Controller
Booting fails as seen in the picture with a (blue) usb3 thumb drive connected to either (blue) usb3 port, and suceeds for the usb2 one
comment:6 by , 3 years ago
Interestingly, you have a Texas Instruments XHCI controller, but Intel EHCI controllers. Intel XHCI controllers have a routing system where the USB3 ports go to the EHCI controllers by default on most hardware, and are routed to the XHCI controller once the XHCI driver performs a handoff. I wonder if there is something similar going on here, that is, your device really is connected to the EHCI controller, it seems more than plausible given the error message.
comment:7 by , 3 years ago
Keywords: | boot-failure added |
---|
comment:8 by , 3 years ago
Please retest under a recent nightly.
If it still fails, please boot under a USB2 port, then connect a drive to a USB3 port, and post a syslog.
comment:9 by , 2 years ago
Still occurs, the log is from a self compiled image. The images from download.haiku-os.org seem completely broken to me, shows up without any formatted partitons to me. (the image i downloaded was hrev56511)
comment:10 by , 2 years ago
This TI xhci device seems to have a quirk available: https://github.com/torvalds/linux/blob/master/drivers/usb/host/xhci-pci.c#L327
it should only affect interrupt and isochronous pipes though: https://github.com/torvalds/linux/blob/6f9b5ed8caddfbc94af8307c557ed57a8ec5c65c/drivers/usb/host/xhci-mem.c#L1447
comment:11 by , 2 years ago
Ubuntu 22 fails to boot similarily (kernel gets loaded and i itramfs but then fails to mount/find rootfs). So this may be related but might also not be :)
follow-up: 13 comment:12 by , 2 years ago
the quirk you mention seems to be for replugging https://github.com/torvalds/linux/commit/69307ccb9ad7ccb653e332de68effdeaaab6907d
comment:13 by , 2 years ago
Replying to nephele:
the quirk you mention seems to be for replugging https://github.com/torvalds/linux/commit/69307ccb9ad7ccb653e332de68effdeaaab6907d
indeed, probably unrelated then.
photo of kdl