From owner-freebsd-stable@FreeBSD.ORG Tue Jan 8 21:26:30 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3C2EE16A417; Tue, 8 Jan 2008 21:26:30 +0000 (UTC) (envelope-from toomas.aas@raad.tartu.ee) Received: from smtp-out.neti.ee (smtp-out.neti.ee [194.126.126.40]) by mx1.freebsd.org (Postfix) with ESMTP id EE50413C447; Tue, 8 Jan 2008 21:26:29 +0000 (UTC) (envelope-from toomas.aas@raad.tartu.ee) Received: from localhost (localhost [127.0.0.1]) by MXR-5.estpak.ee (Postfix) with ESMTP id 5761615DFA1; Tue, 8 Jan 2008 23:26:28 +0200 (EET) X-Virus-Scanned: Debian amavisd-new at estpak.ee Received: from smtp-out.neti.ee ([127.0.0.1]) by localhost (MXR-5.estpak.ee [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ycl07mgdqghl; Tue, 8 Jan 2008 23:26:23 +0200 (EET) Received: from Relayhost1.neti.ee (Relayhost1 [88.196.174.141]) by MXR-5.estpak.ee (Postfix) with ESMTP id 840A715E2F1; Tue, 8 Jan 2008 23:26:23 +0200 (EET) Received: from originaal.kodu.lan (88-196-109-8-dsl.trt.estpak.ee [88.196.109.8]) by Relayhost1.neti.ee (Postfix) with ESMTP id 14C8D29DA54; Tue, 8 Jan 2008 23:26:22 +0200 (EET) Message-ID: <4783EA7E.1050008@raad.tartu.ee> Date: Tue, 08 Jan 2008 23:26:22 +0200 From: Toomas Aas User-Agent: Thunderbird 2.0.0.9 (X11/20071121) MIME-Version: 1.0 To: Kris Kennaway 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> In-Reply-To: <4783DCAA.1080108@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org, Wayne Sierke Subject: Re: 6.3-PRERELEASE desktop system periodically freezes momentarily X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Jan 2008 21:26:30 -0000 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?