public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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:06:46 -0500	[thread overview]
Message-ID: <43AE1AD6.1030300@comcast.net> (raw)
In-Reply-To: <20051224194621.73206.qmail@web50113.mail.yahoo.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Doug Thompson wrote:
> With the Opteron Bank 4 value you gave, this decodes to:
> 
> 
> Decoding MCE value as MCi_STATUS: 'b200000000070f0f'
> Bit  63:    Valid error
> Bit  61:    UNCORRECTED error
> Bit  60:    MCA Error Reporting Enabled
> Bit  57:    Process Context Corrupt
>             HyperTransport Link Number= 0
>             Extended Error Code = 0x7 - WatchDog error
> 
> BUS Error:
>         Processor(generic)
>         TimeOut(timed out)
>         Memory Transaction Type(generic)
>         Mem or IO(generic)
>         Cache Level(generic)
> 
> You had an Uncorrectable Error. 
> Since you did not post an address error, I assume that it did NOT report such. Therefore, because
> of the WatchDog error, there might be an error between the CPU and memory.  There is a hardware
> problem definitely.
> 
> CPU-Mem Controller
> Even bad memory DIMM
> 
> doug thompson

HI Doug,

Thank you for your quick reply.  There was no "address error" - the only
 thing on the serial console is what I posted.

In the past, this board, the CPUs, and these memory DIMMs have passed 24
continuous hours of memtest, but perhaps something has deteriorated in
the mean time.  I'll run memtest again to see if I can find a problem.

FYI:  This MB (MSI K8T Master2 FAR) has been problematic since day one.
 A BIOS upgrade improved stability, but I've never gotten more then 21
straight days of uptime on this machine (compared to 200-300 days on
several other machines in my house).  I've had *many* random hangs but
seldom does something get printed on the serial console.  When it does
hang, the serial console is unresponsive.

I'll be swapping out this MB in favor of a Tyan.  I've put up with it
long enough.  Assuming that the Tyan MB solves the problem, I won't be
purchasing any more MSI MBs (and neither will my friends if I have
anything to say about it).

Thanks again for the help!

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

iD8DBQFDrhrVHl0iXDssISsRAhzLAJoCb5yTL2meARSIVhnQjP54AVVPOwCeJ2aS
NWkOTzLQ57U6tuU8h+YM9bM=
=NH89
-----END PGP SIGNATURE-----

  reply	other threads:[~2005-12-25  4:06 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 [this message]
2005-12-25  4:19     ` Doug Thompson
2005-12-25  4:36       ` Andy Stewart
     [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=43AE1AD6.1030300@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