nobody cares about via interrupt

[John Moser]

Well I thought I reported it before. I guess it was just a part of another report (I did have excess dmesg in one...).

This appears to be Linux Kernel Bug 6419 at http://bugzilla.kernel.org/show_bug.cgi?id=6419

Linux icebox 2.6.17-10-generic #2 SMP Fri Oct 6 00:36:14 UTC 2006 i686
GNU/Linux

[18142714.092000] agpgart: Found an AGP 3.0 compliant device at 0000:00:00.0.
[18142714.092000] agpgart: Xorg tried to set rate=x12. Setting to AGP3 x8 mode.
[18142714.092000] agpgart: Putting AGP V3 device at 0000:00:00.0 into 8x mode
[18142714.092000] agpgart: Putting AGP V3 device at 0000:01:00.0 into 8x mode
[18142714.652000] irq 201: nobody cared (try booting with the "irqpoll" option)
[18142714.652000] <c01499b4> __report_bad_irq+0x24/0x80 <c0149aad> note_interrupt+0x9d/0x270
[18142714.652000] <c0149333> handle_IRQ_event+0x33/0x60 <c0149458> __do_IRQ+0xf8/0x110
[18142714.652000] <c0105c89> do_IRQ+0x19/0x30 <c010408a> common_interrupt+0x1a/0x20
[18142714.652000] <c0102080> default_idle+0x0/0x60 <c01020aa> default_idle+0x2a/0x60
[18142714.652000] <c0102122> cpu_idle+0x42/0xb0 <c03f07a1> start_kernel+0x321/0x3a0
[18142714.652000] <c03f0210> unknown_bootoption+0x0/0x270
[18142714.652000] handlers:
[18142714.652000] [<f8e31490>] (via_driver_irq_handler+0x0/0x1d0 [via])
[18142714.652000] Disabling IRQ #201

[John Moser (nigelenki)]

LSPCI and /proc/interrupts below, someone said this would be useful.

bluefox@icebox:~/programming/olpc/perf$ lspci
00:00.0 Host bridge: VIA Technologies, Inc. K8M800 Host Bridge
00:00.1 Host bridge: VIA Technologies, Inc. K8M800 Host Bridge
00:00.2 Host bridge: VIA Technologies, Inc. K8M800 Host Bridge
00:00.3 Host bridge: VIA Technologies, Inc. K8M800 Host Bridge
00:00.4 Host bridge: VIA Technologies, Inc. K8M800 Host Bridge
00:00.7 Host bridge: VIA Technologies, Inc. K8M800 Host Bridge
00:01.0 PCI bridge: VIA Technologies, Inc. VT8237 PCI bridge [K8T800/K8T890 South]
00:09.0 Multimedia audio controller: Creative Labs SB Audigy (rev 03)
00:09.2 FireWire (IEEE 1394): Creative Labs SB Audigy FireWire Port
00:0f.0 RAID bus controller: VIA Technologies, Inc. VIA VT6420 SATA RAID Controller (rev 80)
00:0f.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06)
00:10.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81)
00:10.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81)
00:10.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81)
00:10.3 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81)
00:10.4 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 86)
00:11.0 ISA bridge: VIA Technologies, Inc. VT8237 ISA bridge [KT600/K8T800/K8T890 South]
00:13.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration
00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map
00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller
00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control
01:00.0 VGA compatible controller: VIA Technologies, Inc. S3 Unichrome Pro VGA Adapter (rev 01)

bluefox@icebox:~/programming/olpc/perf$ cat /proc/interrupts
           CPU0
  0: 19245959 IO-APIC-edge timer
  1: 105408 IO-APIC-edge i8042
  8: 3 IO-APIC-edge rtc
  9: 0 IO-APIC-level acpi
 15: 27811602 IO-APIC-edge ide1
169: 129574 IO-APIC-level libata
177: 244889 IO-APIC-level ohci1394, eth0
185: 551481 IO-APIC-level uhci_hcd:usb1, uhci_hcd:usb2, uhci_hcd:usb3, uhci_hcd:usb4, ehci_hcd:usb5
193: 5603443 IO-APIC-level EMU10K1
201: 100000 IO-APIC-level via@pci:0000:01:00.0
NMI: 0
LOC: 19246832
ERR: 0
MIS: 0

[Chuck Short (zulcss)]

Have you tried what the dmesg has suggested?

[John Moser (nigelenki)]

Yes, it causes the kernel to not boot.

[Jacob Nevins (0jacobnk-ulp)]

I ran into this error message and problem straight after installing Dapper. "irqpoll" didn't help me either (the machine hung hard instead).

I notice that your /proc/interrupts has a suspiciously round number. I found that when an interrupt packed in (for me it was usually USB or sound, with concomitant symptoms), the interrupt count displayed in /proc/interrupts was *always* a multiple of 100000 (and sometimes implausibly large). For instance, see IRQs 11 and 185:

$ cat /proc/interrupts
           CPU0
  0: 2455783 IO-APIC-edge timer
  1: 3979 IO-APIC-edge i8042
  7: 0 IO-APIC-edge parport0
  8: 3 IO-APIC-edge rtc
  9: 1 IO-APIC-level acpi
 11: 200000 IO-APIC-level uhci_hcd:usb1, uhci_hcd:usb2
 12: 78674 IO-APIC-edge i8042
 14: 15828 IO-APIC-edge ide0
 15: 266079 IO-APIC-edge ide1
169: 1080436 IO-APIC-level nvidia
177: 146 IO-APIC-level eth0
185: 600000 IO-APIC-level Ensoniq AudioPCI
NMI: 0
LOC: 2455610
ERR: 0
MIS: 0

For me, the workaround is to add "noapic nolapic" to my kernel command line. (May be a sledgehammer to crack a nut, but it works. I got it from Wikipedia, of all places.)

The motherboard is an MSI K7T Turbo2. (I can post lspci type spew if anyone's interested.)

Hope this info helps somebody. This was very frustrating until I found the workaround.

[Sitsofe Wheeler (sitsofe)]

Jacob:
Does using nolapic by itself also solve the problem?

[Jacob Nevins (0jacobnk-ulp)]

Yes, I think so. I've run two long sessions recently (both around 14 hours) with just "nolapic" without problems. I think that the problem would normally have become evident in that time. I will change the default to just "nolapic" and see if any problems occur.

"nolapic" is certainly sufficient to change /proc/interrupts from "IO-APIC-xxx" to "XT-PIC". I've been unable to distinguish it from "noapic nolapic".

Something else that may (or may not) be relevant: I've just noticed that the message "BIOS bug, local APIC #0 not detected!..." flashes up during the boot sequence, at least with "nolapic". This does not happen with neither "noapic" nor "nolapic". I don't know if it happens with both enabled; it shows in dmesg but doesn't get as far as /var/log/messages, and I haven't checked that combination recently. (I suppose this could just be a poorly-worded message triggered directly by inclusion of "nolapic"; I haven't checked the source.)

[Sitsofe Wheeler (sitsofe)]

John:
Does nolapic help you too?

John/Jacob:
Can you reproduce this problem with later versions of Ubuntu (e.g. the 2.6.20 based 7.04)?

[Launchpad Janitor (janitor)]

[Expired for linux-source-2.6.15 (Ubuntu) because there has been no activity for 60 days.]

[Jacob Nevins (0jacobnk-ulp)]

Sitsofe: I haven't seriously tried anything later than Dapper, I'm afraid.

(FWIW, I've been running with just "nolapic" since my previous comment in June, with no problems.)