Unkillable KSE threaded proc
John Baldwin
jhb at FreeBSD.org
Thu Sep 9 12:26:29 PDT 2004
On Thursday 09 September 2004 03:08 pm, Julian Elischer wrote:
> >I'm following it from 0xc1a22540 for today's lockup:
> >
> >(kgdb) p $proc->p_mtx
> >$3 = {
> > mtx_object = {
> > lo_class = 0xc069e55c,
> > lo_name = 0xc067788d "process lock",
> > lo_type = 0xc067788d "process lock",
> > lo_flags = 0x430000,
> > lo_list = {
> > tqe_next = 0x0,
> > tqe_prev = 0x0
> > },
> > lo_witness = 0x0
> > },
> > mtx_lock = 0xc1b617d2,
> > mtx_recurse = 0x0
> >}
> >
> >
> >0xc1b617d2 is almost the same as the thread id of the
> >first thread (0xc1b617d0)..
That means it has a flag set, 2 = MTX_CONTESTED meaning that it is a contested
lock. 0xc1b617d0 is the thread that owns the lock.
--
John Baldwin <jhb at FreeBSD.org> <>< http://www.FreeBSD.org/~jhb/
"Power Users Use the Power to Serve" = http://www.FreeBSD.org
More information about the freebsd-threads
mailing list