Date: Tue, 9 Mar 2004 22:36:30 +0100 From: flag@oltrelinux.com To: Peter Wemm <peter@wemm.org> Cc: FreeBSD_Current <freebsd-current@freebsd.org> Subject: Re: LOR in yesterday CURRENT: system map vs Giant Message-ID: <20040309213630.GA656@tin.it> In-Reply-To: <200403081210.40697.peter@wemm.org> References: <20040307184421.GA18871@tin.it> <200403081210.40697.peter@wemm.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Mar 08, 2004 at 12:10:40PM -0800, Peter Wemm wrote: > > This particular one was my fault, I believe it's been fixed. However, I > also believe this particular LOR happens via other code paths that were > not my fault. actually it's still there, and today (after a succesful buildkernel/installkernel) i got eveen a solid freeze of my laptop with this on my text console: panic: lockmgr: locking against myself at line 370 in file /usr/src/sys/kern/kern_lock.c [something else] i had DDB turned on in my kernel so i tried to panic but it was completely freezed. Now, i built again a new kernel without DDB, wishing that the next crash will dump directly to disk... well, actually i don't really know if disabling DDB would bring me directly to a crash dump, and i don't think so but this problem (i mean the panic) shows a really random pattern and it's difficult to track it down... any idea is welcome, i'm all ears... bye -- Paolo Italian FreeBSD User Group: http://www.gufi.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040309213630.GA656>