public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: APIC errors w/ 2.4.0-test11-pre2
Date: 10 Nov 2000 13:39:31 -0800	[thread overview]
Message-ID: <8uhpuj$1uf$1@cesium.transmeta.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0011101523170.14596-100000@bochum.redhat.de>

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)
> 
> This doesn't happen with 2.2.x, but I've seen "unexpected IRQ vector 208
> on CPU0" in 2.2.18 occasionally (nowhere near as often, maybe once a
> month).
> 
> This is an ASUS P2-D board (Intel 440BX chipset), 2 Pentium III-700
> processors.
> 
> The same kernel works perfectly on a similar (but slower) system, Gigabyte
> P2B-D board (Intel 440BX chipset), 2 Pentium III-450 processors.
> 

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.

	-hpa


-- 
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt
-
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/

  reply	other threads:[~2000-11-10 21:40 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 [this message]
2000-11-10 22:25   ` Rogier Wolff
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='8uhpuj$1uf$1@cesium.transmeta.com' \
    --to=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