irq 16: nobody cared (try booting with the "irqpoll" option) - but irqpoll causes boot failure

Version: OpenSuse 11.4 x64
I installed a USB 2.x card in my only PCI slot, and since then IRQ 16/17 keep showing these errors.

If I attempt to use the “irqpoll” option, the boot fails with messages such as /dev/sda read/write failure (hex). It isn’t logged, so it isn’t like I can do a screen capture of the error. But it fails utterly if the option is attempted.

I’ve tried apm=off, pci=routeirq but neither seem to make any real change. When I had my mice on the 2.x card when the IRQ(s) failed, it would turn the entire system into slow motion land. After moving the mice back to the legacy USB 1.1 ports, I don’t have a slowdown on mouse input, but since the AGP Radeon card utilizes IRQ 17, there is a few seconds hesitation before the screen will re-write and respond to input.

I would prefer to resolve this while keeping the USB 2.x card installed. Webcam video is horrible with the 1.1 ports so skype sessions with my sons overseas become quite choppy without it.

Suggestions are welcome. (Note: Tyan S2885 dual cpu board “Thunder K8W” with the latest BIOS revisions installed)

Output from message log.
Jun 28 19:34:22 saul kernel: 7995.555356] irq 16: nobody cared (try booting with the “irqpoll” option)
Jun 28 19:34:22 saul kernel: 7995.555364] Pid: 0, comm: kworker/0:1 Not tainted 2.6.37.6-0.5-desktop #1
Jun 28 19:34:22 saul kernel: 7995.555367] Call Trace:
Jun 28 19:34:22 saul kernel: 7995.555388] <ffffffff810059b9>] dump_trace+0x79/0x340
Jun 28 19:34:22 saul kernel: 7995.555397] <ffffffff81521752>] dump_stack+0x69/0x6f
Jun 28 19:34:22 saul kernel: 7995.555405] <ffffffff810cb38e>] __report_bad_irq+0x1e/0x90
Jun 28 19:34:22 saul kernel: 7995.555410] <ffffffff810cb5a9>] note_interrupt+0x1a9/0x200
Jun 28 19:34:22 saul kernel: 7995.555417] <ffffffff810cc545>] handle_fasteoi_irq+0x105/0x140
Jun 28 19:34:22 saul kernel: 7995.555422] <ffffffff810058b5>] handle_irq+0x15/0x20
Jun 28 19:34:22 saul kernel: 7995.555427] <ffffffff810054fe>] do_IRQ+0x5e/0xe0
Jun 28 19:34:22 saul kernel: 7995.555433] <ffffffff81524fd3>] ret_from_intr+0x0/0xa
Jun 28 19:34:22 saul kernel: 7995.555441] <ffffffff8100b794>] default_idle+0x44/0x230
Jun 28 19:34:22 saul kernel: 7995.555447] <ffffffff8100125c>] cpu_idle+0x4c/0xa0
Jun 28 19:34:22 saul kernel: 7995.555452] handlers:
Jun 28 19:34:22 saul kernel: 7995.555453] <ffffffff81385410>] (usb_hcd_irq+0x0/0x70)
Jun 28 19:34:22 saul kernel: 7995.555458] <ffffffffa0111f00>] (radeon_driver_irq_handler_kms+0x0/0x20 [radeon])
Jun 28 19:34:22 saul kernel: 7995.555505] Disabling IRQ #16
Jun 28 19:37:16 saul kernel: 8169.349744] irq 17: nobody cared (try booting with the “irqpoll” option)
Jun 28 19:37:16 saul kernel: 8169.349753] Pid: 0, comm: kworker/0:1 Not tainted 2.6.37.6-0.5-desktop #1
Jun 28 19:37:16 saul kernel: 8169.349756] Call Trace:
Jun 28 19:37:16 saul kernel: 8169.349780] <ffffffff810059b9>] dump_trace+0x79/0x340
Jun 28 19:37:16 saul kernel: 8169.349788] <ffffffff81521752>] dump_stack+0x69/0x6f
Jun 28 19:37:16 saul kernel: 8169.349796] <ffffffff810cb38e>] __report_bad_irq+0x1e/0x90
Jun 28 19:37:16 saul kernel: 8169.349802] <ffffffff810cb5a9>] note_interrupt+0x1a9/0x200
Jun 28 19:37:16 saul kernel: 8169.349808] <ffffffff810cc545>] handle_fasteoi_irq+0x105/0x140
Jun 28 19:37:16 saul kernel: 8169.349814] <ffffffff810058b5>] handle_irq+0x15/0x20
Jun 28 19:37:16 saul kernel: 8169.349818] <ffffffff810054fe>] do_IRQ+0x5e/0xe0
Jun 28 19:37:16 saul kernel: 8169.349825] <ffffffff81524fd3>] ret_from_intr+0x0/0xa
Jun 28 19:37:16 saul kernel: 8169.349832] <ffffffff8108aa5b>] tick_nohz_stop_sched_tick+0x28b/0x3d0
Jun 28 19:37:16 saul kernel: 8169.349840] <ffffffff81001242>] cpu_idle+0x32/0xa0
Jun 28 19:37:16 saul kernel: 8169.349844] handlers:
Jun 28 19:37:16 saul kernel: 8169.349846] <ffffffff81385410>] (usb_hcd_irq+0x0/0x70)
Jun 28 19:37:16 saul kernel: 8169.349851] <ffffffffa000ac60>] (sil_interrupt+0x0/0x94 [sata_sil])
Jun 28 19:37:16 saul kernel: 8169.349875] <ffffffffa0085560>] (azx_interrupt+0x0/0x1a0 [snd_hda_intel])
Jun 28 19:37:16 saul kernel: 8169.349882] <ffffffffa01ce640>] (snd_intel8x0_interrupt+0x0/0x2e0 [snd_intel8x0])
Jun 28 19:37:16 saul kernel: 8169.349888] Disabling IRQ #17

