From owner-freebsd-current@FreeBSD.ORG Fri Dec 12 10:38:57 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6B20A1065676 for ; Fri, 12 Dec 2008 10:38:57 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 467958FC1F for ; Fri, 12 Dec 2008 10:38:57 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [65.122.17.41]) by cyrus.watson.org (Postfix) with ESMTP id E3EA046B51; Fri, 12 Dec 2008 05:38:56 -0500 (EST) Date: Fri, 12 Dec 2008 10:38:56 +0000 (GMT) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Kostik Belousov In-Reply-To: <20081212095238.GY2038@deviant.kiev.zoral.com.ua> Message-ID: References: <4940A685.7040608@psg.com> <494216C2.7080606@kkip.pl> <20081212095238.GY2038@deviant.kiev.zoral.com.ua> User-Agent: Alpine 1.10 (BSF 962 2008-03-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Randy Bush , Bartosz Stec , FreeBSD Current Subject: Re: panic: sleeping thread & bufwrite: buffer is not busy??? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Fri, 12 Dec 2008 10:38:57 -0000 On Fri, 12 Dec 2008, Kostik Belousov wrote: >> Unfortunately I cannot provide more debug information at this time >> because kernel was built without debugging options. (I will rebuild it >> if needed) However I can still provide some info: >> - kernel panic while loading modules, just after loding ZFS module (I >> have RAIDZ configuration) and after a couple of minutes without any >> visible action on the screen. >> - I have this panic with *every* build I made after 7 Dec 2008, but I >> don't remember wchich day exactly I have experienced that for the first >> time. >> - For now I'm using kernel builded 7 Dec 2008 and no panic seen at all. > > You are mixing the issues without a reason. To claim that you problem is > similar, you need to show the similar backtrace. The panic shown is the late > manifestation of a problem, it is kind a catch-all for some sort of locking > issues. This is the second report of weird rwlock-related panics in a week. We should read the code on this one closely, but I can't help but notice that it's similar to Roman's report of an rwlock-related panic. Was there a locking/scheduling change in the last week or two in -current that could explain these symptoms? Robert N M Watson Computer Laboratory University of Cambridge