From: "Herbert Pötzl" <herbert@13thfloor.at>
To: Shawn <core@enodev.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: APIC error on CPU0: 02(02)
Date: Wed, 30 Jul 2003 10:12:57 +0200 [thread overview]
Message-ID: <20030730081257.GC2593@www.13thfloor.at> (raw)
In-Reply-To: <1059528202.4820.12.camel@localhost>
On Tue, Jul 29, 2003 at 08:23:22PM -0500, Shawn wrote:
> I just bought a shiny new Athlon 2400+ and popped it in my biostar M7VIB
> with an up to date bios.
>
> I'm running 2.6.0-test1-mm2, and I get tons of "APIC error on CPU0:
> 02(02)" messages. Can someone tell me what is going on?
in the ol' BP6 times (dual Celeron) APIC errors
where reported (by certain 2.4.x kernels, previous
versions simply ignored them) when an error occured
while the CPUs where communicating ...
as far as I understood, the communication between
APIC and CPU is checksummed (a very simple checksum,
like a parity) and if this checksum is invalid, the
action is restarted, so this okay, because an error
was avoided, but because the checksum is so simple
(IIRC only two bits), chances are good that some
faulty communication will go undetected ...
please, I'm no expert on Athlon APIC or such stuff,
so this could be total bullshit, but maybe some
APIC expert will comment on that ;)
best,
Herbert
> Info about my machine's hardware:
> http://www.enodev.com/info.html
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2003-07-30 8:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-30 1:23 APIC error on CPU0: 02(02) Shawn
2003-07-30 1:50 ` sandalle
2003-07-30 8:12 ` Herbert Pötzl [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-07-30 11:19 Mikael Pettersson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030730081257.GC2593@www.13thfloor.at \
--to=herbert@13thfloor.at \
--cc=core@enodev.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.