Date: Tue, 20 Apr 2010 08:50:35 +0200 From: Erik Cederstrand <erik@cederstrand.dk> To: Attilio Rao <attilio@freebsd.org> Cc: FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: panic: deadlkres: possible deadlock detected Message-ID: <D9A0A5FB-D49A-4F57-92D4-EEDC0EEAC643@cederstrand.dk> In-Reply-To: <u2q3bbf2fe11004190803l9e9e9c26rb5b11ec77a991ee6@mail.gmail.com> References: <DE06953A-C52B-4BF0-9F5F-BCECE62F1803@cederstrand.dk> <u2q3bbf2fe11004190803l9e9e9c26rb5b11ec77a991ee6@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Den 19/04/2010 kl. 17.03 skrev Attilio Rao: > 2010/4/19 Erik Cederstrand <erik@cederstrand.dk>: >> 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? This is current (the latest ClangBSD revision). I was running pho's stress2 test suite when this happened. Thanks, Erik
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?D9A0A5FB-D49A-4F57-92D4-EEDC0EEAC643>