From: Andy Stewart <andystewart@comcast.net>
To: Doug Thompson <norsk5@yahoo.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Machine check 2.6.13.3 dual opteron
Date: Sat, 24 Dec 2005 23:36:25 -0500 [thread overview]
Message-ID: <43AE21C9.4030900@comcast.net> (raw)
In-Reply-To: <20051225041912.70959.qmail@web50108.mail.yahoo.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Doug Thompson wrote:
> I got an ASUS A8V-E with a 3500+ CPU, 2 GB of ram. I have had not problem with it.
>
> I run Bluesmoke on it (bluesmoke.sourceforge.net), which is renamed EDAC in a submission for
> inclusion in the kernel (hopefully 2.6.16). Bluesmoke, scans the the K8's Memory controller
> looking for Correctable Errors that occur. The idea is that detection correctable errors and
> replacing memory can reduce sudden uncorrectable errors.
>
> But your problem seems generated by the motherboard, no memory. SOMETHING is not quite right.
>
> doug t
HI Doug,
I'll be sure to take a look at Bluesmoke / EDAC. Thanks!
Now, I'd best go to bed or Santa won't come to my house. :-)
Andy
- --
Andy Stewart, Founder
Worcester Linux Users' Group
Worcester, MA, USA
http://www.wlug.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFDriHJHl0iXDssISsRAnqGAJ4rUEd7rF4uesucMhQaxTlW4byx3ACfRYV3
EJeZ3kXez6cRF1hxQJVh+NE=
=h52c
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2005-12-25 4:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-24 17:32 Machine check 2.6.13.3 dual opteron Andy Stewart
2005-12-24 19:46 ` Doug Thompson
2005-12-25 4:06 ` Andy Stewart
2005-12-25 4:19 ` Doug Thompson
2005-12-25 4:36 ` Andy Stewart [this message]
[not found] ` <3aa654a40512241258l2d3e0c57qf2345b143304bbef@mail.gmail.com>
2005-12-25 4:13 ` Andy Stewart
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=43AE21C9.4030900@comcast.net \
--to=andystewart@comcast.net \
--cc=linux-kernel@vger.kernel.org \
--cc=norsk5@yahoo.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