From owner-freebsd-stable@FreeBSD.ORG Tue Apr 6 20:31:30 2004 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 090FB16A4CE for ; Tue, 6 Apr 2004 20:31:30 -0700 (PDT) Received: from mail.sandvine.com (sandvine.com [199.243.201.138]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7CE8B43D1F for ; Tue, 6 Apr 2004 20:31:29 -0700 (PDT) (envelope-from don@sandvine.com) Received: by mail.sandvine.com with Internet Mail Service (5.5.2657.72) id ; Tue, 6 Apr 2004 23:30:01 -0400 Message-ID: From: Don Bowman To: "'tjg@meitech.com'" Date: Tue, 6 Apr 2004 23:30:00 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: text/plain; charset="iso-8859-1" cc: "'freebsd-stable@freebsd.org'" Subject: RE: FreeBSD 4.9 / Supermicro 7043P-8R / Crashes After 2-5 Minutes Of Uptime X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Apr 2004 03:31:30 -0000 From: Doug White [mailto:dwhite@gumbysoft.com] > On Fri, 2 Apr 2004, Gustafson, Tim wrote: > > > Hello > > > > I have a brand spanking new Supermicro 7043P-8R server with > dual Intel > > 3.2gHZ Xeon processors and 4GB of Kingston memory. > > > > I installed FreeBSD 4.9 on the box and it gives me the > following message on > > the screen about 2-5 minutes after it finished booting: > > > > boot() called on CPU#0 > > This means the machine is trying to reboot for some reason. > Typically, > its due to a panic. You should get a lot more output with a > message and a > traceback, or if you have ddb compiled in, a db> prompt. > > If you aren't getting anything, try setting up serial console > and log to > another machine. > > > Is this a known issue with Supermicro Motherboards? Does > anyone have any > > suggestions as to a potential patch or other fix? > > > > I'm going to start doing the hardware swapping thing in a > bit and see if > > that fixes anything, but I'd really like to hear back from > anyone who has > > any experience with this issue. > > Random panics are generally caused by bad memory, CPU cache, > anod other > hardware issues. FYI, i'm using the same system. I would guesstimate that you have a problem running out of ram (sounds silly, but yes) due to the large amount of ram you have. Here's what i have in mine, currently running 5.2 kern.maxswzone=16777216 kern.vm.kmem.size=314572800 kern.ipc.nmbclusters=16384 kern.ipc.nmbufs=65536 kern.ipc.shm_use_phys=1 net.inet.tcp.tcbhashsize=16384 kern.ipc.maxsockets=32768 kern.maxfiles=34000 but i have run 4.7 and releng_4 on it. Definitely i would suggest running memtest86 on it for a bit [at least 24 hours], but with the ECC, memory errors would have to be gross to be noticeable.