From: James Cleverdon <jamesclv@us.ibm.com>
To: Peter Monta <pmonta@pmonta.com>, linux-kernel@vger.kernel.org
Subject: Re: APIC errors, Asus A7M266-D (760MPX chipset)
Date: Mon, 21 Jan 2002 08:37:09 -0800 [thread overview]
Message-ID: <200201211637.g0LGbCq07602@butler1.beaverton.ibm.com> (raw)
In-Reply-To: <20020121104204.971231C5@www.pmonta.com>
In-Reply-To: <20020121104204.971231C5@www.pmonta.com>
On Monday 21 January 2002 02:42 am, Peter Monta wrote:
> I'm getting a storm of APIC errors with an Asus A7M266-D motherboard
> at the beginning of boot (and no further boot progress is made).
> The console message is "APIC error on CPU0: 04(04)". A single
> Athlon MP 1200 is installed; the kernel is compiled with SMP=n
> but both "local APIC" and "use IO-APIC" are enabled. I'm using
> 2.5.2pre10.
ESR == 04 means Send Accept Error. The P6 manual says:
Set when the local APIC detects that a message it sent was not
accepted by any APIC on the bus.
Now, I wonder why it was sending anything at all. Maybe that CPU was the one
that does the PIC emulation and has one of the LVT{0,1} entries set to ExtInt.
BTW, be aware that Intel has changed the way the ESR works. The P6 manual
says that software must do two back-to-back writes to clear ESR bits. The
most recent P4s say that a read clears bits and writes are ignored, save for
the requirement of a write before the read to get the ESR up to date. AFAIK,
Intel's Linux gang hasn't posted any patches to fix smp_error_interrupt() for
P4s. I've been meaning to do that myself....
> Oddly, booting this same kernel with the "noapic" option results in
> the same problem, but recompiling with all APIC options disabled
> gives a successful boot.
Sounds like the APIC was up to something anyway....
> While running in this legacy interrupt mode there seem to be a lot
> of ERR: interrupts in /proc/interrupts, in fact about five times as
> many as "real" ones listed above. Does this affect performance? How
> much is interrupt latency increased when the APIC bus must reissue
> commands like this (if I understand the documentation correctly)?
As you would expect performance takes a nosedive from the printks, if nothing
else, and keeping the APIC bus busy with retransmits increases latency. They
use a round robin fairness algorithm so no interrupt source gets starved, but
because the APIC bus is a serial bus (relatively slow) waiting for a turn can
take a while. How long? Beats me. The HW guys are no longer leasing an
APIC bus analyzer pod, so your guess is as good as mine.
> Cheers,
> Peter Monta
--
James Cleverdon, IBM xSeries Platform (NUMA), Beaverton
jamesclv@us.ibm.com | cleverdj@us.ibm.com
next prev parent reply other threads:[~2002-01-21 16:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-21 10:42 Peter Monta
2002-01-21 16:37 ` James Cleverdon [this message]
2002-01-21 16:57 ` Maciej W. Rozycki
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=200201211637.g0LGbCq07602@butler1.beaverton.ibm.com \
--to=jamesclv@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pmonta@pmonta.com \
/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
all inboxes | Powered by JetHome®