From owner-freebsd-current@FreeBSD.ORG Mon Apr 19 17:46:17 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C8B271065677 for ; Mon, 19 Apr 2010 17:46:17 +0000 (UTC) (envelope-from mj@feral.com) Received: from ns1.feral.com (ns1.feral.com [192.67.166.1]) by mx1.freebsd.org (Postfix) with ESMTP id 883E28FC21 for ; Mon, 19 Apr 2010 17:46:17 +0000 (UTC) Received: from [192.168.221.2] (remotevpn [192.168.221.2]) by ns1.feral.com (8.14.3/8.14.3) with ESMTP id o3JHBvXL040304 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for ; Mon, 19 Apr 2010 10:11:57 -0700 (PDT) (envelope-from mj@feral.com) Message-ID: <4BCC8EDC.1090907@feral.com> Date: Mon, 19 Apr 2010 10:11:56 -0700 From: Matthew Jacob Organization: Feral Software User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.9) Gecko/20100330 Fedora/3.0.4-1.fc11 Thunderbird/3.0.4 MIME-Version: 1.0 To: freebsd-current@freebsd.org References: In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Greylist: Sender DNS name whitelisted, not delayed by milter-greylist-4.2.3 (ns1.feral.com [192.168.221.1]); Mon, 19 Apr 2010 10:11:57 -0700 (PDT) Subject: Re: panic: deadlkres: possible deadlock detected X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: mj@feral.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Apr 2010 17:46:17 -0000 On 04/19/2010 08:03 AM, Attilio Rao wrote: > 2010/4/19 Erik Cederstrand: > >> Hi >> >> I'm testing ClangBSD in a VirtualBox client and ran into a panic on the client, but I don't think it's clang-related. I haven't tried kernel debugging before. I tried getting a backtrace as described in http://old.nabble.com/Re%3A-ia64--%3E-panic%3A-deadlkres%3A-possible-deadlock-detected-for-0xe00000001187d880%2C-blocked-for-1801437-ticks-p28123802.html and this i the result: >> >> http://tinypic.com/r/2llegza/5 >> >> Any pointers on ho to debug this further? >> > I think we have to bless getblk. However your system may have got > buffers shortage due to bufdaemon deficiencies. > > Are you using 8.0 or current? > > Attilio > > > I've seen this in -current as of yesterday