From: R.E.Wolff@BitWizard.nl (Rogier Wolff)
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: test11-pre5, Athlon, and Machine Check Architecture
Date: Wed, 15 Nov 2000 22:14:44 +0100 (MET) [thread overview]
Message-ID: <200011152114.WAA06084@cave.bitwizard.nl> (raw)
In-Reply-To: <8uuqij$ejs$1@cesium.transmeta.com> from "H. Peter Anvin" at "Nov 15, 2000 12:09:55 pm"
H. Peter Anvin wrote:
> crash; I don't expect anyone to actually see an #MF exception in real
> life. I'm trying to get confirmation from AMD that the code should
> be correct even for Athlon.
Peter,
Would it be an idea to invite people to lower the voltage on their
CPUs a bit, to try and trigger #MF's?
(I started thinking about slowly overclocking the CPUs, to try and
trigger them, but that's not neccesary. At lower voltages, you'll also
get errors, but shouldn't risk smoking your CPU.... )
Roger.
--
** R.E.Wolff@BitWizard.nl ** http://www.BitWizard.nl/ ** +31-15-2137555 **
*-- BitWizard writes Linux device drivers for any device you may have! --*
* Common sense is the collection of *
****** prejudices acquired by age eighteen. -- Albert Einstein ********
-
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/
next prev parent reply other threads:[~2000-11-15 21:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-15 20:09 test11-pre5, Athlon, and Machine Check Architecture H. Peter Anvin
2000-11-15 21:14 ` Rogier Wolff [this message]
2000-11-15 21:32 ` H. Peter Anvin
-- strict thread matches above, loose matches on Subject: below --
2000-11-15 21:12 davej
2000-11-15 21:34 ` H. Peter Anvin
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=200011152114.WAA06084@cave.bitwizard.nl \
--to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.