From owner-freebsd-stable@FreeBSD.ORG Sun Jan 13 01:29: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 3135F16A417 for ; Sun, 13 Jan 2008 01:29:30 +0000 (UTC) (envelope-from dg@dglawrence.com) Received: from dglawrence.com (static-72-90-113-2.ptldor.fios.verizon.net [72.90.113.2]) by mx1.freebsd.org (Postfix) with ESMTP id 0D47313C468 for ; Sun, 13 Jan 2008 01:29:29 +0000 (UTC) (envelope-from dg@dglawrence.com) Received: from tnn.dglawrence.com (localhost [127.0.0.1]) by dglawrence.com (8.14.1/8.14.1) with ESMTP id m0D1TT9n073243; Sat, 12 Jan 2008 17:29:29 -0800 (PST) (envelope-from dg@dglawrence.com) Received: (from dg@localhost) by tnn.dglawrence.com (8.14.1/8.14.1/Submit) id m0D1TQJX073242; Sat, 12 Jan 2008 17:29:26 -0800 (PST) (envelope-from dg@dglawrence.com) X-Authentication-Warning: tnn.dglawrence.com: dg set sender to dg@dglawrence.com using -f Date: Sat, 12 Jan 2008 17:29:26 -0800 From: David G Lawrence To: "J.R. Oldroyd" Message-ID: <20080113012926.GC39994@tnn.dglawrence.com> References: <4783DB72.6030605@raad.tartu.ee> <4783DCAA.1080108@FreeBSD.org> <4783EA7E.1050008@raad.tartu.ee> <4783ED15.1060606@FreeBSD.org> <20080109141859.74d08743@linwhf.opal.com> <478522B5.5030101@FreeBSD.org> <20080109235819.7707133d@linwhf.opal.com> <4785C9FC.4090102@FreeBSD.org> <20080111124929.4aed2471@linwhf.opal.com> <20080112123053.164b5a5c@linwhf.opal.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080112123053.164b5a5c@linwhf.opal.com> X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0 (dglawrence.com [127.0.0.1]); Sat, 12 Jan 2008 17:29:29 -0800 (PST) Cc: freebsd-stable@freebsd.org Subject: Re: RELENG_7 2008/01/10 desktop system also periodically freezes 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: Sun, 13 Jan 2008 01:29:30 -0000 > On Fri, 11 Jan 2008 12:49:29 -0500, I wrote: > > > > I have yet to experience a "random" freeze not directly attributable > > to a softupdate while running the lock profiling. I am running with > > lock profiling on, and resetting the profiling counters once a minute. > > Yesterday and this morning, I've run for quite a while now with lock > > profiling on but without a "random" freeze. I'll wait some more, but > > I'm hoping that enabling the lock profiling hasn't masked the freeze. > > I'll post again when I see one.. > > > > It is looking more likely to me that enabling lock profiling does mask > the freeze. I ran for more than 10 hours yesterday with lock profiling > enabled and did not observe a single freeze. After about 7 hours, I > stopped the lock profiling and within 20 mins or so, I experienced a > NINE MINUTE freeze!! On re-enabling the lock profiling, I ran for about > 3 more hours with no further freezes. > > At the time of that long freeze, all I was doing was typing an email > message. The load average was almost 0. Mail client is claws-email. > Also running but idle were firefox, ical, several xterms, fvwm & its > children (Fvwm{Buttons,Event,Pager,IconMan}), xload and xclock. And > xorg which uses the xf86-video-intel driver. Daemons running were > wpa_supplicant, dhclient, devd, syslogd, cupsd, ntpd, powerd, sshd, > sendmail, cron, moused and xdm. That is all. You might want to try disabling powerd and see if that mitigates the problem. powerd is going to be messing with the CPU clock when it is near idle. Your system would be less idle with lock profiling enabled, which might explain why the problem seems to happen less often in that case. -DG David G. Lawrence President Download Technologies, Inc. - http://www.downloadtech.com - (866) 399 8500 The FreeBSD Project - http://www.freebsd.org Pave the road of life with opportunities.