mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Roger Heflin" <rheflin@atipa.com>
To: "'Orion Poplawski'" <orion@cora.nwra.com>,
	<linux-kernel@vger.kernel.org>
Subject: RE: Help with machine check exception
Date: Thu, 12 Jan 2006 13:18:43 -0600	[thread overview]
Message-ID: <EXCHG2003GR881Np7vX00000c0f@EXCHG2003.microtech-ks.com> (raw)
In-Reply-To: <43C6974F.2080104@cora.nwra.com>

 

> 
> I would have expected 2 CPU temps (being dual-processor).  
> Maybe Remote is the second.
> 
> With 4 copies of burnK7:
> 
> machine with problems:
> 
> CPU:      +71.25°C  (low  =   +10°C, high =   +50°C)     ALARM
> Board:    +47.25°C  (low  =   +10°C, high =   +35°C)     ALARM
> Remote:   +68.50°C  (low  =   +10°C, high =   +35°C)     ALARM
> 
> machine without:
> 
> CPU:      +61.25°C  (low  =   +10°C, high =   +50°C)     ALARM
> Board:    +47.25°C  (low  =   +10°C, high =   +35°C)     ALARM
> Remote:   +74.25°C  (low  =   +10°C, high =   +35°C)     ALARM
> 
> 
> So *maybe* cooling?
> 

That is a little on the warm side, I believe AMD's posted limit
is 70C for most of their chips, assuming the measuring point is
in the correct place for the 70C limit.

Certain cpus also seem to have more issues than others, so one cpu
out of a batch can be ok with a certain setup, and another from the
same batch will mce under similar conditions.

Did you build the machines yourself or did you buy them this way?

Machines getting MCE's that often will fail the burnin testing that
we use here.

And machines that produce those kinds of temps will also fail our
burn-in process just because that seems a bit too warm.

                           Roger


  reply	other threads:[~2006-01-12 19:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-12 16:30 Orion Poplawski
2006-01-12 17:07 ` Orion Poplawski
2006-01-12 17:33   ` Alan Cox
2006-01-12 17:52     ` Orion Poplawski
2006-01-12 19:18       ` Roger Heflin [this message]
2006-01-12 17:32 ` Roger Heflin

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=EXCHG2003GR881Np7vX00000c0f@EXCHG2003.microtech-ks.com \
    --to=rheflin@atipa.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=orion@cora.nwra.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

all inboxes | Powered by JetHome®