From owner-freebsd-current@FreeBSD.ORG Thu Nov 25 07:24:43 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B603216A4CE for ; Thu, 25 Nov 2004 07:24:43 +0000 (GMT) Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 96E2A43D49 for ; Thu, 25 Nov 2004 07:24:43 +0000 (GMT) (envelope-from dwhite@gumbysoft.com) Received: by carver.gumbysoft.com (Postfix, from userid 1000) id 8417B72DF4; Wed, 24 Nov 2004 23:24:43 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by carver.gumbysoft.com (Postfix) with ESMTP id 8173172DCB; Wed, 24 Nov 2004 23:24:43 -0800 (PST) Date: Wed, 24 Nov 2004 23:24:43 -0800 (PST) From: Doug White To: Hogan Whittall In-Reply-To: <20041123182254.GB10721@ninthgate.net> Message-ID: <20041124231627.I2006@carver.gumbysoft.com> References: <20041123182254.GB10721@ninthgate.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-current@freebsd.org Subject: Re: Random panics with 5.3-REL, SMP X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Nov 2004 07:24:43 -0000 On Tue, 23 Nov 2004, Hogan Whittall wrote: > Dell PE6450 server, 4xP3-700 Xeon, 4gb ram, system disks reside on > a 2 disk RAID1 attached to a MegaRAID controller. Wireless is a > D-Link DWL-G520-B, also has Intel Pro/100 ethernet. For the record, I have a PE6300 (4x500MHz) I'm testing a fix for panics of the form panic: Previous IPI is stuck if thats one of the "random panics" you're seeing. The thread "number of CPUs and IPI panic" in -current has details, and a temporary patch is available from http://people.freebsd.org/~ups/ipi4_patch I believe this patch will apply to both RELENG_5 and -CURRENT, for now. I was having a problem with random resets (no panic, just reset) and traced it to a broken cpu0. Replacing it made the resets go away. If you have room you may want to install RedHat or Windows on another partition, load up the OpenManage tools, and inspect the system event log for anything peculiar. If you've never run this before then you may need to clear the event log for it to log any new events. If you have a DRAC card in the machine you can use that too. -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org