From: Mike Eldridge <diz@cafes.net>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 2.4.20-rc2-xfs lockups
Date: Thu, 21 Nov 2002 18:53:55 -0600 [thread overview]
Message-ID: <20021121185355.A4376@ornery.cafes.net> (raw)
In-Reply-To: <1037925505.9160.13.camel@irongate.swansea.linux.org.uk>; from alan@lxorguk.ukuu.org.uk on Fri, Nov 22, 2002 at 12:38:25AM +0000
On Fri, Nov 22, 2002 at 12:38:25AM +0000, Alan Cox wrote:
> On Thu, 2002-11-21 at 23:26, Mike Eldridge wrote:
> > On Thu, Nov 21, 2002 at 03:31:22PM -0600, Mike Eldridge wrote:
> > > i recently replaced a pII-350 with a pair of pIII-500s in a tyan
> > > S1836-DLUAN-GX board (440GX dual slot 1). i'm now getting loads of NMI
> > > interrupts for unknown reasons (reasons 2c and 3c).
> >
> > after more googling, i've found several pieces of information that seem
> > to suggest interrupt routing on 440GX-based motherboards is busted.
> >
> > can anyone confirm this? will booting with 'noapic' fix this problem?
> > am i doomed to run a UP kernel?
>
> It varies. Unfortunately Intel won't tell us how to sort this mess out.
hrm :/
ironically, i've got another box here (440GX dual pIII-500) running
linux-2.2.20 with apic enabled that doesn't have this problem.
interestingly, the NMI line from /proc/interrupts only lists counts for
CPU0, not for CPU1. and it's sitting comfortably at 0.
running with 'noapic' on the troublesome machine still produces NMIs and
random hangs.
-mike
------------------------------------------------------------------------
/~\ the ascii "rich gifts wax poor when givers prove
\ / ribbon campaign unkind"
X against html -- ophelia (hamlet; act III, scene 1)
/ \ email!
prev parent reply other threads:[~2002-11-22 0:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-21 21:31 Mike Eldridge
2002-11-21 23:26 ` Mike Eldridge
2002-11-22 0:38 ` Alan Cox
2002-11-22 0:53 ` Mike Eldridge [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=20021121185355.A4376@ornery.cafes.net \
--to=diz@cafes.net \
--cc=alan@lxorguk.ukuu.org.uk \
--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
all inboxes | Powered by JetHome®