From: Chris Rankin <rankincj@yahoo.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: APIC error on SMP machine
Date: Tue, 30 Sep 2003 22:42:19 +0100 [thread overview]
Message-ID: <3F79F8BB.2080905@yahoo.com> (raw)
Linux-2.4.22-SMP, 1 GB RAM, devfs, gcc-3.2.3.
Hi,
Today, my dual PIII (Coppermine) refused to boot, and wrote a large number of
these messages to the serial console instead:
APIC error on CPU1: 04(04)
APIC error on CPU1: 04(04)
APIC error on CPU1: 04(04)
APIC error on CPU1: 04(04)
APIC error on CPU1: 04(04)
APIC error on CPU1: 04(04)
APIC error on CPU1: 04(04)
APIC error on CPU1: 04(04)
APIC error on CPU1: 04(04)
APIC error on CPU1: 04(04)
APIC error on CPU1: 04(04)
APIC error on CPU1: 04(04)
APIC error on CPU1: 04(04)
APIC error on CPU1: 04(04)
APIC error on CPU1: 04(04)
Can anyone tell me what these might mean, please? The kernel source implies that
it's a "Send accept error", but this doesn't help me in an "Ah, I can fix that!"
sense.
Does this APIC error just mean that the CPU is unhappy in this slot, and is
refusing to listen to the motherboard? Or is the motherboard refusing to listen
to the CPU?
Background:
This machine has been misbehaving for a while. I thought I had worked around the
problem by underclocking the FSB from 133 MHz to 100 MHz, but that now looks
like it was just a "reprieve". I have tried running "nosmp", "pci=noacpi" and
"noapic pci=noacpi" without success, and have resorted to yanking the CPU out of
this slot entirely. (I suspect that the CPU is fine, however.) I have also
restored the FSB to 133 MHz, so I am currently running the SMP kernel on a
single 933 MHz PIII.
Cheers,
Chris
next reply other threads:[~2003-09-30 21:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-30 21:42 Chris Rankin [this message]
2003-10-01 1:52 ` APIC error on SMP machine James Cleverdon
2003-10-01 10:14 ` Chris Rankin
2003-10-01 7:47 ` Rogier Wolff
-- strict thread matches above, loose matches on Subject: below --
2003-10-01 13:08 Matt_Domsch
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=3F79F8BB.2080905@yahoo.com \
--to=rankincj@yahoo.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