From owner-freebsd-hardware Tue Jul 23 11:21:20 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4348237B400 for ; Tue, 23 Jul 2002 11:21:16 -0700 (PDT) Received: from cobra.acceleratedweb.net (cobra-gw.acceleratedweb.net [207.99.79.37]) by mx1.FreeBSD.org (Postfix) with SMTP id A0FB243E65 for ; Tue, 23 Jul 2002 11:21:12 -0700 (PDT) (envelope-from simon@optinet.com) Received: (qmail 73400 invoked by uid 106); 23 Jul 2002 18:20:20 -0000 Received: from 24-90-121-13.nyc.rr.com (HELO station1) (24.90.121.13) by cobra.acceleratedweb.net with SMTP; 23 Jul 2002 18:20:20 -0000 From: "Simon" To: "freebsd-hardware@freebsd.org" Date: Tue, 23 Jul 2002 14:22:16 -0400 Reply-To: "Simon" X-Mailer: PMMail 2000 Professional (2.10.2010) For Windows 2000 (5.0.2195;2) In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: Re: Supermicro and FreeBSD? Message-Id: <20020723182112.A0FB243E65@mx1.FreeBSD.org> Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi, Although I haven't tried their Xeon boards, Supermicro makes solid boards and cases, we use them exclusively. Make sure you get %100 compatible RAM (different brand doesn't mean it's compatible or reliable), if that doesn't help, try different board, it's possible for the board itself to be faulty. I really doubt this is FreeBSD issue, try running linux on this box and see how it handles, but be aware, freebsd is much more sensitive to flaky hardware (which is a good thing, in a long run). I would strip everything down, leave a single CPU, 1 (or 2 if required) modules of RAM, one drive and take it from there. There are memory tests, harddrive IO tests, see what causes the crash. Failed buildworld could mean anything, a failed memory test alone will most likely indicate faulty memory, you get the picture. PS: I once had a SCA backplane break and it would cause panics, first I thought it was RAM, but then realized that it started to happen after I swapped drives in RAID... so as you can see, it can be a number of things, but rarely the FreeBSD itself. Good luck (sometimes you just need it)! -Simon On Tue, 23 Jul 2002 11:39:28 -0600 (MDT), C.J. wrote: >I'm having some issues with three separate SuperMicro 6022c SuperServers. >Random reboots, sig 11's in /var/log/messages (most of the coming from >ident2), sig 11's when trying to buildworld (rare but it has happened), >etc. > >They all have the same hardware configuration: >* SuperMicro 6022c w/ SUPER P4DC6+ motherboard and Integrated Adaptec > AIC-7899W dual channel U160 SCSI controller. > >* Dual Pentium Xeon 2.0 GHz processors. > >* Integrated Intel 82559 LAN controller. > >* Quantum Atlas 10k III 18GB U160 SCSI drive. > >* 2GB of PC800 RDRAM ram (512meg sticks x 4). > > >Here's what I've done: >* Swapped power supplies between boxes. > >* Backed off to 1GB of RAM. > >* Removed one processor. > >* Swapped RAM between boxes. > >* Reinstalled FreeBSD (numerous times). > >* Installed WinXP *shiver* and ran some hardware diagnostic software >(passed every time). > >* Tried a different brand of RAM. > >So after trying everything above and coming to the conclusion that >SuperMicro products just suck, I give them a call and try to get more >ideas and the tech tells me he doesn't think they are compatible with >FreeBSD and I should try running RedHat 7.3, which is of course a non >option :-) > >Does anyone else use these boxes with FreeBSD and have luck with them, or >are SuperMicro and FreeBSD not compatible? Does anyone else use FreeBSD >and Dual Xeons, or is that too bleeding edge? Any help or suggestions >would be greatly appreciated :) > >Thanks in advance, > > >- C.J. > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-hardware" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message