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 _______________________________________________ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
