irq 11: nobody cared (try booting with the "irqpoll" option)

Same problem for me, too.
I get the error with IRQ 9, after playing something with xmms for about 10 seconds..
I tried booting with 'pci=nomsi', 'pci=assign-busses' and 'noapic'.
But only irqpoll gives me a working wireless and audio card, even if the sound is still discontinued.

I also reported the bug here:
https://launchpad.net/ubuntu/+source/alsa-driver/+bug/88080
but the changes haven't solved my problem.

What should I do?
Should I attach here my dmesg and lspci?

Thank you

Hi, found some more stuff, maybe this has something to do with it.

[ 8.845436] PCI quirk: region 1000-107f claimed by ICH6 ACPI/GPIO/TCO
[ 8.845485] PCI quirk: region 1300-133f claimed by ICH6 GPIO

[ 8.846167] PCI: Transparent bridge - 0000:00:1e.0
[ 8.846274] PCI: Bus #07 (-#0a) is hidden behind transparent bridge #06 (-#06) (try 'pci=assign-busses')
[ 8.846329] Please report the result to linux-kernel to fix this permanently

(OK, it is only copied from my dmesg, but I think it has something to do with the Texas Instruments PCIxx21 Integrated FlashMedia Controller and the transparent bridge) But it is also possible that I am very wrong. I'm just guessing.

More info for the apic

[ 8.393662] Local APIC disabled by BIOS -- you can enable it with "lapic"

The problem appears on a Laptop with limited bios settings (actually I can only set the Time and the boot order). I also tried to use a fixed DSDT Table from http://acpi.sourceforge.net/ . But this also didn't help.

@svetj
Sorry I can't help you further. I read your thread and found some useful info for my problem, but don't know if the problems have something in common. Because my sound is working fine even without irqpoll. So thanks for your answer anyway.

And thanks to those who trying to solve this problem.

And some more information, I tried again the different boot options and saved all the dmesg from every case. But his would be to much to post, contact me if you need one.

booted with no options:
- sound is working
- usb - mouse is not usable
- no wireless network
- processor is speedsteping
- system preformance is ok

booted with lapic:
- sound is working
- usb - mouse is not usable
- no wireless network
- processor is working on full throttle
- system preforming very slow

booted with pci=routeirq:
- sound is working
- usb - mouse is not usable
- no wireless network

booted with pci=assign-busses:
- sound is working
- usb - mouse is not usable
- no wireless network

booted with acpi=off:
- sound is working
- usb - mouse _is_ usable
- no wireless network
- processor is speedsteping
- processor thermal sensors are missing (no surprise)

booted with pci=noacpi:
- everything is working fine (sound, sensors, speedsteping, wireless)

At this point I will leave the last option as boot option. I think it will be better than the irqpoll option. I didn't tried to mix the boot options. But I will further test this settings.

@ svetj

i found something, but can't tell if it will work for you. And it looks very dangerous, but anyway have a look:

http://www.cpqlinux.com/acpi-howto.html#irq9_hack

Or try it with "pci=biosirq".

-------
On more thing to my problem:

Now I'm using the pci=noacpi and when I choose reboot from a running system the newly booted system behaves like in the other cases (unusable usb mouse and no wireless), but if I choose shutdown and start the system by power button everything works fine.
I also choose a new Bios version and checked the DSDT Table, but there were no errors in it only one warning. So no need for fixing it. Or not?

Thank you a lot dansh!
Unfortunately the first tip is only for old kernel 2.4,
and no lucky also with the boot parameter biosriq :-(

I think I must open a new bug...

bye ;-)

OK but I tried. Couldn't find any new information. But it seems like a common problem. Did you ever try to fix your possibly broken dsdt table like describe in http://acpi.sourceforge.net/ ?
Maybe this won't fix everything but a part of it? I'm not that experienced to give valuable advices.
Greetings Dan

For those who are using pci=assign-buses can you attach the output of sudo dmidecode > dmidecode.

Thanks
chuck

Hi,
normally I'm using the irqpoll option because as I have written with pci=assign-buses in an older post my USB-mouse and the wireless LAN aren't working. I changed irqpoll at boot to pci=assign-buses just to give you a feedback.
I hope my dmidecode is exploitable even if I'm computer isn't properly usable with pci=assign-busses.
(By the way: I know there is a newer version of the Bios for my system, but I have to downgrade to an older version because the new one is very crappy.)
Thanks for taking care of my problem
Dan

I've discovered the similar problem on HP Pavilion DV9266EU. After the "disabling IRQ"-message my laptop doesn't recognize newly plugged in devices.

I'm booting the kernel with noapic, because the laptop wouldn't start up without that option.

