From: R.E.Wolff@BitWizard.nl (Rogier Wolff)
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: APIC errors w/ 2.4.0-test11-pre2
Date: Fri, 10 Nov 2000 23:25:57 +0100 (MET) [thread overview]
Message-ID: <200011102225.XAA04339@cave.bitwizard.nl> (raw)
In-Reply-To: <8uhpuj$1uf$1@cesium.transmeta.com> from "H. Peter Anvin" at "Nov 10, 2000 01:39:31 pm"
H. Peter Anvin wrote:
> Followup to: <Pine.LNX.4.21.0011101523170.14596-100000@bochum.redhat.de>
> By author: Bernhard Rosenkraenzer <bero@redhat.de>
> In newsgroup: linux.dev.kernel
> >
> > Hi,
> > after booting a 2.4.0 (any testx-release I've tried so far, including
> > test11-pre2) on a Dual-Pentium III box, the system works ok, but the
> > console gets filled with
> >
> > APIC error on CPU0: 08(08)
> >
> > every couple of seconds, occasionally some lines in between say
> >
> > APIC error on CPU0: 08(02)
> >
> > and
> >
> > APIC error on CPU0: 02(08)
> >
> I have seen the same problem on the same motherboard. It appears to
> be a motherboard bug that 2.4 exposes and 2.2 doesn't.
This PRINT was added in 2.4.
You're seeing noise on the apic lines. The APICs notice, but every now
and then you may see a lockup due to this. (i.e. if the corruption
does not trigger a parity error, because two bits flipped!)
Roger.
--
** R.E.Wolff@BitWizard.nl ** http://www.BitWizard.nl/ ** +31-15-2137555 **
*-- BitWizard writes Linux device drivers for any device you may have! --*
* Common sense is the collection of *
****** prejudices acquired by age eighteen. -- Albert Einstein ********
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-11-10 22:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-10 14:31 APIC errors w/ 2.4.0-test11-pre2 Bernhard Rosenkraenzer
2000-11-10 21:39 ` H. Peter Anvin
2000-11-10 22:25 ` Rogier Wolff [this message]
2000-11-10 23:37 ` H. Peter Anvin
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=200011102225.XAA04339@cave.bitwizard.nl \
--to=r.e.wolff@bitwizard.nl \
--cc=hpa@zytor.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox