[Edgy] APIC error on CPU0

[Stéphane Marguet]

dmesg show me multiple messages of :
APIC error on CPU0: 40(40)
and sometime
APIC error on CPU0: 00(40)

Ubuntu Edgy Beta (with updates) kernel 2.6.17-10-generic

[Stéphane Marguet (stemp)]

I think it's getting worse. More and more of these messages.

[James Tait (jamestait)]

I have the same here. Roughly 3-4 instances of this message per second in syslog. I noticed something in the boot log:

Oct 27 09:57:09 ferrari kernel: [ 20.545479] PCI: Ignoring BAR0-3 of IDE controller 0000:00:14.1
Oct 27 09:57:09 ferrari kernel: [ 20.546417] PCI: Transparent bridge - 0000:00:14.4
Oct 27 09:57:09 ferrari kernel: [ 20.546479] PCI: Bus #07 (-#0a) is hidden behind transparent bridge #06 (-#07) (try 'pci=assign-busses')
Oct 27 09:57:09 ferrari kernel: [ 20.546482] Please report the result to linux-kernel to fix this permanently
...
...
Oct 27 09:57:09 ferrari kernel: [ 20.554087] ACPI: Embedded Controller [EC0] (gpe 16) interrupt mode.
Oct 27 09:57:09 ferrari kernel: [ 21.726612] Linux Plug and Play Support v0.97 (c) Adam Belay
Oct 27 09:57:09 ferrari kernel: [ 21.726619] pnp: PnP ACPI init
Oct 27 09:57:09 ferrari kernel: [ 21.730635] pnp: PnP ACPI: found 12 devices
Oct 27 09:57:09 ferrari kernel: [ 21.730680] PCI: Using ACPI for IRQ routing
Oct 27 09:57:09 ferrari kernel: [ 21.730682] PCI: If a device doesn't work, try "pci=routeirq". If it helps, post a report
Oct 27 09:57:09 ferrari kernel: [ 21.730809] PCI-DMA: Disabling IOMMU.
...
...
Oct 27 09:57:09 ferrari kernel: [ 51.045751] bcm43xx driver
Oct 27 09:57:09 ferrari kernel: [ 51.065157] nsc-ircc, chip->init
Oct 27 09:57:09 ferrari kernel: [ 51.065173] nsc-ircc, Found chip at base=0x02e
Oct 27 09:57:09 ferrari kernel: [ 51.065219] nsc-ircc, driver loaded (Dag Brattli)
Oct 27 09:57:09 ferrari kernel: [ 51.065226] nsc_ircc_open(), can't get iobase of 0x2f8
Oct 27 09:57:09 ferrari kernel: [ 51.065279] nsc-ircc, Found chip at base=0x02e
Oct 27 09:57:09 ferrari kernel: [ 51.065324] nsc-ircc, driver loaded (Dag Brattli)
Oct 27 09:57:09 ferrari kernel: [ 51.065327] nsc_ircc_open(), can't get iobase of 0x2f8
Oct 27 09:57:09 ferrari kernel: [ 51.065605] pnp: Device 00:09 disabled.
Oct 27 09:57:09 ferrari kernel: [ 51.155081] ACPI: PCI Interrupt 0000:00:14.6[B] -> GSI 17 (level, low) -> IRQ 209
Oct 27 09:57:09 ferrari kernel: [ 51.167668] ACPI: PCI Interrupt 0000:06:02.0[A] -> GSI 21 (level, low) -> IRQ 233

