APIC error on CPU0

[mp]

On Ubuntu 8.04 - all updates done.

There is a long string of error messages from dmesg:

[12064.388918] APIC error on CPU0: 40(40)
[12066.030095] APIC error on CPU0: 40(40)
[12074.609324] APIC error on CPU0: 40(40)
[12094.133049] APIC error on CPU0: 40(40)
[12096.449042] APIC error on CPU0: 40(40)
[12157.639234] APIC error on CPU0: 40(40)
[12171.393141] APIC error on CPU0: 40(40)
[12197.533751] APIC error on CPU0: 40(40)
[12213.303303] APIC error on CPU0: 40(40)
[12233.921385] APIC error on CPU0: 40(40)
[12249.413151] APIC error on CPU0: 40(40)
[12252.667913] APIC error on CPU0: 40(40)
[12268.665927] APIC error on CPU0: 40(40)
[12315.343925] APIC error on CPU0: 40(40)
[12316.172564] APIC error on CPU0: 40(40)
[12324.991946] APIC error on CPU0: 40(40)
[12448.403363] APIC error on CPU0: 40(40)
[12451.961571] APIC error on CPU0: 40(40)
[12748.909036] APIC error on CPU0: 40(40)
[12846.123709] APIC error on CPU0: 40(40)
[12858.469938] APIC error on CPU0: 40(40)
[12894.194710] APIC error on CPU0: 40(40)
[12917.650023] APIC error on CPU0: 40(40)
[13029.016979] APIC error on CPU0: 40(40)
[13051.694018] APIC error on CPU0: 40(40)
[13099.459982] APIC error on CPU0: 40(40)
[13124.813359] APIC error on CPU0: 40(40)
[13139.902114] APIC error on CPU0: 40(40)
[13172.619207] APIC error on CPU0: 40(40)
[13199.843456] APIC error on CPU0: 40(40)
[13822.003423] APIC error on CPU0: 40(40)
[13872.787542] APIC error on CPU0: 40(40)
[13879.469412] APIC error on CPU0: 40(40)
[14013.769187] APIC error on CPU0: 40(40)
[14163.670562] APIC error on CPU0: 40(40)
[14171.959998] APIC error on CPU0: 40(40)
[14266.825467] APIC error on CPU0: 40(40)
[14268.474523] APIC error on CPU0: 40(40)
[14600.462445] APIC error on CPU0: 40(40)
[14609.700670] APIC error on CPU0: 40(40)
[15179.859913] APIC error on CPU0: 40(40)
[15185.163747] APIC error on CPU0: 40(40)
[15217.870046] APIC error on CPU0: 40(40)
[15219.006048] APIC error on CPU0: 40(40)

It seems that this bug was opened and solved in 2006 - but it is back to haunt us.

[Richard Seguin (sectech)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it, because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" [WWW] http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at [WWW] http://wiki.ubuntu.com/DebuggingProcedures

At a minimum, we need:
1. the specific steps or actions you took that caused you to encounter the problem,
2. the behavior you expected, and
3. the behavior you actually encountered (in as much detail as possible).
Thanks!

[mp (m-p)]

I understand that,

but I have no idea what causes this,

and what I expect is that dmesg includes no error messages

all I did to encounter to issue is to type:

dmesg

and that includes many such error messages

Richard Seguin wrote:
> Thank you for taking the time to report this bug and helping to make
> Ubuntu better. Unfortunately we can't fix it, because your description
> didn't include enough information. You may find it helpful to read "How
> to report bugs effectively" [WWW]
> http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful
> if you would then provide a more complete description of the problem.
>
> We have instructions on debugging some types of problems at [WWW]
> http://wiki.ubuntu.com/DebuggingProcedures
>
> At a minimum, we need:
> 1. the specific steps or actions you took that caused you to encounter the problem,
> 2. the behavior you expected, and
> 3. the behavior you actually encountered (in as much detail as possible).
> Thanks!
>
> ** Changed in: ubuntu
> Status: New => Incomplete
>

[Richard Seguin (sectech)]

It's hard to troubleshoot strange errors I understand :)

My questions are basically to has as much information documented so the developers can fix the bug...

I have a few more questions...

1) Does this happen on a clean boot? or on a resume after a suspend
2) What kind of hardware do you have?

I did a little research on this and booting with the "noapic" option might be a work around for you... It doesn't mean that it isn't a bug though.

[Richard Seguin (sectech)]

It appears that this might be a duplicate of bug #66900... can you confirm?

[mp (m-p)]

It looks like it is the same bug -

the error message comes soon after normal boot (I never use resume or hibernation or any such thing)

this is the hardware:

~# lshw

    description: Notebook
    product: Satellite Pro A120
    vendor: TOSHIBA
    version: PSAC0E-035014EN
    serial:
    width: 32 bits
    capabilities: smbios-2.4 dmi-2.4
    configuration: administrator_password=disabled boot=normal chassis=notebook frontpanel_password=disabled keyboard_password=disabled power-on_password=disabled uuid=FA6F1980-7329-11DB-8030-B05996077591
  *-core
       description: Motherboard
       product: Portable PC
       vendor: TOSHIBA
       physical id: 0
       version: Version A0
       serial: $$C06YB1HR
     *-firmware
          description: BIOS
          vendor: TOSHIBA
          physical id: 0
          version: Version 1.50 (08/24/2006)
          size: 128KiB
          capacity: 960KiB
          capabilities: isa pci pcmcia pnp upgrade shadowing vesa cdboot bootselect edd int13floppytoshiba int13floppy720 int5printscreen int9keyboard int14serial int17printer acpi usb biosbootspecification netboot
     *-cpu
          description: CPU
          product: Intel(R) Celeron(R) M CPU 430 @ 1.73GHz
          vendor: Intel Corp.
          physical id: 4
          bus info: cpu@0
          version: 6.14.8
          serial: 0000-06E8-0000-0000-0000-0000
          slot: uFC-PGA Socket
          size: 1730MHz
          capacity: 1730MHz
          width: 32 bits
          clock: 133MHz
          capabilities: fpu fpu_exception wp vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat clflush dts acpi mmx fxsr sse sse2 ss tm pbe constant_tsc up arch_perfmon bts pni monitor tm2 xtpr
        *-cache:0
             description: L1 cache
             physical id: 12
             slot: CPU Internal
             size: 64KiB
             capacity: 64KiB
             clock: 1GHz (1.0ns)
             capabilities: internal write-back unified
        *-cache:1
             description: L2 cache
             physical id: 13
             slot: CPU Internal
             size: 1MiB
             capacity: 1MiB
             clock: 1GHz (1.0ns)
             capabilities: internal write-back unified
     *-memory
          description: System Memory
          physical id: 81
          slot: System board or motherboard
          size: 1280MiB
          capacity: 2GiB
        *-bank:0
             description: SODIMM Synchronous
             product: M4 70T3354CZ3-CD5
             vendor: CE00
             physical id: 0
             serial: 0800A84B
             slot: DIMM 0
             size: 256MiB
             width: 64 bits
        *-bank:1
             description: SODIMM Synchronous
             product: 8HTF12864HDY-53EE1
             vendor: 2C00
             physical id: 1
             serial: E00C6BC8
             slot: DIMM 1
             size: 1GiB
             width: 64 bits
     *-pci
          description: Host bridge
          product: ATI Technologies Inc
          vendor: ATI Technologies Inc
          physical id: 100
          bus info: pci@0000:00:00.0
          version: 01
          width: 32 bits
        ...

[Richard Seguin (sectech)]

Okay... I marked this as a duplicate of bug #66900... It might help to see what they suggested on that bug