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.
-- Package-specific info:
** Version:
Linux version 2.6.26-2-amd64 (Debian 2.6.26-19lenny2) (dannf@debian.org) (gcc version 4.1.3 20080704 (prerelease) (Debian 4.1.2-25)) #1 SMP Thu Nov 5 02:23:12 UTC 2009
Kernel: Linux 2.6.26-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages linux-image-2.6.26-2-amd64 depends on:
ii debconf [debconf-2.0] 1.5.24 Debian configuration management sy
ii initramfs-tools [linux-initra 0.92o tools for generating an initramfs
ii module-init-tools 3.4-1 tools for managing Linux kernel mo
linux-image-2.6.26-2-amd64 recommends no packages.
Versions of packages linux-image-2.6.26-2-amd64 suggests:
ii grub 0.97-47lenny2 GRand Unified Bootloader (Legacy v
pn linux-doc-2.6.26 <none> (no description available)
-- debconf information excluded
[93543.093300] qla2xxx 0000:0b:01.0: Mailbox command timeout occured. Issuing ISP abort.
[93543.187021] qla2xxx 0000:0b:01.0: Performing ISP error recovery - ha= ffff81022b8985f8.
[93544.168312] qla2xxx 0000:0b:01.0: LIP reset occured (f700).
[93545.488056] qla2xxx 0000:0b:01.0: LOOP UP detected (4 Gbps).
[93545.684498] do_IRQ: 0.184 No irq handler for vector
[93545.800455] int3: 0000 [1] SMP
[93545.836381] CPU 0
[93545.836381] Modules linked in: dm_round_robin dm_multipath dm_mod qla2xxx firmware_class scsi_transport_fc scsi_tgt iTCO_wdt snd_pcm snd_timer snd soundcore snd_page_alloc i2c_i801 serio_raw i2c_core container tg3 rng_core pcspkr psmouse shpchp button pci_hotplug i5000_edac edac_core evdev thermal processor fan thermal_sys ahci libata dock raid1 md_mod ext3 jbd mbcache sd_mod scsi_mod
[93546.363711] Pid: 0, comm: swapper Not tainted 2.6.26-2-amd64 #1
[93546.451197] RIP: 0010:[<ffffffff8057d0f1>] [<ffffffff8057d0f1>] _sinittext+0xf1/0x140
[93546.558593] RSP: 0000:ffffffff80575f18 EFLAGS: 00000046
[93546.558593] RAX: 0000000000000000 RBX: ffffffff80212c3f RCX: 0000000000000000
[93546.717564] RDX: 0000000000000000 RSI: 0000000000000001 RDI: ffffffff804fbe70
[93546.717564] RBP: 0000000000000000 R08: ffff8100010356a0 R09: 00008fb6f7876db6
[93546.717564] R10: ffff81022b891990 R11: ffffffff8021a827 R12: ffffffffffffffff
[93546.717564] R13: ffffffff805a5900 R14: ffffffff805a64c0 R15: 0000000000000000
[93546.717564] FS: 0000000000000000(0000) GS:ffffffff8053c000(0000) knlGS:0000000000000000
[93547.171510] CS: 0010 DS: 0018 ES: 0018 CR0: 000000008005003b
[93547.171510] CR2: 00007ffe29eb6218 CR3: 00000001e7c6a000 CR4: 00000000000006e0
[93547.171510] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[93547.171510] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
[93547.171510] Process swapper (pid: 0, threadinfo ffffffff80574000, task ffffffff804f9480)
[93547.171510] Stack: ffffffff80212c80 0000000000000010 0000000000000246 ffffffff80575f40
[93547.171510] 0000000000000000 ffffffff8020ac79 0000000000000020 ffffffff8057ddd1
[93547.171510] 0000000000000000 ffffffff8058e5d6 ffffffff805a64c0 0000000000675398
[93547.171510] Call Trace:
[93547.171510] [<ffffffff80212c80>] mwait_idle+0x41/0x4d
[93547.171510] [<ffffffff8020ac79>] cpu_idle+0x89/0xb3
[93547.171510]
[93547.171510]
[93547.171510] Code: cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc <cc> cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc
[93548.344319] RIP [<ffffffff8057d0f1>] _sinittext+0xf1/0x140
[93548.344319] RSP <ffffffff80575f18>
[93548.344319] ---[ end trace f2c19baabbb385ea ]---
[93548.344319] Kernel panic - not syncing: Attempted to kill the idle task!
05-30-2010, 12:43 PM
Moritz Muehlenhoff
Bug#556106: do_IRQ: 0.184 No irq handler for vector
On Fri, Nov 13, 2009 at 05:18:05PM +0200, Andrejs Dubovskis wrote:
> 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.
Hi,
Sorry for the late response.
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.
Thanks,
Moritz
--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20100530124322.GU2398@galadriel.inutil.org">http://lists.debian.org/20100530124322.GU2398@galadriel.inutil.org
06-08-2010, 02:08 PM
Andrejs Dubovskis
Bug#556106: do_IRQ: 0.184 No irq handler for vector
Hi!
>> 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.
Thank you.
--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 4C0E4EEA.10709@lmt.lv">http://lists.debian.org/4C0E4EEA.10709@lmt.lv
06-15-2010, 01:48 AM
Ben Hutchings
Bug#556106: do_IRQ: 0.184 No irq handler for vector
On Tue, 2010-06-08 at 17:08 +0300, Andrejs Dubovskis wrote:
> Hi!
> >> 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?
Ben.
--
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.
06-15-2010, 07:52 AM
Andrejs Dubovskis
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
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.
--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 4C17314A.20401@lmt.lv">http://lists.debian.org/4C17314A.20401@lmt.lv
06-15-2010, 12:53 PM
Ben Hutchings
Bug#556106: do_IRQ: 0.184 No irq handler for vector
On Tue, 2010-06-15 at 10:52 +0300, Andrejs Dubovskis wrote:
> >>>> 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
[...]
> 57: 19 23 19 23 PCI-MSI-edge qla2xxx
> 58: 27 32 26 27 PCI-MSI-edge qla2xxx
[...]
> # cat 2.6.26-2-amd64
[...]
> 24: 27 27 28 26 IO-APIC-fasteoi qla2xxx
> 25: 38 31 34 35 IO-APIC-fasteoi qla2xxx
[...]
> 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.
The fix I applied is to disable MSI automatically for this device. I
don't know whether the driver somehow works reliably in 2.6.32 without
that change, but that change has been accepted by QLogic and by the
Linux SCSI maintainer.
Ben.
--
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.