From: Jan Dittmer <jdittmer@ppp0.net>
To: gene.heskett@verizon.net
Cc: linux-kernel@vger.kernel.org, Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: Linux 2.6.10-ac1
Date: Fri, 31 Dec 2004 13:38:50 +0100 [thread overview]
Message-ID: <41D5485A.4060709@ppp0.net> (raw)
In-Reply-To: <200412310705.52976.gene.heskett@verizon.net>
Gene Heskett wrote:
> If I feed it the lines with the numbers it reports something about an
> invalid IP on restart.
>
> [root@coyote root]# parsemce -e Bank 2: d40040000000017a -b Bank 2: -s
> d40040000000017a
> Status: (ba) Error IP valid
> Restart IP invalid.
>
> The exact same output is obtained from the Bank 1 message & numbers
> too.
Try
$ ./parsemce -e 0xba -b 2 -s d40040000000017a -a 0
Status: (ba) Error IP valid
Restart IP invalid.
parsebank(2): d40040000000017a @ 0
External tag parity error
Correctable ECC error
Address in addr register valid
Error enabled in control register
Error overflow
Memory heirarchy error
Request: Generic error
Transaction type : Generic
Memory/IO : I/O
See [1] for a possible explanation. I hope the link works. It's a message
from DaveJ about the same error:
"Looks like the L2 cache ECC checking spotted something going wrong,
and fixed it up. This can happen in cases where there is inadequate
cooling, power, or overclocking (or in rare circumstances, flaky CPUs)"
Jan
[1] http://groups-beta.google.com/group/linux.kernel/browse_thread/thread/bbf1d32da11eb369/8b2300b83ac0ab9e?q=%22Restart+IP+invalid%22&_done=%2Fgroups%3Fq%3D%22Restart+IP+invalid%22%26hl%3Den%26lr%3D%26client%3Dfirefox%26rls%3Dorg.mozilla:en-US:unofficial%26sa%3DN%26tab%3Dwg%26&_doneTitle=Back+to+Search&&d#8b2300b83ac0ab9e
next prev parent reply other threads:[~2004-12-31 12:38 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-26 23:31 Linux 2.6.10-ac1 Alan Cox
2004-12-27 0:57 ` Bartlomiej Zolnierkiewicz
2004-12-27 1:25 ` Andreas Steinmetz
2004-12-27 1:40 ` Bartlomiej Zolnierkiewicz
2004-12-27 14:28 ` Alan Cox
2004-12-27 15:46 ` Bartlomiej Zolnierkiewicz
2004-12-27 14:45 ` Ross Biro
2004-12-27 15:38 ` Bartlomiej Zolnierkiewicz
2004-12-27 15:49 ` Andreas Steinmetz
2004-12-27 15:54 ` Bartlomiej Zolnierkiewicz
2004-12-27 16:02 ` Andreas Steinmetz
2004-12-27 16:54 ` Alan Cox
2004-12-27 14:36 ` Rafael J. Wysocki
2004-12-27 14:57 ` Andreas Steinmetz
2004-12-27 14:33 ` Alan Cox
2004-12-27 20:31 ` Rogério Brito
2004-12-27 20:43 ` Michal Schmidt
2004-12-28 0:45 ` Alan Cox
2004-12-28 2:44 ` Rogério Brito
2004-12-30 4:41 ` Gene Heskett
2004-12-30 5:05 ` Gene Heskett
2004-12-30 23:38 ` Alan Cox
2004-12-31 1:06 ` Gene Heskett
2004-12-31 9:57 ` Jan Dittmer
2004-12-31 12:05 ` Gene Heskett
2004-12-31 12:38 ` Jan Dittmer [this message]
2004-12-31 13:18 ` Gene Heskett
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=41D5485A.4060709@ppp0.net \
--to=jdittmer@ppp0.net \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=gene.heskett@verizon.net \
--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