Symmetric Multiprocessing (SMP) development
 help / color / mirror / Atom feed
From: cerise@armory.com
To: msz@astrouw.edu.pl, linux-smp@vger.kernel.org
Subject: Re: FC4 crashes repeatedly on Supermicro AS1020A-T dual-core Opterons, SMP
Date: Fri, 5 May 2006 08:23:44 -0700	[thread overview]
Message-ID: <20060505152344.GA8408@boogeyman> (raw)
In-Reply-To: <445B5A8A.3060106@tmr.com>

> Michal Szymanski wrote:
>
> >All systems crash (either hang with some "machine check exception"
> >kernel messages or reset) when loaded with repeating runs of 1.3gb, CPU
> >intensive with some I/O. I run 2 or 4 jobs simultaneously and they had
> >never survived more than a few hours.

Let's try the easy stuff first -- if it's crashing with a machine check
exception, then let's disable machine check exceptions, and see if things
still break.

Try booting with the parameter "nomce".  Be aware that mce is a mechanism
for the processor to inform the kernel of thermal issues or component 
failure.  You'll only want to disable this mechanism if you aren't having
thermal problems.  

Of course, if you are having thermal problems, it's probably a good idea to
resolve those before cranking up the other 3/4s of your system.  ; )

Hope that helps!

-Phil/CERisE

P.S.  I came a little late to this party -- I didn't see the original message.
Did you include the text of the kernel crash?

  parent reply	other threads:[~2006-05-05 15:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-18 19:11 FC4 crashes repeatedly on Supermicro AS1020A-T dual-core Opterons, SMP Michal Szymanski
2006-05-05 14:00 ` Bill Davidsen
2006-05-05 15:18   ` Robert M. Hyatt
2006-05-05 15:28     ` cerise
2006-05-05 16:31       ` Robert M. Hyatt
2006-05-09 12:23     ` Michal Szymanski
2006-05-24 20:23       ` Bill Davidsen
2006-05-24 20:28         ` Bill Davidsen
2006-05-05 15:23   ` cerise [this message]
2006-05-12 10:54     ` Michal Szymanski

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=20060505152344.GA8408@boogeyman \
    --to=cerise@armory.com \
    --cc=linux-smp@vger.kernel.org \
    --cc=msz@astrouw.edu.pl \
    /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