public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@transmeta.com>
To: Rogier Wolff <R.E.Wolff@BitWizard.nl>
Cc: "H. Peter Anvin" <hpa@zytor.com>, linux-kernel@vger.kernel.org
Subject: Re: APIC errors w/ 2.4.0-test11-pre2
Date: Fri, 10 Nov 2000 15:37:31 -0800	[thread overview]
Message-ID: <3A0C86BB.4C87A630@transmeta.com> (raw)
In-Reply-To: <200011102225.XAA04339@cave.bitwizard.nl>

Rogier Wolff wrote:
> 
> > I have seen the same problem on the same motherboard.  It appears to
> > be a motherboard bug that 2.4 exposes and 2.2 doesn't.
> 
> This PRINT was added in 2.4.
> 
> You're seeing noise on the apic lines. The APICs notice, but every now
> and then you may see a lockup due to this. (i.e. if the corruption
> does not trigger a parity error, because two bits flipped!)
> 

What I was seeing, though, was that 2.4 would lock up with an NMI deadman
after a few days.  2.2 never did.  Even on other hardware I see very high
NMI rates, but no lockups, using 2.4.

	-hpa

-- 
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

      reply	other threads:[~2000-11-10 23:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-10 14:31 APIC errors w/ 2.4.0-test11-pre2 Bernhard Rosenkraenzer
2000-11-10 21:39 ` H. Peter Anvin
2000-11-10 22:25   ` Rogier Wolff
2000-11-10 23:37     ` H. Peter Anvin [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=3A0C86BB.4C87A630@transmeta.com \
    --to=hpa@transmeta.com \
    --cc=R.E.Wolff@BitWizard.nl \
    --cc=hpa@zytor.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