mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Roger Heflin" <rheflin@atipa.com>
To: <linux-kernel@vger.kernel.org>
Subject: Question about Kernel MCE and what exactly they could mean
Date: Thu, 30 Jun 2005 09:38:07 -0500	[thread overview]
Message-ID: <EXCHG2003YKpDS7hx2700000499@EXCHG2003.microtech-ks.com> (raw)

Hello,

I have customer that is getting MCE errors, the errors are
non consistantly on a single cpu (this is a opteron system
with separate memory busses),  and the customer believes
that these correspond with the same time he sshes into the
machine from external, they also appear to only be a serious 
issue just after boot up, if the machine survives the first
few sshes, we don't seem to have an issue later, so things
seem to be a early boot up issue of some sort.

The kernel is a Suse 2.4 kernel variant (2.4.21-143), 
I don't expect anyone to likely know if it is a bug.

I have debugged and fixed a large number of machines getting
kernel panic mce errors (by replacing cpu, and if it still 
occurs replacing memory), but I have never seen one being 
started by something like inbound ssh, and have never seen
it move from cpu to cpu with what looks like the same "cause".

The pro's of it being hardware are:
	It gets mce errors.

The pro's of it being software are:
	They aren't consistant on cpu's
	The machine survives heavy HPL runs and does not appear
		to have broken hardware.
	A specific user action seems to cause the issue.

This issue does seem to occur several times a week.

Anyone have any ideas or experience of whether this is a
kernel bug or hardware problem?

                        Roger


                 reply	other threads:[~2005-06-30 14:35 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=EXCHG2003YKpDS7hx2700000499@EXCHG2003.microtech-ks.com \
    --to=rheflin@atipa.com \
    --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®