Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 26 Feb 2009 16:48:32 -0500
From:      John Baldwin <jhb@freebsd.org>
To:        Guy Helmer <ghelmer@palisadesys.com>
Cc:        freebsd-stable@freebsd.org
Subject:   Re: 7.1 hangs in cache_lookup mutex?
Message-ID:  <200902261648.32845.jhb@freebsd.org>
In-Reply-To: <49A70807.9020600@palisadesys.com>
References:  <49A46AB4.3080003@palisadesys.com> <200902261012.24325.jhb@freebsd.org> <49A70807.9020600@palisadesys.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Thursday 26 February 2009 4:22:15 pm Guy Helmer wrote:
> db> show sleepchain 23110
> thread 100181 (pid 23110, vmstat) blocked on sx "user map" XLOCK
> thread 100208 (pid 23092, kvoop) is on a run queue
> db> show sleepchain 23092
> thread 100208 (pid 23092, kvoop) is on a run queue

Ah, so this is normal (well, mostly) in that kvoop is simply on the run queue 
waiting for a CPU.  Can you find the thread pointer for kvoop and check on 
things such as if it is pinned and if so to which CPU (td_pinned will tell 
you the first, and td_sched->ts_cpu will tell you the second with ULE).

Then you will want to see what is running on that CPU.  You might want to 
check your other coredump and find the td_state member of the thread for 
kvoop there as well.

-- 
John Baldwin



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200902261648.32845.jhb>