From owner-freebsd-stable@FreeBSD.ORG Tue Jun 7 18:27:11 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org 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 3E64B16A41C for ; Tue, 7 Jun 2005 18:27:11 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [204.156.12.53]) by mx1.FreeBSD.org (Postfix) with ESMTP id CD0A443D4C for ; Tue, 7 Jun 2005 18:27:10 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by cyrus.watson.org (Postfix) with ESMTP id 18A0B46B4C; Tue, 7 Jun 2005 14:27:08 -0400 (EDT) Date: Tue, 7 Jun 2005 19:28:02 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: delphij@delphij.net In-Reply-To: <1118146251.755.4.camel@spirit> Message-ID: <20050607192712.F65983@fledge.watson.org> References: <2D2A5D81-9E95-4D83-B479-D61BBB39C25F@nordahl.net> <1118146251.755.4.camel@spirit> MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-1381648810-1118168882=:65983" Cc: freebsd-stable@freebsd.org, Frode Nordahl Subject: Re: propagate_priority panic 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: Tue, 07 Jun 2005 18:27:11 -0000 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --0-1381648810-1118168882=:65983 Content-Type: TEXT/PLAIN; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: QUOTED-PRINTABLE On Tue, 7 Jun 2005, Xin LI wrote: > =FF=FF 2005-06-07=FF=FF=FF=FF 09:32 +0200=FF=FFFrode Nordahl=FF=FF=FF=FF= =FF=FF >> Dear colleagues, > [snip] >> db> trace >> Tracing pid 86 tid 100089 td 0xc54a1e10 >> propagate_priority(c54a1e10,c08f3750,c54c6960,c0901ae0,c54a1e10) at >> propagate_priority+0x7f > > This looks like what I have been observed within a recent -CURRENT=20 > kernel, which indicates a bug that was fixed recently. propagate_priority() panics are often a symptom of an attempt to use a=20 mutex operation on a non-mutex, so this could be a symptom of an attempt=20 to call mtx_lock() on a free'd data structure (or related bug). Robert N M Watson --0-1381648810-1118168882=:65983--