#14792 closed bug (fixed)
XHCI: "found device with invalid IRQ - check IRQ assignment"
Reported by: | Jose64141 | Owned by: | nobody |
---|---|---|---|
Priority: | normal | Milestone: | R1/beta2 |
Component: | Drivers/USB/XHCI | Version: | R1/Development |
Keywords: | Cc: | ||
Blocked By: | Blocking: | #13188 | |
Platform: | All |
Description
I tried to install Haiku from an USB, but I always got the Unable to find boot partition error. So, I tried to run the Installer from the HDD, and it worked, but not the USB mouse. PS: I have a TUF H370 PRO mobo
Attachments (4)
Change History (12)
comment:1 by , 6 years ago
by , 6 years ago
comment:2 by , 6 years ago
Component: | - General → Drivers/USB/XHCI |
---|---|
Keywords: | USB removed |
Summary: | USB not working → XHCI: "found device with invalid IRQ - check IRQ assignment" |
KERN: usb xhci: found device with invalid IRQ - check IRQ assignment
Well, that's a new one; I've never seen that message before!
comment:3 by , 6 years ago
The system seems to support MSIs (as the HDA driver uses one) so it is a bit surprising XHCI wouldn't be using those. The early part of the boot seems to be missing from the syslog, which holds the PCI dump and interrupt setup, so it's hard to say what's going on. Can you try removing the syslogs and booting fresh and attach a new syslog and possibly syslog.old if it exists?
comment:5 by , 6 years ago
Replying to waddlesplash:
This should be fixed in hrev52742; please test.
I tested hrev52749, and it booted :D, and I have Ethernet. c: But, when I try yo mount an external HDD, the USB devices stop working. :c I remember when I had my old PC, sometimes I got the same error. So i have to restart the computer and bla bla, but at least I can use the mouse, and can see the HDD files. :) I will attach the syslog after and before I mounted the HDD.
comment:6 by , 6 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
That's already tracked as #13772. So this issue is fixed. :)
comment:7 by , 6 years ago
Blocking: | 13188 added |
---|
comment:8 by , 5 years ago
Milestone: | Unscheduled → R1/beta2 |
---|
Assign tickets with status=closed and resolution=fixed within the R1/beta2 development window to the R1/beta2 Milestone
Please post a syslog; one from your working install is fine.