From: "Jim McKie" <jmk@plan9.bell-labs.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] SuperMicro P6DGU
Date: Mon, 8 Nov 2004 20:54:32 -0500 [thread overview]
Message-ID: <004601c4c5ff$0fd13e00$171aff87@narwhal> (raw)
In-Reply-To: <0f80678b4131e0ae5303b0f6e94c642d@quintile.net>
Our main fileserver is a SuperMicro dual-pIII, I'm out of
town until Friday but I think it is a 370DLE, 933MHz. It has
both venti+fossil running and boots standalone with its own
fossil partition. We have lots of SMP systems.
Make sure you have binaries (including libraries) made recently,
there was a compiler bug over the summer that could perhaps cause
weird things like fp stack underflow.
--jim
----- Original Message -----
From: "Steve Simon" <steve@quintile.net>
To: <9fans@cse.psu.edu>
Sent: Monday, November 08, 2004 6:32 AM
Subject: [9fans] SuperMicro P6DGU
> Hi,
>
> Trying a SuperMicro P6DGU dual PIII 600 motherboard
> in my all-in-one fossil/venti/cpu/auth server and
> have had a few(3) unexpected reboots when running
> with SMP enabled; the one panic I saw was an fp underflow
> in fossil.
>
> I am running it single cpu at the moment and its seems
> to be reliable (so far). It could have been a cosmic ray strike,
> or perhaps I have a duff motherboard (it was free).
>
> Anyone running multi cpu x86 servers? if so and they are cpu
> servers, anyone any idea if the all-in-one architecture might
> prevoke problems?
>
> -Steve
>
next prev parent reply other threads:[~2004-11-09 1:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-08 6:32 Steve Simon
2004-11-09 1:54 ` Jim McKie [this message]
2004-11-10 13:02 Steve Simon
2004-11-10 13:48 ` C H Forsyth
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='004601c4c5ff$0fd13e00$171aff87@narwhal' \
--to=jmk@plan9.bell-labs.com \
--cc=9fans@cse.psu.edu \
/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;
as well as URLs for NNTP newsgroup(s).