Date: Mon, 19 Apr 2010 17:03:35 +0200 From: Attilio Rao <attilio@freebsd.org> To: Erik Cederstrand <erik@cederstrand.dk> Cc: FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: panic: deadlkres: possible deadlock detected Message-ID: <u2q3bbf2fe11004190803l9e9e9c26rb5b11ec77a991ee6@mail.gmail.com> In-Reply-To: <DE06953A-C52B-4BF0-9F5F-BCECE62F1803@cederstrand.dk> References: <DE06953A-C52B-4BF0-9F5F-BCECE62F1803@cederstrand.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
2010/4/19 Erik Cederstrand <erik@cederstrand.dk>: > Hi > > I'm testing ClangBSD in a VirtualBox client and ran into a panic on the c= lient, but I don't think it's clang-related. I haven't tried kernel debuggi= ng before. I tried getting a backtrace as described in http://old.nabble.co= m/Re%3A-ia64--%3E-panic%3A-deadlkres%3A-possible-deadlock-detected-for-0xe0= 0000001187d880%2C-blocked-for-1801437-ticks-p28123802.html and this i the r= esult: > > 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 --=20 Peace can only be achieved by understanding - A. Einstein
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?u2q3bbf2fe11004190803l9e9e9c26rb5b11ec77a991ee6>