Date: Tue, 08 Jan 2008 23:26:22 +0200 From: Toomas Aas <toomas.aas@raad.tartu.ee> To: Kris Kennaway <kris@FreeBSD.org> Cc: freebsd-stable@freebsd.org, Wayne Sierke <ws@au.dyndns.ws> Subject: Re: 6.3-PRERELEASE desktop system periodically freezes momentarily Message-ID: <4783EA7E.1050008@raad.tartu.ee> In-Reply-To: <4783DCAA.1080108@FreeBSD.org> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
Kris Kennaway wrote: > OK, you may need to set up hwpmc or LOCK_PROFILING to figure out what > your system is doing at that moment. I set up a kernel with hwpmc support, but am feeling a bit (to put it mildly) lost, since I haven't really done anything with hwpmc ever before. I was hoping to maybe figure out whether this freezing is caused by some device interrupt, so I tried: # pmcstat -S interrupts -o /tmp/sample.txt But all I get is this: pmcstat: ERROR: Cannot allocate system-mode pmc with specification "interrupts": Invalid argument Yet "interrupts" is listed in pmc(3). I'm sure I'm making some ridiculous error. Having now revealed my ignorance, I go to sleep(1). -- Toomas Aas ... How can i miss you if you won't go away?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4783EA7E.1050008>