From owner-freebsd-current@FreeBSD.ORG Tue Jan 27 12:16:32 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 4DE4716A4CE for ; Tue, 27 Jan 2004 12:16:32 -0800 (PST) Received: from mail3.speakeasy.net (mail3.speakeasy.net [216.254.0.203]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1F19E43D5A for ; Tue, 27 Jan 2004 12:16:21 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: (qmail 14509 invoked from network); 27 Jan 2004 20:16:21 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 27 Jan 2004 20:16:21 -0000 Received: from 10.50.40.205 (gw1.twc.weather.com [216.133.140.1]) by server.baldwin.cx (8.12.10/8.12.10) with ESMTP id i0RKGAM4058145; Tue, 27 Jan 2004 15:16:17 -0500 (EST) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: Peter Losher , current@freebsd.org Date: Tue, 27 Jan 2004 13:34:07 -0500 User-Agent: KMail/1.5.4 References: <20040127082106.L14045@farside.isc.org> In-Reply-To: <20040127082106.L14045@farside.isc.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200401271334.07761.jhb@FreeBSD.org> X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp) Subject: Re: spin lock panic in 5.2-REL 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: Tue, 27 Jan 2004 20:16:32 -0000 On Tuesday 27 January 2004 03:47 am, Peter Losher wrote: > So, the quad-Xeon box serving half of ftp.freebsd.org was upgraded to > 5.2-RELEASE Sunday night, and a couple of hours ago it broke to gdb w/ a > spin lock panic. > > -=- > spin lock sched lock held by 0x8d2f7a00 for > 5 seconds > panic: spin lock held too long > cpuid = 4; > Debugger("panic") > Stopped at Debugger+0x55: xchgl %ebx,in_Debugger.0 > db> > db> > db> > db> [tail-] > -=- > > We had this issue after updating to 5.1-REL, one of our techs caught this > and reset the box to bring it back online, so I don't have any additional > info. I am not sure if this is a revisit of those same problems, or if > it's something new. This is a very hard to debug problem. If WITNESS is on it provides more useful information that can help track that down, but I wouldn't expect a production machine to be using WITNESS. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org