Bug 87531
Summary: | do_IRQ: 0.166 No irq handler for vector (irq -1) | ||
---|---|---|---|
Product: | Platform Specific/Hardware | Reporter: | Elmar Stellnberger (estellnb) |
Component: | i386 | Assignee: | platform_i386 |
Status: | NEW --- | ||
Severity: | blocking | CC: | alan, bjorn, szg00000, tj |
Priority: | P1 | ||
Hardware: | i386 | ||
OS: | Linux | ||
Kernel Version: | 3.17.1-1-ARCH #1 SMP PREEMPT Wed Oct 15 15:36:07 CEST 2014 | Subsystem: | |
Regression: | No | Bisected commit-id: | |
Attachments: |
dmesg
/proc/interrupts /proc/irq/* lspci cpuinfo: 2xPIII800 /proc/interrupts (2xCPU) /proc/irq/* (2xCPU) dmesg (2xCPU) lspci -vvvxx (2xCPU) |
Description
Elmar Stellnberger
2014-11-02 10:03:54 UTC
Created attachment 156111 [details]
dmesg
Created attachment 156121 [details]
/proc/interrupts
Created attachment 156131 [details]
/proc/irq/*
Created attachment 156141 [details]
lspci
Created attachment 157141 [details]
cpuinfo: 2xPIII800
After having happily installed a second CPU, now everything works fine like by a miracle; SATA works well, no more messages 'No IRQ handler for vector (irq -1)', no keyboard that would refuse to work.
Created attachment 157151 [details]
/proc/interrupts (2xCPU)
Created attachment 157161 [details]
/proc/irq/* (2xCPU)
Created attachment 157171 [details]
dmesg (2xCPU)
Now it even works with a kernel which is a little bit older. However I can remember this bug having already persisted for a long time before I have filed this report; i.e. the observed effects won`t depend on the kernel version.
Created attachment 157181 [details]
lspci -vvvxx (2xCPU)
The board is an Asus P2B-DS; it requires 2CPUs to work with this card. Other boards supporting only one CPU will not work at all with this Promise SATA300 card under Linux as far as I could test.
Looks like PCI IRQ assignment somehow gets screwed w/ single CPU. Bjorn, any ideas? Thanks. |