From owner-freebsd-stable@FreeBSD.ORG Wed Feb 23 21:24:51 2005 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 E021816A4CE for ; Wed, 23 Feb 2005 21:24:51 +0000 (GMT) Received: from ebb.errno.com (ebb.errno.com [66.127.85.87]) by mx1.FreeBSD.org (Postfix) with ESMTP id AE66243D45 for ; Wed, 23 Feb 2005 21:24:51 +0000 (GMT) (envelope-from sam@errno.com) Received: from [66.127.85.91] (sam@[66.127.85.91]) (authenticated bits=0) by ebb.errno.com (8.12.9/8.12.6) with ESMTP id j1NLOpWi016656 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 23 Feb 2005 13:24:51 -0800 (PST) (envelope-from sam@errno.com) Message-ID: <421CF4D1.1050807@errno.com> Date: Wed, 23 Feb 2005 13:25:37 -0800 From: Sam Leffler User-Agent: Mozilla Thunderbird 1.0RC1 (X11/20041208) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Doug White References: <1109047539.786.10.camel@nicoya.surfbbx> <20050223103623.J7804@carver.gumbysoft.com> In-Reply-To: <20050223103623.J7804@carver.gumbysoft.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-stable@freebsd.org cc: Eric Thornton Subject: Re: AP #1 (PHY#1) failed! Panic (y/n)? 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, 23 Feb 2005 21:24:52 -0000 Doug White wrote: > On Mon, 21 Feb 2005, Eric Thornton wrote: > > >>Got this on a reboot tonight. I dont have the actual kernel output, but >>i pieced it together from the start of a normal boot. It happened right >>after "ACPI APIC Table: " I hit "y" and powercycled and >>have not been able to reproduce the error. >> >>5.3-RELEASE-p5 FreeBSD 5.3-RELEASE-p5 #11: Mon Feb 14 22:16:56 EST 2005 >> >>Is this a rare occurence? > > > It should never happen. This may be indicative of a problem with that CPU. > You might run the Dell diagnostics on that machine. > I've seen this randomly on a dual-Xeon Dell 450 for >1 year (i.e. lots of different os versions). I believe it's a race/bug in the BSP startup logic. Sam