From: William Lee Irwin III <wli@holomorphy.com>
To: Dave Hansen <haveblue@us.ibm.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fix kirq code for clustered mode
Date: Thu, 20 Feb 2003 04:29:34 -0800 [thread overview]
Message-ID: <20030220122934.GA29983@holomorphy.com> (raw)
In-Reply-To: <20030220121917.GZ29983@holomorphy.com>
On Tue, Feb 18, 2003 at 09:51:28AM -0800, Dave Hansen wrote:
>> The new kirq code breaks clustered apic mode. This 2-liner fixes it.
>> It should compile down to the same thing, unless you're using a
>> clustered apic sub-arch.
On Thu, Feb 20, 2003 at 04:19:17AM -0800, William Lee Irwin III wrote:
> This isn't quite enough:
Also, even with your patch, I get:
Uhhuh. NMI received for unknown reason 25 on CPU 3.
Uhhuh. NMI received for unknown reason 35 on CPU 2.
Dazed and confused, but trying to continue
...
Hmm... something is going seriously wrong here. I suspect someone
is clobbering my RTE's even though no_irq_balance is #defined to 1.
Or, worse yet, NMI interrupt gate boogie is going seriously wrong.
-- wli
prev parent reply other threads:[~2003-02-20 12:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-18 17:51 [PATCH] fix kirq code for clustered mode Dave Hansen
2003-02-20 12:19 ` William Lee Irwin III
2003-02-20 12:29 ` William Lee Irwin III [this message]
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=20030220122934.GA29983@holomorphy.com \
--to=wli@holomorphy.com \
--cc=haveblue@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