mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Allen Martin" <AMartin@nvidia.com>
To: "Rumi Szabolcs" <rumi_ml@rtfm.hu>
Cc: <linux-kernel@vger.kernel.org>
Subject: RE: Athlon64 + Nforce4 MCE panic
Date: Fri, 14 Jul 2006 11:18:38 -0700	[thread overview]
Message-ID: <DBFABB80F7FD3143A911F9E6CFD477B00E48CFD9@hqemmail02.nvidia.com> (raw)
In-Reply-To: <20060714093749.07529924.rumi_ml@rtfm.hu>

> 1x Asrock NF4G-SATA2 motherboard 
> (http://www.asrock.com/product/939NF4G-SATA2.htm)
> 1x Athlon64 "Venice" 3500+ with a huge Arctic cooler
> 1x Corsair kit of 2 matched 512MB DDR400 modules
> 1x Seagate 160GB SATA drive
> 1x well ventilated Chieftec rackmount chassis w/PSU

You don't have any PATA devices at all?  SATA is a lot more resilient to
this type of problem.

> So I have a reason to believe that this could be a chipset specific
> problem which not only affects me but quite a number of NF4 users,
> most of which (using Windo$$$) will probably never know why their
> system suddenly hung after some weeks or months of use...

Windows will generate a bugcheck on an MCA exception just like Linux.
We have really detailed statistics on Windows bugchecks due to OCA, so I
know this is not a widespread issue at least on Windows.


> Or maybe just a neutrino hit to the CPU?
> What do you think?

The stack trace will almost always tell you exactly what device timed
out the PIO, you should start there.
-----------------------------------------------------------------------------------
This email message is for the sole use of the intended recipient(s) and may contain
confidential information.  Any unauthorized review, use, disclosure or distribution
is prohibited.  If you are not the intended recipient, please contact the sender by
reply email and destroy all copies of the original message.
-----------------------------------------------------------------------------------

  reply	other threads:[~2006-07-14 18:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-13  7:01 Rumi Szabolcs
2006-07-13  7:12 ` Avuton Olrich
2006-07-13 11:44 ` Alan Cox
2006-07-14  4:30 ` Allen Martin
2006-07-14  7:37   ` Rumi Szabolcs
2006-07-14 18:18     ` Allen Martin [this message]
2006-07-15  7:28       ` Rumi Szabolcs

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=DBFABB80F7FD3143A911F9E6CFD477B00E48CFD9@hqemmail02.nvidia.com \
    --to=amartin@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rumi_ml@rtfm.hu \
    /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®