From: "Chris Rankin" <rankincj@yahoo.com>
To: jamesclv@us.ibm.com, linux-kernel <linux-kernel@vger.kernel.org>
Cc: R.E.Wolff@BitWizard.nl
Subject: Re: APIC error on SMP machine
Date: Wed, 1 Oct 2003 11:14:45 +0100 (BST) [thread overview]
Message-ID: <20031001101445.62739.qmail@web40602.mail.yahoo.com> (raw)
In-Reply-To: <200309301852.47835.jamesclv@us.ibm.com>
--- James Cleverdon <jamesclv@us.ibm.com> wrote:
> An APIC send accept error means that when trying to
> send an interrupt, it was not accepted by the
target.
> In this case, the target is a CPU, either your other
> CPU or the same one (a CPU can send itself an
> interrupt).
...
> 3) Maybe the other CPU is broken and physically
> cannot accept the interrupt.
Given the background, the most likely cause would seem
to be bad a CPU/motherboard connection. I have
realised that the APIC error is for CPU1, but I have
actually removed CPU0. And a bad CPU0 would explain
why "nosmp" didn't work either.
It's a pity that "nosmp" doesn't (logially cannot?)
take a "boot CPU number" as a parameter.
> Do any previous kernels boot?
Not any more. Everything started to hit the fan at the
beginning of August, and I thought that I had
"patched" things by underclocking the FSB. However,
that only seems to have delayed the inevitable. CPU
slot 2 on my motherboard just seems not to work any
more. I have no idea why - it's not like I can see a
lot of dust and dirt in there.
Oh well, I hear that Dell are selling dual 2.6 GHz
Xeons with RedHat preinstalled nowadays. (These should
have "hyperthreading support", right ;-) ?)
Cheers,
Chris
________________________________________________________________________
Want to chat instantly with your online friends? Get the FREE Yahoo!
Messenger http://mail.messenger.yahoo.co.uk
next prev parent reply other threads:[~2003-10-01 10:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-30 21:42 Chris Rankin
2003-10-01 1:52 ` James Cleverdon
2003-10-01 10:14 ` Chris Rankin [this message]
2003-10-01 7:47 ` Rogier Wolff
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=20031001101445.62739.qmail@web40602.mail.yahoo.com \
--to=rankincj@yahoo.com \
--cc=R.E.Wolff@BitWizard.nl \
--cc=jamesclv@us.ibm.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
Powered by JetHome