From: Bill Davidsen <davidsen@tmr.com>
To: Bill Davidsen <davidsen@tmr.com>
Cc: Michal Szymanski <msz@astrouw.edu.pl>,
SMP list <linux-smp@vger.kernel.org>
Subject: Re: FC4 crashes repeatedly on Supermicro AS1020A-T dual-core Opterons, SMP
Date: Wed, 24 May 2006 16:28:07 -0400 [thread overview]
Message-ID: <4474C1D7.3040005@tmr.com> (raw)
In-Reply-To: <4474C0D1.2030701@tmr.com>
Bill Davidsen wrote:
> Michal Szymanski wrote:
>
>> On Fri, May 05, 2006 at 10:18:36AM -0500, Robert M. Hyatt wrote:
>>
>>
>>> One note. I am running on a quad 875 system, but am using Suse
>>> rather than FC4. It is running perfectly reliable (this is a 4 cpu,
>>> dual-core, 2.2ghz box, 8 processors total). I had problems with FC4
>>> myself, although it runs perfectly on my normal dual xeon boxes...
>>>
>>> On Fri, 5 May 2006, Bill Davidsen wrote:
>>>
>>>
>>>
>>>> Michal Szymanski wrote:
>>>>
>>>>
>>>>
>>>>> Hi all,
>>>>>
>>>>> I have recently purchased three Supermicro AS1020A-T servers equipped
>>>>> with two dual-core Opterons 280 each. H8DAR-T motherboards, 8 or
>>>>> 12 GB
>>>>> RAM. The systems carry FC4 x86_64 with proprietary driver (made by
>>>>> Adaptec) for the onboard Marvell 88SX6041 SATA Controller. Original
>>>>> (install) kernel 2.6.11-1.1369_FC4smp - unfortunately not
>>>>> upgradable due
>>>>> to the lack of the SATA driver for other kernel versions.
>>>>>
>>>>> 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.
>>>>> ...
>>>>> 2. I ran non-SMP 2.6.11 kernel (with Adaptec driver) on another
>>>>> machine.
>>>>> There have been two test repeating 1.3g jobs running on it (each
>>>>> getting 50%
>>>>> of the single CPU used by the system) for over 50 hours now, no
>>>>> crashes.
>>>>> Also, a single test job running on SMP kernel gave no crashes in
>>>>> 24 hours.
>>>>>
>>>>>
>>>>
>>>> What happens if you use only one CPU? Either with a uni kernel (you
>>>> should have gotten one) or "maxcpus=1" in the boot commands. You
>>>> are running a custom kernel with custom drivers, so you really
>>>> should be asking the supplier, all we can do is suggest things
>>>> which might provide extra information.
>>>>
>>>
>>
>> Hi all,
>>
>> I got 3 copies of Roberts' message but none of Bill's :-)
>>
>> Still, I don't quite understand Bill's question ("What happens if you
>> use only one CPU?"). The answer is quoted just above this question!
>> There were no crashes with the system running on non-SMP kernel.
>>
>>
>
> It's a great answer, but not to my question. I wasn't asking what
> happens with a different kernel, but what happens when you run the SMP
> kernel and ==>use<== only one CPU by setting the max cpu to one. The
> uni kernel doesn't have a lot of code in an SMP kernel, so it haides a
> lot of possible questions.
s/haides/hides/
Yes, I know my original question wasn't explicit on what I was asking,
it's just the first thing I would have tried because I wouldn't have
that uni kernel around.
--
bill davidsen <davidsen@tmr.com>
CTO TMR Associates, Inc
Doing interesting things with small computers since 1979
next prev parent reply other threads:[~2006-05-24 20:28 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 [this message]
2006-05-05 15:23 ` cerise
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=4474C1D7.3040005@tmr.com \
--to=davidsen@tmr.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.