ACPI startup causes unhandled IRQ.

[Daniel Pittman]

Binary package hint: linux-image-2.6.15-26-686

With the latest kernel update for Dapper, and I believe the one prior to it, the ACPI startup causes IRQ9 to be issues.

Nothing handles the interrupt, leading to the kernel disabling the IRQ, and consequently ACPI, wifi, and some of my USB hardware not functoning correctly.

I am not sure exactly which kernel version caused this because I don't actually /use/ much of that hardware routinely, I fear. It is a recent development, though, and is definitely present in the latest (-26) release of the kernel.

The hardware is an IBM A31p Thinkpad laptop. The latest firmware updates have been applied, which was over a year ago now IIRC. The hardware has been very stable up to now.

This looks to me like some change in IRQ handling causes the ACPI interrupt to issue at registration time, before the acpi IRQ handler is fully registered.

The dmesg trace of this is:

[17179572.376000] ACPI: Subsystem revision 20051216
[17179585.040000] irq 9: nobody cared (try booting with the "irqpoll" option)
[17179585.040000] [<c014ea9a>] __report_bad_irq+0x2a/0xa0
[17179585.040000] [<c014ebb7>] note_interrupt+0x87/0xf0
[17179585.040000] [<c014e38d>] __do_IRQ+0xfd/0x110
[17179585.040000] [<c0105ce9>] do_IRQ+0x19/0x30
[17179585.040000] [<c0103f26>] common_interrupt+0x1a/0x20
[17179585.040000] [<c012a74f>] __do_softirq+0x5f/0xe0
[17179585.040000] [<c014e35c>] __do_IRQ+0xcc/0x110
[17179585.040000] [<c012a805>] do_softirq+0x35/0x40
[17179585.040000] [<c012a8e5>] irq_exit+0x45/0x50
[17179585.040000] [<c0105cee>] do_IRQ+0x1e/0x30
[17179585.040000] [<c0103f26>] common_interrupt+0x1a/0x20
[17179585.040000] [<c030ef26>] _spin_unlock_irqrestore+0x6/0x20
[17179585.040000] [<c014e6e9>] setup_irq+0xc9/0x120
[17179585.040000] [<c0218467>] acpi_irq+0x0/0x16
[17179585.040000] [<c014e8fa>] request_irq+0xaa/0xd0
[17179585.040000] [<c02184d3>] acpi_os_install_interrupt_handler+0x56/0x80
[17179585.040000] [<c0218467>] acpi_irq+0x0/0x16
[17179585.040000] [<c0218467>] acpi_irq+0x0/0x16
[17179585.040000] [<c021c99f>] acpi_ev_install_sci_handler+0x1a/0x1e
[17179585.040000] [<c021c968>] acpi_ev_sci_xrupt_handler+0x0/0x18
[17179585.040000] [<c021c1b0>] acpi_ev_install_xrupt_handlers+0x6/0x68
[17179585.040000] [<c022c4a4>] acpi_enable_subsystem+0x63/0x79
[17179585.040000] [<c03c6df4>] acpi_bus_init+0xc/0x8e
[17179585.040000] [<c03c6eab>] acpi_init+0x35/0xb0
[17179585.040000] [<c03acb04>] do_initcalls+0x54/0xd0
[17179585.040000] [<c03d0c95>] netfilter_init+0x65/0xa0
[17179585.040000] [<c0100395>] init+0x75/0x200
[17179585.040000] [<c0100320>] init+0x0/0x200
[17179585.040000] [<c0101525>] kernel_thread_helper+0x5/0x10
[17179585.040000] handlers:
[17179585.040000] [<c0218467>] (acpi_irq+0x0/0x16)
[17179585.040000] Disabling IRQ #9

I can supply further details, if needed. I have also had some (limited) kernel development experience before, so can cope with things like enabling debugging and patch the system if you need me to.

[Daniel Pittman (daniel-rimspace)]

This problem continues after the recent kernel update. The trace, etc, look identical.

[Patrick Dixon (patrick-dixon)]

I have what I think is a similar problem with a A8V-MX motherboard.

dmesg output is as follows:

[ 57.411434] [drm] Initialized drm 1.1.0 20060810
[ 57.427919] ACPI: PCI Interrupt 0000:01:00.0[A] -> GSI 16 (level, low) -> IRQ 20
[ 57.428521] [drm] Initialized via 2.10.0 20060529 on minor 0
[ 57.429010] [drm] Initialized via 2.10.0 20060529 on minor 1
[ 57.643029] agpgart: Found an AGP 3.0 compliant device at 0000:00:00.0.
[ 57.643147] agpgart: Putting AGP V3 device at 0000:00:00.0 into 8x mode
[ 57.643300] agpgart: Putting AGP V3 device at 0000:01:00.0 into 8x mode
[ 58.036175] eth0: no IPv6 routers present
[ 60.033467] irq 20: nobody cared (try booting with the "irqpoll" option)
[ 60.033476] [<c0151534>] __report_bad_irq+0x24/0x80
[ 60.033489] [<c01517e0>] note_interrupt+0x250/0x290
[ 60.033501] [<c0150aa5>] handle_IRQ_event+0x25/0x50
[ 60.033510] [<c015210d>] handle_fasteoi_irq+0xbd/0xd0
[ 60.033518] [<c0105960>] do_IRQ+0x40/0x80
[ 60.033528] [<c0104103>] common_interrupt+0x23/0x30
[ 60.033532] [<c0101e00>] default_idle+0x0/0x40
[ 60.033545] [<c0101e2f>] default_idle+0x2f/0x40
[ 60.033551] [<c01013f9>] cpu_idle+0x49/0xc0
[ 60.033557] [<c03cb7c6>] start_kernel+0x336/0x3b0
[ 60.033562] [<c03cb230>] unknown_bootoption+0x0/0x260
[ 60.033577] =======================
[ 60.033579] handlers:
[ 60.033580] [<dca311c0>] (cx8800_irq+0x0/0x230 [cx8800])
[ 60.033587] [<dca49160>] (cx8802_irq+0x0/0x2d0 [cx8802])
[ 60.033594] [<ddcba480>] (via_driver_irq_handler+0x0/0x1d0 [via])
[ 60.033600] Disabling IRQ #20

The problem affects a PCI card installed into slot 1 since it shares this pci interrupt. Once the IRQ is disabled, the card's interrupts go unhandled. I've tried booting with irqpoll, but that doesn't seem to solve the problem.

Have tried 2.6.10, 2.6.11 and 2.6.20 kernels with the same result. The IRQ number is different each time, but is always the one allocated to this device.

:~$ cat /proc/interrupts
           CPU0
  0: 703959 IO-APIC-edge timer
  1: 542 IO-APIC-edge i8042
  6: 5 IO-APIC-edge floppy
  7: 0 IO-APIC-edge parport0
  8: 3 IO-APIC-edge rtc
  9: 1 IO-APIC-fasteoi acpi
 12: 9279 IO-APIC-edge i8042
 14: 519410 IO-APIC-edge ide0
 15: 0 IO-APIC-edge libata
 16: 0 IO-APIC-fasteoi uhci_hcd:usb3
 17: 0 IO-APIC-fasteoi uhci_hcd:usb1
 18: 1334 IO-APIC-fasteoi uhci_hcd:usb2, ehci_hcd:usb5, VIA8237
 19: 7797 IO-APIC-fasteoi uhci_hcd:usb4, eth0
 20: 300000 IO-APIC-fasteoi cx88[0], cx88[0], via@pci:0000:01:00.0
221: 0 PCI-MSI-edge libata
NMI: 0
LOC: 703964
ERR: 0
MIS: 0

[Jérôme Guelfucci (jerome-guelfucci-deactivatedaccount)]

Thank you for your bug report. Do you still have this issue with the latest release of Ubuntu ?

[Patrick Dixon (patrick-dixon)]

Yes - I do.

I'm running a 2.6.20-15-generic kernel on Fiesty

I've resolved it for now by booting with noirqdebug

I also have problems with DMA on this m/b, and have had to restrict DMA speed of the HD to get my DVB-T card to work. Dunno if it's related ...

[Jérôme Guelfucci (jerome-guelfucci-deactivatedaccount)]

Could you update to 2.6.20-16.29 and tell me if this still happens ?

[Patrick Dixon (patrick-dixon)]

I've updated to 2.6.20-16-generic via apt-get dist-upgrade

but still have the problem:-