The relevant dmesg part is:
[19709.680000] irq 7: nobody cared (try booting with the "irqpoll" option)
[19709.680000] [<c015b5d4>] __report_bad_irq+0x24/0x80
[19709.680000] [<c015b892>] note_interrupt+0x262/0x2a0
[19709.680000] [<f88f96c2>] usb_hcd_irq+0x22/0x60 [usbcore]
[19709.680000] [<c015aaf0>] handle_IRQ_event+0x30/0x60
[19709.680000] [<c015c4ab>] handle_level_irq+0xdb/0x110
[19709.680000] [<c0106b1b>] do_IRQ+0x3b/0x70
[19709.680000] [<c0102e00>] default_idle+0x0/0x60
[19709.680000] [<c0105223>] common_interrupt+0x23/0x30
[19709.680000] [<c0102e00>] default_idle+0x0/0x60
[19709.680000] [<c011dba2>] native_safe_halt+0x2/0x10
[19709.680000] [<c0102e3c>] default_idle+0x3c/0x60
[19709.680000] [<c0102413>] cpu_idle+0x53/0xe0
[19709.680000] =======================
[19709.680000] handlers:
[19709.680000] [<f88f96a0>] (usb_hcd_irq+0x0/0x60 [usbcore])
[19709.680000] Disabling IRQ #7

i got the same error when connecting a device to the internal usb port

apperances:
[ 102.996000] Bluetooth: RFCOMM ver 1.8
[ 121.388000] irq 11: nobody cared (try booting with the "irqpoll" option)
[ 121.388000] [<c015b594>] __report_bad_irq+0x24/0x80
[ 121.388000] [<c015b852>] note_interrupt+0x262/0x2a0
[ 121.388000] [<c015aab0>] handle_IRQ_event+0x30/0x60
[ 121.388000] [<c015c46b>] handle_level_irq+0xdb/0x110
[ 121.388000] [<c0106b1b>] do_IRQ+0x3b/0x70
[ 121.388000] [<c0105223>] common_interrupt+0x23/0x30
[ 121.388000] [<c012d68b>] __do_softirq+0x5b/0x110
[ 121.388000] [<c012d795>] do_softirq+0x55/0x60
[ 121.388000] [<c012da7d>] irq_exit+0x6d/0x80
[ 121.388000] [<c0106b20>] do_IRQ+0x40/0x70
[ 121.388000] [<c013173b>] get_next_timer_interrupt+0x1ab/0x230
[ 121.388000] [<c0105223>] common_interrupt+0x23/0x30
[ 121.388000] [<c013007b>] sys_capset+0x12b/0x2e0
[ 121.388000] [<f003a99a>] acpi_processor_idle+0x24f/0x425 [processor]
[ 121.388000] [<f003a74b>] acpi_processor_idle+0x0/0x425 [processor]
[ 121.388000] [<c0102413>] cpu_idle+0x53/0xe0
[ 121.388000] [<c03e3a85>] start_kernel+0x325/0x3b0
[ 121.388000] [<c03e31f0>] unknown_bootoption+0x0/0x260
[ 121.388000] =======================
[ 121.388000] handlers:
[ 121.388000] [<f00706a0>] (usb_hcd_irq+0x0/0x60 [usbcore])
[ 121.388000] [<f00706a0>] (usb_hcd_irq+0x0/0x60 [usbcore])
[ 121.388000] [<f00706a0>] (usb_hcd_irq+0x0/0x60 [usbcore])
[ 121.388000] [<f00907f0>] (e100_intr+0x0/0xd0 [e100])
[ 121.388000] [<f01388e0>] (yenta_interrupt+0x0/0xe0 [yenta_socket])
[ 121.388000] [<f040d640>] (snd_intel8x0_interrupt+0x0/0x240 [snd_intel8x0])
[ 121.388000] Disabling IRQ #11

some seconds after connecting the device the interrupt becomes disabled.

i tryed the irqpoll parameter, wich works most of the time for me with the disadvantage of slowing down the system noteably.

other parameters i tryed are:
-------------------------------------
acpi=noirq
acpi=off apm=on : results in a kernel panic > posted in next comment
acpi=force pci=noacpi
lapic
lapic + no_timer_check
pci=noacpi
pci=noearly
pci=routeirq
uhci-hcd.ignore_oc
noirqdebug
ec_intr=0
nosmp
acpi_irq_reserve=11
acpi_serialize
pci=nobios
pci=biosirq
pnpacpi=off
pnpbios=curr
acpi_fake_ecdt

i also fixed my DSDT, but without any luck :-)

any other ideas ?

Thanks, Joe

