APIC error on CPU0: 40(40)

Bug #314530 reported by Alex Mayorga
30
This bug affects 4 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Won't Fix
Medium
Unassigned

Bug Description

There are lot's of these in dmesg on a Dell Inspiron 1501 with fully updated BIOS at 2.6.3, A16 from http://support.dell.com/support/downloads/download.aspx?c=us&cs=19&l=en&s=dhs&releaseid=R174470&SystemID=INS_PNT_1501&servicetag=&os=WW1&osl=en&deviceid=13120&devlib=0&typecnt=0&vercnt=9&catid=-1&impid=-1&formatcnt=1&libid=1&fileid=236967:

[28299.568004] APIC error on CPU1: 40(40)
[28299.568014] APIC error on CPU0: 40(40)
[28829.068004] APIC error on CPU1: 40(40)
[28829.068016] APIC error on CPU0: 40(40)
[29400.856004] APIC error on CPU1: 40(40)
[29400.856026] APIC error on CPU0: 40(40)
[30967.629008] APIC error on CPU0: 40(40)
[30967.629017] APIC error on CPU1: 40(40)
[31002.672014] APIC error on CPU1: 40(40)
[31002.672030] APIC error on CPU0: 40(40)
[31361.847277] APIC error on CPU0: 40(40)
[31361.847294] APIC error on CPU1: 40(40)
[31377.037024] APIC error on CPU1: 40(40)
[31377.037040] APIC error on CPU0: 40(40)

$ uname -a
Linux inspiron-1501 2.6.27-9-generic #1 SMP Thu Nov 20 21:57:00 UTC 2008 i686 GNU/Linux

ProblemType: Bug
Architecture: i386
DistroRelease: Ubuntu 8.10
Package: linux-image-2.6.27-9-generic 2.6.27-9.19
ProcCmdLine: root=UUID=0f6affdf-cdf2-4884-b986-7215e18c3576 ro quiet splash
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.27-9.19-generic
SourcePackage: linux

Tags: apport-bug
Revision history for this message
Alex Mayorga (alex-mayorga) wrote :
description: updated
Revision history for this message
Connor Imes (ckimes) wrote :

Hi Alex, thanks for filing this. Can you please also add the following as separate attachments?

 * Output of sudo dmidecode (attach dmidecode.txt)
    sudo dmidecode > dmidecode.txt
 * Try to suspend/hibernate and then restart the system and attach /var/log/kern.log.0
 * Tarball of /proc/acpi directory. You can't just tar all files because their content sometimes changes etc.
    cp -r /proc/acpi /tmp
    tar -cvjf ~/acpi.tar.bz /tmp/acpi
then attach acpi.tar.bz from your home directory

Also, please let us know when you are seeing these errors exactly. If you are having trouble booting, can you also please try the steps in section 2.1 "Debugging procedure" at https://wiki.ubuntu.com/DebuggingACPI - particularly the parts about APIC (not the same thing as ACPI).

Thanks in advance.

Changed in linux:
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
Alex Mayorga (alex-mayorga) wrote :

I don't see any particular problem and it boots just fine as far as I can tell, it's just the dmesg getting filled with this messages.

Revision history for this message
Alex Mayorga (alex-mayorga) wrote :
Revision history for this message
Alex Mayorga (alex-mayorga) wrote :
Revision history for this message
Alex Mayorga (alex-mayorga) wrote :
Connor Imes (ckimes)
Changed in linux:
status: Incomplete → Triaged
Revision history for this message
goofy66 (lmgelinas) wrote :

just a me-too, inspiron 1501
Linux bigblue 2.6.27-9-generic #1 SMP Thu Nov 20 22:15:32 UTC 2008 x86_64 GNU/Linux

I am attaching the acpi tarball and dmidecode as requested, I can happilly provide other things...

This bug may occur when accessing a card in the sd card reader. ( the messages poped up when I started coping massive data from dvd -> sd card.

Revision history for this message
goofy66 (lmgelinas) wrote :

dmidecode:

Revision history for this message
Mitchell (mitchellvc) wrote :

Is this bug related to this other?
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/270798
well as far as I have noticed, in my laptop TOSHIBA a215s4767 with intrepid fully updated, AMD turion 64 X2, ATI x1200, 2GB RAM, it happens wit ubuntu kubuntu, 32 bits and 64 bits, well I got rid of it by disabling APIC support at boot, adding this option to the kernel line in grub: noapic.
but I have realized that when I execute some opengl appication (the ones who caused hpet increasing min_delta... as the bug I linked), the video gets some slow, like it reduced the fps. but the hpet and the APIC error on CPUs messages disappeared.
In fact I am working now without the noapic option on my 64 bits intrepid, and i get eventually some lockups and the hpet increasing message, and a bunch of APIC error on CPUs messages, but I can live with it.
I think that this two bugs are related and the two of them have the noapic option as a workaround, but this may alter in some way the behavior of the system, especially when more processing capabilities are required. The system in general may be affected in the performance.

Revision history for this message
Alex Mayorga (alex-mayorga) wrote :

dmesg is still being spammed in a fully updated copy of Jaunty as of today.

Revision history for this message
Igor Starikov (idlesign) wrote :

Confirm the issue on Ubuntu 9.04, Acer Aspire 5005.

Revision history for this message
Steven Ellis (steven-openmedia) wrote :

Same issue with an Aspire 3000 running Jaunty with an AMD Sempron 2800+ CPU.

Revision history for this message
Giacomo (poderi1980) wrote :

I confirm the problem on an Asus a6k.

Linux vger 2.6.28-15-generic #52-Ubuntu SMP Wed Sep 9 10:48:52 UTC 2009 x86_64 GNU/Linux

Revision history for this message
Giacomo (poderi1980) wrote :
Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

This bug report was marked as Triaged a while ago but has not had any updated comments for quite some time. Please let us know if this issue remains in the current Ubuntu release, http://www.ubuntu.com/getubuntu/download . If the issue remains, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

Revision history for this message
Brad Figg (brad-figg) wrote : Unsupported series, setting status to "Won't Fix".

This bug was filed against a series that is no longer supported and so is being marked as Won't Fix. If this issue still exists in a supported series, please file a new bug.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: Triaged → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.