[ 53.934348] irq 16: nobody cared (try booting with the "irqpoll" option)
[ 53.934354]
[ 53.934355] Call Trace:
[ 53.934358] <IRQ> [<ffffffff802bd265>] __report_bad_irq+0x35/0x90
[ 53.934401] [<ffffffff802bd4e0>] note_interrupt+0x220/0x280
[ 53.934411] [<ffffffff802bdf9a>] handle_fasteoi_irq+0xca/0x120
[ 53.934417] [<ffffffff8026223c>] call_softirq+0x1c/0x28
[ 53.934426] [<ffffffff80270189>] do_IRQ+0x89/0x100
[ 53.934429] [<ffffffff8026e860>] default_idle+0x0/0x50
[ 53.934434] [<ffffffff80261631>] ret_from_intr+0x0/0xa
[ 53.934437] <EOI> [<ffffffff8026e889>] default_idle+0x29/0x50
[ 53.934453] [<ffffffff8024b15b>] cpu_idle+0x9b/0xd0
[ 53.934461] [<ffffffff805707ca>] start_kernel+0x24a/0x260
[ 53.934466] [<ffffffff80570163>] _sinittext+0x163/0x170
[ 53.934471]
[ 53.934472] handlers:
[ 53.934475] [<ffffffff88290330>] (cx8800_irq+0x0/0x250 [cx8800])
[ 53.934486] [<ffffffff8829b220>] (cx8802_irq+0x0/0x2c0 [cx8802])
[ 53.934495] [<ffffffff88426470>] (via_driver_irq_handler+0x0/0x1b0 [via])
[ 53.934503] Disabling IRQ #16

[Jérôme Guelfucci (jerome-guelfucci-deactivatedaccount)]

Ok thank you.

1. Please include the output of the command "uname -a" in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
2. Please run the command "dmesg > dmesg.log" and attach the resulting file "dmesg.log" to this bug report.
3. Please run the command "lspci -vvnn > lspci-vvnn.log" and attach the resulting file "lspci-vvnn.log" to this bug report.

Have you tried with the "irqpoll" option as advised in the logs ?

[Patrick Dixon (patrick-dixon)]

dixon@mediaserver:~$ uname -a
Linux mediaserver 2.6.20-16-generic #2 SMP Thu Jun 7 19:00:28 UTC 2007 x86_64 GNU/Linux

Yes I did try irqpoll, but it didn't solve the problem and may (can't remember offhand) have created others. I tried a number of other kernel options, but the only one that worked was noirqpoll.

[Patrick Dixon (patrick-dixon)]

Sorry - ignore previous lspci-vvnn.log

Here's the correct one.

[Patrick Dixon (patrick-dixon)]

Oops - sorry, these are with noirqpoll

I'll post the dmesg without when I get a chance to reboot the system shortly.

Thanks for looking at this btw.

[Jérôme Guelfucci (jerome-guelfucci-deactivatedaccount)]

Ok, I'm marking this as confirmed, and assigning to the kernel acpi team, hopefully someone will have a look at this.

[goto (gotolaunchpad)]

 [noob]

I am having the same Problem on a Thinkpad T61 with Kernel 2.6.22-rc3 and previous ones...just wanted to mention it :)

[Leann Ogasawara (leannogasawara)]

This bug was reported a while ago but there hasn't been any recent activity. We're just curious if this is still an issue in the latest Hardy Heron Alpha release? Hardy contains an updated version of the kernel. You can download and try the new Hardy Heron Alpha release from http://cdimage.ubuntu.com/releases/hardy/ . You should be able to then test the new kernel via the LiveCD. If you can, please verify if this bug still exists or not and report back your results. General information regarding the release can also be found here: http://www.ubuntu.com/testing/ .

Also, we will keep this report open against the actively developed kernel bug against 2.6.20 this will be closed. Thanks.

[Patrick Dixon (patrick-dixon)]

Let's be honest here: this bug was logged over a year ago and no one is really interested in investigating it!

I've updated kernels a few times on Feisty and it remains, and I doubt it will 'just go away' without someone trying to reproduce it and figure out what's causing it!

[Daniel Pittman (daniel-rimspace)]

Leann Ogasawara <email address hidden> writes:

> This bug was reported a while ago but there hasn't been any recent
> activity. We're just curious if this is still an issue in the latest
> Hardy Heron Alpha release?

No, the problem has not shown up recently. Thank you for reminding me
about this, and at this stage I believe that it is no longer relevant to
me, at least.

Regards,
        Daniel

[Leann Ogasawara (leannogasawara)]

Thanks for the update Daniel. Since you are the original bug reporter I'm going to go ahead and close this report against the Hardy kernel. Thanks.

[wateenellende (fpbeekhof)]

I've got an A8V board, and I'm trying to resolve bug https://bugs.launchpad.net/bugs/256316 , so I flashed the BIOS yesterday. Ever since, I've been affected by this bug. (On Intrepid)

Can this bug be reopened ?