Bug#556106: do_IRQ: 0.184 No irq handler for vector
>>>> Package: linux-image-2.6.26-2-amd64
>>>>> Version: 2.6.26-19lenny2
>>>>> Severity: critical
>>>>> Justification: breaks the whole system
>>>>>
>>>>>
>>>>> On some disk load (over qla2xxx attached disks) the server prints an
>>>>> error and stops (console output attached below).
>>>>> The same kernel with additional parameter pci=nomsi runs with no any
>>>>> problem.
>>
>>> The next release of Debian (6.0, code name Squeeze) will be based
>>> on 2.6.32. Please test the current 2.6.32 from unstable/testing and tell
>>> us whether the problem persists. If so, we should report it upstream
>>> to the kernel.org developers.
>>>
>>> The 2.6.32 kernel is available from packages.debian.org and can
>>> be installed in both Debian stable, testing and unstable
>>> installations.
>>
>> During few hours I was unable to reproduce the error on lenny with kernel from
>> testing. A hardware was exactly the same as before.
>
> I believe this bug is the same as #572322, which I fixed in version
> 2.6.26-22. Please can you check whether the current stable security
> update (version 2.6.26-22lenny1) fixes this bug?
I do not think that the bug is the same.
I had loaded kernel 2.6.32 and 2.6.26-22lenny1. With the same command line
/proc/interrupts are different
# cat 2.6.32-3-amd64
CPU0 CPU1 CPU2 CPU3
0: 81 0 0 0 IO-APIC-edge timer
1: 2 1 1 2 IO-APIC-edge i8042
4: 58 64 63 58 IO-APIC-edge serial
8: 0 1 0 0 IO-APIC-edge rtc0
9: 0 0 0 0 IO-APIC-fasteoi acpi
16: 137 129 129 124 IO-APIC-fasteoi eth0
17: 29 29 41 35 IO-APIC-fasteoi eth1
19: 873 867 863 875 IO-APIC-fasteoi ahci
57: 19 23 19 23 PCI-MSI-edge qla2xxx
58: 27 32 26 27 PCI-MSI-edge qla2xxx
NMI: 0 0 0 0 Non-maskable interrupts
LOC: 7881 7700 7647 7339 Local timer interrupts
SPU: 0 0 0 0 Spurious interrupts
PMI: 0 0 0 0 Performance monitoring interrupts
PND: 0 0 0 0 Performance pending work
RES: 393 307 235 285 Rescheduling interrupts
CAL: 963 956 249 260 Function call interrupts
TLB: 105 104 428 533 TLB shootdowns
TRM: 0 0 0 0 Thermal event interrupts
THR: 0 0 0 0 Threshold APIC interrupts
MCE: 0 0 0 0 Machine check exceptions
MCP: 1 1 1 1 Machine check polls
ERR: 3
MIS: 0
# cat 2.6.26-2-amd64
CPU0 CPU1 CPU2 CPU3
0: 62 0 0 0 IO-APIC-edge timer
1: 0 0 0 0 IO-APIC-edge i8042
4: 50 59 63 64 IO-APIC-edge serial
8: 0 1 0 0 IO-APIC-edge rtc0
9: 0 0 0 0 IO-APIC-fasteoi acpi
16: 997 1003 1009 1002 IO-APIC-fasteoi eth0
17: 123 112 108 122 IO-APIC-fasteoi eth1
19: 1259 1263 1252 1246 IO-APIC-fasteoi ahci
24: 27 27 28 26 IO-APIC-fasteoi qla2xxx
25: 38 31 34 35 IO-APIC-fasteoi qla2xxx
NMI: 0 0 0 0 Non-maskable interrupts
LOC: 10773 11111 14064 10870 Local timer interrupts
RES: 362 534 578 538 Rescheduling interrupts
CAL: 309 376 396 365 function call interrupts
TLB: 414 420 639 643 TLB shootdowns
TRM: 0 0 0 0 Thermal event interrupts
THR: 0 0 0 0 Threshold APIC interrupts
SPU: 0 0 0 0 Spurious interrupts
ERR: 0
Yes, the 2.6.26 does not have the problem. But it is because of disabled MSI.
2.6.32 has enabled MSI, at the same time the problem does not happen.
Reply to: