From: "Martin J. Bligh" <Martin.Bligh@us.ibm.com>
To: Mark Hahn <hahn@physics.mcmaster.ca>,
Adam K Kirchhoff <adamk@voicenet.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: SMP & APIC problem.
Date: Mon, 11 Mar 2002 16:36:57 -0800 [thread overview]
Message-ID: <132630000.1015893417@flay> (raw)
In-Reply-To: <Pine.LNX.4.33.0203111920430.1437-100000@coffee.psychology.mcmaster.ca>
In-Reply-To: <Pine.LNX.4.33.0203111920430.1437-100000@coffee.psychology.mcmaster.ca>
>> My second question: Is there any chance of getting this working with
>> APIC, if not in 2.4.* maybe in a future release?
>
> given that it's a hardware problem, no. but it *would* be cool
> if the kernel noticed repeated APIC warnings and just turned
> off apic use (as if you had booted with noapic). I'm guessing
> this would be ugly, since APIC setup is probably discarded after boot...
There were some patches floating around to do exactly this (don't
remember where, sorry ;-) )
There's also an esr_disable flag variable I put in a while back
when doing bringup of NUMA-Q to smack the ESR into submission.
You might want to try tweaking that on in smp.h. It's not like we
actually do anything with the errors anyway. (all assuming my
mind isn't faulty, and this is actually the same thing). The read /
write protocol for ESR is really .... wierd, and it seems to need
smacking multiple times to accept a write.
M.
next prev parent reply other threads:[~2002-03-12 0:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-11 23:31 SMP & APIC problem Adam K Kirchhoff
2002-03-12 0:22 ` Mark Hahn
2002-03-12 0:36 ` Martin J. Bligh [this message]
2002-03-12 13:58 ` Zwane Mwaikambo
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=132630000.1015893417@flay \
--to=martin.bligh@us.ibm.com \
--cc=adamk@voicenet.com \
--cc=hahn@physics.mcmaster.ca \
--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