Marked "confirmed" based on availability of required logs.

I'm having the same problem on Gutsy, and also had it on Feisty with the same hardware - system boots OK, but a freeze happens on the on-board Ethernet, some USB and all IDE drives. This takes a day or so after I connect an internal USB flash card reader, and hasn't happened for over 10 days with this device disconnected. Relevant dmesg output is:

May 21 06:11:35 valluga kernel: [39107.154068] irq 16: nobody cared (try booting with the "irqpoll" option)
May 21 06:11:35 valluga kernel: [39107.154084] [__report_bad_irq+36/128] __report_bad_irq+0x24/0x80
May 21 06:11:35 valluga kernel: [39107.154100] [note_interrupt+610/672] note_interrupt+0x262/0x2a0
May 21 06:11:35 valluga kernel: [39107.154116] [handle_IRQ_event+48/96] handle_IRQ_event+0x30/0x60
May 21 06:11:35 valluga kernel: [39107.154127] [handle_fasteoi_irq+187/240] handle_fasteoi_irq+0xbb/0xf0
May 21 06:11:35 valluga kernel: [39107.154139] [do_IRQ+59/112] do_IRQ+0x3b/0x70
May 21 06:11:35 valluga kernel: [39107.154145] [irq_exit+81/128] irq_exit+0x51/0x80
May 21 06:11:35 valluga kernel: [39107.154148] [smp_apic_timer_interrupt+85/128] smp_apic_timer_interrupt+0x55/0x80
May 21 06:11:35 valluga kernel: [39107.154162] [common_interrupt+35/48] common_interrupt+0x23/0x30
May 21 06:11:35 valluga kernel: [39107.154195] =======================
May 21 06:11:35 valluga kernel: [39107.154196] handlers:
May 21 06:11:35 valluga kernel: [39107.154197] [<f88b26a0>] (usb_hcd_irq+0x0/0x60 [usbcore])
May 21 06:11:35 valluga kernel: [39107.154212] [<f892c600>] (ata_interrupt+0x0/0x200 [libata])
May 21 06:11:35 valluga kernel: [39107.154227] [<f88d1e60>] (rtl8169_interrupt+0x0/0x410 [r8169])
May 21 06:11:35 valluga kernel: [39107.154236] Disabling IRQ #16
May 21 06:12:06 valluga kernel: [39138.396862] ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
May 21 06:12:06 valluga kernel: [39138.396870] ata5.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0
May 21 06:12:06 valluga kernel: [39138.396872] res 40/00:02:08:08:00/00:00:00:00:00/a0 Emask 0x4 (timeout)
May 21 06:12:06 valluga kernel: [39138.396885] ata5: soft resetting port
May 21 06:12:37 valluga kernel: [39168.482133] ata5.01: qc timeout (cmd 0x27)
May 21 06:12:37 valluga kernel: [39168.482142] ata5.01: ata_hpa_resize 1: hpa sectors (0) is smaller than sectors (488397168)
May 21 06:12:37 valluga kernel: [39168.637696] ata5.00: failed to IDENTIFY (I/O error, err_mask=0x40)
May 21 06:12:37 valluga kernel: [39168.637699] ata5.00: revalidation failed (errno=-5)
May 21 06:12:37 valluga kernel: [39168.637702] ata5: failed to recover some devices, retrying in 5 secs
May 21 06:12:42 valluga kernel: [39173.628634] ata5: soft resetting port
May 21 06:13:12 valluga kernel: [39203.713907] ata5.01: qc timeout (cmd 0x27)
May 21 06:13:12 valluga kernel: [39203.713916] ata5.01: ata_hpa_resize 1: hpa sectors (0) is smaller than sectors (488397168)
May 21 06:13:12 valluga kernel: [39203.869476] ata5.00: failed to IDENTIFY (I/O error, err_mask=0x40)
May 21 06:13:12 valluga kernel: [39203.869479] ata5.00: revalidation failed (errno=-5)
May 21 06:13:12 valluga kernel: [39203.869484] ata5.00: limiting speed to UDMA/33:PIO3
...

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this bug to the new "linux" package. However, development has already began for the upcoming Intrepid Ibex 8.10 release. It would be helpful if you could test the upcoming release and verify if this is still an issue - http://www.ubuntu.com/testing . If the issue still exists, please update this report by changing the Status of the "linux" task from "Incomplete" to "New". We appreciate your patience and understanding as we make this transition. Thanks!

Hi, I open this bug, but it is very old I think. So I think I can close or delete the bug. And I can't confirm if this bug still exists, because I sold the computer on which I had this bug. Also the status won't fix, is a bad indication. But thanks anyway.