Date: Tue, 29 Jun 2004 12:40:38 -0700 From: Colin Percival <colin.percival@wadham.ox.ac.uk> To: Daniel Lang <dl@leo.org> Cc: freebsd-current@freebsd.org Subject: Re: kern/68442: panic - acquiring duplicate lock of same type: "sleepq chain" Message-ID: <6.1.0.6.1.20040629120017.02a27f48@popserver.sfu.ca> In-Reply-To: <20040629183557.GA77135@atrbg11.informatik.tu-muenchen.de> References: <20040628202434.GA73213@atrbg11.informatik.tu-muenchen.de> <20040629153921.GE75577@atrbg11.informatik.tu-muenchen.de> <200406291200.12030.jhb@FreeBSD.org> <20040629163028.GM75577@atrbg11.informatik.tu-muenchen.de> <20040629170014.GC1144@green.homeunix.org> <20040629183557.GA77135@atrbg11.informatik.tu-muenchen.de>
next in thread | previous in thread | raw e-mail | index | archive | help
At 11:35 29/06/2004, Daniel Lang wrote: >So I have a line of code for the failing address: > ># addr2line -e kernel.debug 0xc053932b >/usr/src/sys/kern/subr_witness.c:898 > >which is (in my kernel): > >[..] > lock1 = &(*lock_list)->ll_children[(*lock_list)->ll_count - 1]; >[..] Well, that makes sense... the fault was accessing 0x34, and ll_count is at offset 0x34 within its structure. So somewhere between line 708 707: if (*lock_list == NULL) 708: return; and line 898, *lock_list is being modified. Colin Percival
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6.1.0.6.1.20040629120017.02a27f48>