Opened 11 years ago
Closed 10 years ago
#9718 closed bug (fixed)
KERN: More than 99% interrupts of vector 16 are unhandled
| Reported by: | jessicah | Owned by: | korli |
|---|---|---|---|
| Priority: | normal | Milestone: | R1 |
| Component: | Drivers/Graphics/intel_extreme | Version: | R1/Development |
| Keywords: | Cc: | ||
| Blocked By: | Blocking: | ||
| Platform: | All |
Description
Possibly related to #3008. Brand new build of an IvyBridge system. Syslog attached.
System starts up, goes through the lil icons stuff. After the rocket, screen turns off/goes to sleep, and unresponsive.
Attachments (1)
Change History (5)
by , 11 years ago
| Attachment: | syslog.txt added |
|---|
comment:1 by , 11 years ago
| Component: | System/Kernel → Drivers/Graphics/intel_extreme |
|---|
comment:2 by , 11 years ago
I removed the intel_extreme driver, and Haiku boots to the desktop! I wonder if it's struggling with the multiple outputs of the graphics chip. I also noticed in the syslog that it wanted to choose 1024x768 as the resolution. This has DisplayPort, HDMI & DVI (think it's digital only), and at boot I am able to choose 1920x1080 as the resolution (although syslog still showed choosing 1024x768). Currently using HDMI, although DVI didn't work either when I had a DVI monitor connected.
comment:3 by , 10 years ago
| Owner: | changed from to |
|---|---|
| Status: | new → assigned |
comment:4 by , 10 years ago
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
Should be fixed in hrev47032. Please reopen if needed.
Reading the routing table there are 5 devices on GSI 16:
The xHCI driver is incomplete and not loaded, so that one shouldn't be a problem.
EHCI is loaded relatively early and the first message is pretty far away from that, so this one is less likely to blame.
There's no driver for MEI controllers and no interrupts should be enabled for it.
There doesn't seem to be anything attached to the PCIe port, so it shouldn't generate interrupts.
The first message shows up relatively soon after the following is printed:
This line is output just after the interrupt is configured at the end of the intel_extreme_init function. So it looks like the problem is in the interrupt handler of the intel_extreme driver.
The interrupt routing itself looks fine. And since we do get the message for vector 16, it also looks like the right GSI is routed.
You could verify that by forcing safe mode video in the boot menu and/or removing the intel_extreme driver from "/boot/system/add-ons/kernel/drivers/bin".