I know ACPI != APIC, but the message I noticed (I'm not sure yet where it is, I got it in the logcheck mail which I deleted before I saw the APIC error messages) was something along the lines of "noone cares, disabling IRQ 233", which is mentioned above.

Output of lspci:

jtait@ferrari:~$ lspci
00:00.0 Host bridge: ATI Technologies Inc ATI Radeon Xpress 200 (RS480/RS482/RX480/RX482) Chipset - Host bridge (rev 01)
00:02.0 PCI bridge: ATI Technologies Inc RS480 PCI-X Root Port
00:06.0 PCI bridge: ATI Technologies Inc RS480 PCI Bridge
00:13.0 USB Controller: ATI Technologies Inc IXP SB400 USB Host Controller
00:13.1 USB Controller: ATI Technologies Inc IXP SB400 USB Host Controller
00:13.2 USB Controller: ATI Technologies Inc IXP SB400 USB2 Host Controller
00:14.0 SMBus: ATI Technologies Inc IXP SB400 SMBus Controller (rev 11)
00:14.1 IDE interface: ATI Technologies Inc Standard Dual Channel PCI IDE Controller ATI
00:14.3 ISA bridge: ATI Technologies Inc IXP SB400 PCI-ISA Bridge
00:14.4 PCI bridge: ATI Technologies Inc IXP SB400 PCI-...

[James Tait (jamestait)]

Just rebooted and getting the same error. The error I was trying to find was in dmesg output:

[ 20.014050] irq 233: nobody cared (try booting with the "irqpoll" option)
[ 20.014055]
[ 20.014056] Call Trace: <IRQ> <ffffffff80265d08>{ret_from_intr+0}
[ 20.014065] <ffffffff802b68a5>{__report_bad_irq+53} <ffffffff802b6b20>{note_interrupt+544}
[ 20.014081] <ffffffff802b6190>{__do_IRQ+224} <ffffffff802737e2>{do_IRQ+66}
[ 20.014089] <ffffffff8803d659>{:processor:acpi_processor_idle+0}
[ 20.014100] <ffffffff80265d08>{ret_from_intr+0} <EOI> <ffffffff80359d0b>{acpi_hw_register_write+371}
[ 20.014112] <ffffffff8803d832>{:processor:acpi_processor_idle+473}
[ 20.014120] <ffffffff8803d659>{:processor:acpi_processor_idle+0}
[ 20.014127] <ffffffff8803d659>{:processor:acpi_processor_idle+0}
[ 20.014134] <ffffffff8024ecfe>{cpu_idle+158} <ffffffff8060885b>{start_kernel+523}
[ 20.014144] <ffffffff80608293>{_sinittext+659}
[ 20.014148] handlers:
[ 20.014151] [<ffffffff881190c0>] (ohci_irq_handler+0x0/0x7ff [ohci1394])
[ 20.014160] Disabling IRQ #233

I presume from the reference to ohci1394 that the Firewire connector is involved somewhere here? Certainly when I plug in a DV camcorder via the IEEE1394 port it doesn't appear to be detected -- nothing in /var/log/messages or dmesg.

[James Tait (jamestait)]

Booting with the "irqpoll" option gives a significant reduction in the number of these messages, although they're not completely eliminated. Also, plugging in the DV camcorder via the IEEE1394 socket, I now get entries in dmesg, although I can't currently capture the video playback from the camera using Kino. However, dvgrab does appear to work.

I'm not entirely sure what the irqpoll option actually does though, so I'm a little uncomfortable with it. Call me paranoid, but I do like to know what my computer's doing. ;)

[James Tait (jamestait)]

For what it's worth, I just upgraded my (Acer Ferrari 4005 WLMi) laptop's BIOS from 3A19 to 3A23 and it had no effect on this.

[James Tait (jamestait)]

However, the BIOS update combined with the irqpoll kernel option at boot does appear to solve it. I've just tested with my DV camcorder, which works, and still no instances of the APIC error message.

[James Tait (jamestait)]

Upgrading to Feisty (linux-image-2.6.20-9-generic) greatly reduces the frequency of these messages.

[Launchpad Janitor (janitor)]

The 18 month support period for Edgy Eft 6.10 has reached its end of life. As a result, we are closing the linux-source-2.6.17 Edgy Eft kernel task. 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!