From: Gene Heskett <gene.heskett@verizon.net>
To: linux-kernel@vger.kernel.org
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: Linux 2.6.10-ac1
Date: Thu, 30 Dec 2004 20:06:19 -0500 [thread overview]
Message-ID: <200412302006.19872.gene.heskett@verizon.net> (raw)
In-Reply-To: <1104430176.2446.3.camel@localhost.localdomain>
On Thursday 30 December 2004 18:38, Alan Cox wrote:
Thanks for the reply Alan, I appreciate it.
>On Iau, 2004-12-30 at 05:05, Gene Heskett wrote:
>> some sort of an error message that looks like it may be memory
>> related. There's a pair of half giggers in here, running at 333
>> fsb, but they are supposedly rated for a 400 mhz fsb. Thats
>> presumably because I have turned on the MCE stuffs.
>
>MCE's generally come from the processor. To decode it you need to
> know what CPU and then get the manuals out and decode the bits.
>
>> Dec 29 23:44:09 coyote kernel: MCE: The hardware reports a non
>> fatal, correctable incident occurred on CPU 0. Dec 29 23:44:09
>> coyote kernel: Bank 2: d40040000000017a
>>
>> And I've not seen that before. Does it have a simple and correct
>> answer?
>
>Its unhappy about something, but whatever is causing it isn't fatal.
>Previously its been unhappy but not telling you ..
Thats what I thought too Alan, after I'd connected the dots, so I
turned the nonfatal exceptions off. I'll give memtest86 another
chance to break it sometime next week. This is NOT ecc memory that I
know of although I paid nearly $80 per half gig when I bought it last
spring. Theres a gig of it in here, and only two addresses were
being reported, one in each bank. If mapped directly, are those
addresses even in that gig of ram? Thats too big a hex number for my
calculator. Or is there a way to use the dmesg data to define that?
Dumb question, could this memory be on the video card? Its an ATI
9200SE 128 meg card, your basic $85 commodity card there days.
--
Cheers, Gene
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
99.31% setiathome rank, not too shabby for a WV hillbilly
Yahoo.com attorneys please note, additions to this message
by Gene Heskett are:
Copyright 2004 by Maurice Eugene Heskett, all rights reserved.
next prev parent reply other threads:[~2004-12-31 1:06 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-26 23:31 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 [this message]
2004-12-31 9:57 ` Jan Dittmer
2004-12-31 12:05 ` Gene Heskett
2004-12-31 12:38 ` Jan Dittmer
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=200412302006.19872.gene.heskett@verizon.net \
--to=gene.heskett@verizon.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®