Date: Thu, 10 Jan 2008 21:27:25 +0100 From: Kris Kennaway <kris@FreeBSD.org> To: Toomas Aas <toomas.aas@raad.tartu.ee> Cc: freebsd-stable@freebsd.org, Wayne Sierke <ws@au.dyndns.ws> Subject: Re: 6.3-PRERELEASE desktop system periodically freezes momentarily Message-ID: <47867FAD.9050701@FreeBSD.org> In-Reply-To: <47866B15.5070002@raad.tartu.ee> References: <1199812249.96494.133.camel@predator-ii.buffyverse> <4783C8A8.2090705@raad.tartu.ee> <4783D41B.3000204@FreeBSD.org> <4783D748.1050401@raad.tartu.ee> <4783D824.1050502@FreeBSD.org> <4783DB72.6030605@raad.tartu.ee> <4783DCAA.1080108@FreeBSD.org> <47851247.1020306@raad.tartu.ee> <4785186E.4070609@FreeBSD.org> <47852EFF.8000103@raad.tartu.ee> <478530FC.8090701@FreeBSD.org> <478531C4.10909@raad.tartu.ee> <4785334F.205@FreeBSD.org> <47866B15.5070002@raad.tartu.ee>
next in thread | previous in thread | raw e-mail | index | archive | help
Toomas Aas wrote: > Kris Kennaway wrote: > >> OK. Can you obtain a lock profiling dump? > > I'm trying, but not succeeding so far. I added the following to the > kernel config: > > options MUTEX_PROFILING > options MPROF_BUFFERS="1536" > options MPROF_HASH_SIZE="1543" > > And set debug.mutex.prof.enable=1 > > However, kgmon says that profiling is not enabled in the kernel. Am I > missing something essential or barking under completely wrong tree? > > > > Yes :) kgmon has nothing to do with mutex profiling, so remove the MPROF_*. sysctl debug.mutex.prof.enable=1 ... trigger hang ... sysctl debug.mutex.prof.enable=0 and send me the output of sysctl debug.mutex.prof.stats Kris
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?47867FAD.9050701>