From owner-freebsd-stable@FreeBSD.ORG Tue Apr 6 20:07:22 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 C1BCC16A4CE for ; Tue, 6 Apr 2004 20:07:22 -0700 (PDT) Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id B5B5E43D2F for ; Tue, 6 Apr 2004 20:07:22 -0700 (PDT) (envelope-from dwhite@gumbysoft.com) Received: by carver.gumbysoft.com (Postfix, from userid 1000) id C49AF72DF0; Tue, 6 Apr 2004 19:09:11 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by carver.gumbysoft.com (Postfix) with ESMTP id C1D2C72DBF; Tue, 6 Apr 2004 19:09:11 -0700 (PDT) Date: Tue, 6 Apr 2004 19:09:11 -0700 (PDT) From: Doug White To: "Gustafson, Tim" In-Reply-To: <86ECB35C998DCC49AD435A099AFACCD1A7AA44@RIPLEY> Message-ID: <20040406190724.W93257@carver.gumbysoft.com> References: <86ECB35C998DCC49AD435A099AFACCD1A7AA44@RIPLEY> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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:07:22 -0000 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. -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org