On 06-Jan-2003 ryan beasley wrote:
> On Sun, Jan 05, 2003 at 08:54:01PM -0600, ryan beasley wrote:
>> I'm including a GDB capture including traceback and some locking
>> information. Anyone have any ideas? Is there any other data I should
>> grab and submit?
>
> I'm really sorry for following up to myself again, but the following
> might be useful:
>
> (gdb)
>#8 0xc01bce28 in enroll (description=0xc02e3718 "vnode interlock",
> lock_class=0xc0300fc0)
> at /home/ryanb/FREDRIK_DP_INV/sys/kern/subr_witness.c:985
> 985 if (w->w_name == description || (w->w_refcount > 0 &&
> Current language: auto; currently c
> (gdb) p *w
> $16 = {w_name = 0xc16fd8fe <Address 0xc16fd8fe out of bounds>,
> w_class = 0xc0300fc0, w_list = {stqe_next = 0xc032fa50}, w_typelist = {
> stqe_next = 0xc032fa50}, w_children = 0x0, w_file = 0x0, w_line = 0,
> w_level = 0, w_refcount = 2, w_Giant_squawked = 0 '\0',
> w_other_squawked = 0 '\0', w_same_squawked = 0 '\0'}
>
> This is the instruction where the page fault occurred. As to how w_name
> was clobbered, I have no idea.
Your 3rd party registered a lock somehow? Does it do mtx_init() and not
do mtx_destroy() when being unloaded?
--
John Baldwin <[EMAIL PROTECTED]> <>< http://www.FreeBSD.org/~jhb/
"Power Users Use the Power to Serve!" - http://www.FreeBSD.org/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
