Opened 15 years ago
Last modified 6 years ago
#6041 new bug
Haiku hangs on boot with wireless keyboard+mouse
Reported by: | franxico | Owned by: | mmlr |
---|---|---|---|
Priority: | normal | Milestone: | R1 |
Component: | Drivers/USB | Version: | R1/alpha2 |
Keywords: | boot-failure | Cc: | |
Blocked By: | Blocking: | ||
Platform: | x86 |
Description
Haiku Alpha 2 hangs after the 4th icon. Sensor leds go on and then boot process stops.
I had the same problem in the past. It used to work unplugging the USB sensor during boot time. It doesn't work anymore. Tried every safe mode option. It's a Logitech Cordless Desktop EX110 on a Dell Vostro 410.
Hopefully I could install Haiku and safe debug info.
Attachments (2)
Change History (9)
by , 15 years ago
comment:3 by , 13 years ago
Blocking: | 7665 added |
---|
comment:4 by , 13 years ago
Just tried the hrev42190 booting from CD. Still same thing. Tried some safe mode options, but it hangs always on the 4th icons. Do you want debug info pictures? Thanks for the help!
comment:5 by , 13 years ago
Please attach photos individually in the future, resizing them so that they are < 500k if possible. This makes it possible to look at them directly from trac and greatly increases the likelihood of someone looking at them.
In this case, what happens seems to be a lot of unhandled interrupts on UHCI startup, leading to IRQ 19 being disabled. That one is shared between the SATA, IDE and two UHCI controllers. The disable happens before all UHCI controllers are fully initialized which probably explains why the interrupt is disabled, as the controller driver that would handle them isn't yet installed. Since we don't yet re-enable an IRQ when a new handler is installed, the disabled IRQ sticks and probably causes the SATA or IDE controller to fail later on, stalling the boot process.
It's difficult to handle differently. A possibility would be to scan the USB controllers first, initializing them only to the point where the interrupts can be masked, do that for all controllers and only do the full initialization in a second step. The other way (and this one will have to be implemented anyway) is to just re-enable a disabled IRQ whenever a new handler is installed. This still has the problem that there will be an interrupt storm early on (until the IRQ is disabled eventually) which'll introduce needless delays.
comment:6 by , 6 years ago
Keywords: | boot-failure added |
---|
comment:7 by , 6 years ago
Blocking: | 7665 removed |
---|
USB_HID debug information