I suggest to check your PNP BIOS setup perhaps first and even try a toggle to the opposite setting. You might do a clear CMOS (A temporary jumper setting with the power cord pulled from PC or real power switch turned off). Make sure to note the original settings such as for networking, hard disks, boot order, sound chip enable/disable position, SATA port setting (IDE or AHCI) and so forth. Often adding in a new card can cause odd IRQ settings that a CMOS clear can reset. Try a different card slot if more than one choice exists. Since this started with the addition of hardware, I would look for a hardware solution first.

Thank You,

this is a symptom i have also with no real impact on the system, similar in that video is handled by a ATI 3859HD(agp) and there is a lot of hardware plugged into this box… four HD’s, scanner, printer, and 4 or 5 USB2 devices. This is on an Asus MB.

this box runs for days without complaint until i play a video with VLC and within ten seconds i get the same irqpoll error 17. Nothing quits or slows down however…

until i saw this post, i was just mildly suspicious of the latest flgrx drivers since this started about Catalyst 11.3 and “technically” i don’t think the latest drivers are claimed to support older AGP cards even if the chipset IS supported in PCI-E.

i suspect you are not using fglrx, so perhaps there is some other culprit involved and i’ll investigate some and post back if i find anything interesting.

@j_xavier - no, using the Linux drivers for the radeon. IRQ 17 effects my video though and slows video response down greatly. As noted, both 16 & 17 are also shared by the USB 2.x card along my with SATA drives.

@jcmcdaniel13 - I realize it probably will end where I have to pull the card out. It would be a shame because I purchased it exclusively to speed up the webcam frame rate (which it does a marvelous job). Quite interesting on your suggestion to reset the BIOS, but it makes sense. I will try that first. I’ll just use the Optimize Settings afterward while turning off the floppy (none) and a few other features so all the memory is seen.

I am quite surprised at the problems IRQPOLL caused though. My first IDE drive (boot drive) just sits there with sector read errors which repeat every couple seconds. When I reboot, fsck doesn’t run which makes it even odder (well, I suppose a R/O error wouldn’t cause it).

As mentioned, I just hate pulling the card, but if I can’t find a workaround, that is what I will have to do.

Thanks
Doug