From: Chris Wedgwood <cw@f00f.org>
To: Dominik Kubla <dominik@kubla.de>
Cc: Larry McVoy <lm@work.bitmover.com>, linux-kernel@vger.kernel.org
Subject: Re: ECC error in 2.5.64 + some patches
Date: Thu, 27 Mar 2003 09:25:59 -0800 [thread overview]
Message-ID: <20030327172559.GA26700@f00f.org> (raw)
In-Reply-To: <200303271819.41971.dominik@kubla.de>
On Thu, Mar 27, 2003 at 06:19:41PM +0100, Dominik Kubla wrote:
> Well the internal busses and buffers of modern CPU's and in many
> cases also the on-die caches have ECC logic.
his email said "DIMMs"
> And if i should hazard a guess: "Restart IP valid" => Restarted
> Instruction Pre-Fetch resulted in a valid state of the pre-fetch
> queue.
could be ... i've not checked the AMD docs
> In Larry's case i'd remove the cpu cooler, clean everything and
> reassemble, since i would assume that there is a hot-spot on the
> die.
or simply remove the side of the case or increase air-conditioning and
see if that goes away or becomes less apparent, IME if you get these
sporadically rather than often it's 'just' overheating...
--cw
next prev parent reply other threads:[~2003-03-27 17:15 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-24 21:28 3ware driver errors Steven Pritchard
2003-03-25 1:01 ` Jeff V. Merkey
2003-03-24 23:44 ` Larry McVoy
2003-03-25 0:07 ` Mark Hahn
2003-03-25 1:25 ` Jeff V. Merkey
2003-03-25 3:12 ` Steven Pritchard
2003-03-25 3:11 ` Kevin P. Fleming
2003-03-25 15:25 ` Ezra Nugroho
2003-03-25 15:26 ` Roy Sigurd Karlsbakk
2003-03-25 16:26 ` Ezra Nugroho
2003-03-27 16:02 ` ECC error in 2.5.64 + some patches Larry McVoy
2003-03-27 16:17 ` Tim Schmielau
2003-03-27 16:27 ` Larry McVoy
2003-03-27 16:39 ` Tim Schmielau
2003-03-27 16:22 ` Randy.Dunlap
2003-03-27 16:31 ` Larry McVoy
2003-03-28 0:10 ` Dave Jones
2003-03-27 16:31 ` Dave Jones
2003-03-27 17:00 ` Chris Wedgwood
2003-03-27 17:19 ` Dominik Kubla
2003-03-27 17:25 ` Chris Wedgwood [this message]
2003-04-15 4:34 ` Bill Davidsen
2003-04-15 13:24 ` Larry McVoy
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=20030327172559.GA26700@f00f.org \
--to=cw@f00f.org \
--cc=dominik@kubla.de \
--cc=linux-kernel@vger.kernel.org \
--cc=lm@work.bitmover.com \
/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