From owner-freebsd-stable@FreeBSD.ORG Sat May 26 15:47:33 2007 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0047916A46C; Sat, 26 May 2007 15:47:32 +0000 (UTC) (envelope-from mi+kde@aldan.algebra.com) Received: from aldan.algebra.com (aldan.algebra.com [216.254.65.224]) by mx1.freebsd.org (Postfix) with ESMTP id A7C3F13C468; Sat, 26 May 2007 15:47:32 +0000 (UTC) (envelope-from mi+kde@aldan.algebra.com) Received: from aldan.algebra.com (aldan [127.0.0.1]) by aldan.algebra.com (8.13.8/8.13.8) with ESMTP id l4QFUqGp024697 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 26 May 2007 11:30:52 -0400 (EDT) (envelope-from mi+kde@aldan.algebra.com) Received: from localhost (localhost [[UNIX: localhost]]) by aldan.algebra.com (8.13.8/8.13.8/Submit) id l4QFUqWc024696; Sat, 26 May 2007 11:30:52 -0400 (EDT) (envelope-from mi+kde@aldan.algebra.com) From: Mikhail Teterin To: bug-followup@freebsd.org, awallac3@uiuc.edu, jhb@freebsd.org, stable@freebsd.org Date: Sat, 26 May 2007 11:30:51 -0400 User-Agent: KMail/1.9.5 X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7whJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli" Cc: Subject: Re: amd64/89550: spin-lock panics continue (crash trace) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 26 May 2007 15:47:33 -0000 The patch in the PR allows our two Symbios 875 boards to work with FreeBSD-6.2-recent. However, the machine continues to suffer from the "spin lock held to long" panics every few days. Usually, there is a double-panic, which prevents crash dump from occuring. But this morning it succeeded. The full trace is available at http://aldan.algebra.com/~mi/bonkers-crash-4.txt The panic is from kern_mutex.c. The value of the delay-counting i is, no surprise, exactly 60000000. I'm not sure, if it is the sym-enabling patch, that causes the problem, or something else. Either way, it would be very useful for an expert to look at it -- and commit the (possibly modified) patch too. -mi