From owner-freebsd-current@FreeBSD.ORG Wed May 31 00:03:11 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 154D516B22F for ; Wed, 31 May 2006 00:03:11 +0000 (UTC) (envelope-from rnsanchez@gmail.com) Received: from wx-out-0102.google.com (wx-out-0102.google.com [66.249.82.192]) by mx1.FreeBSD.org (Postfix) with ESMTP id 79BDA43D72 for ; Wed, 31 May 2006 00:03:04 +0000 (GMT) (envelope-from rnsanchez@gmail.com) Received: by wx-out-0102.google.com with SMTP id i31so364548wxd for ; Tue, 30 May 2006 17:03:03 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=i6H4wz1OIEskytVa7q6JLp+XpfbHrlinXHUPjQptvNlyaYE0GC5RbQaf0HcQhc6nBG1ZFjOPaa+DNM8ecDDrFpQgNE7ORCr8E2+hnFE6ya378OTAneOv2AgS1FkjZYpl1aYM0WmsKV3EfrxQAeu5CYZE8oQoJVpq5sdrxUSlG5Q= Received: by 10.70.54.11 with SMTP id c11mr4218099wxa; Tue, 30 May 2006 17:03:03 -0700 (PDT) Received: by 10.70.65.17 with HTTP; Tue, 30 May 2006 17:02:53 -0700 (PDT) Message-ID: <52b3de6f0605301702x6627846ap89c8b3ac3cc29cb4@mail.gmail.com> Date: Tue, 30 May 2006 21:02:53 -0300 From: "Ricardo Nabinger Sanchez" To: freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: weird swi4:clock misbehavior after fire saver goes in X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 May 2006 00:03:16 -0000 Hello, After upgrading a somewhat low-end machine to -CURRENT, I noticed a misbehavior of a system thread, "swi4: clock". What happens: after some time, its cpu usage went from ~0.1% to ~62%, without reducing afterwards (in case it was just a peak usage) until rebooting. In a first moment, I thought this was due to something related to "make buildworld" or "portupgrade -a" (which could last for 4 days if there are *many* fat ports to update, like firefox), but this morning the system thread gone crazy without anything happening in the system -- except for the fire saver. When in 5-STABLE or 6-STABLE it went "only" up to ~20% of cpu usage. The machine is up for 9 hours, I did lots of compilations and plenty of network traffic, and the 'swi4: clock' thread is behaving nicely (0.00 to 0.2% of cpu usage). I configured the machine to not enable the screensaver. I'm not completely sure, but I don't remember this behavior happening if there was a X session running with the terminal "pointing" to it, instead of a tty. Details about the machine: rnsanchez@camelo:~% uname -a FreeBSD camelo.lan.box 7.0-CURRENT FreeBSD 7.0-CURRENT #1: Fri May 26 17:29:30 BRT 2006 root@camelo.lan.box:/home/cvsup/obj/home/cvsup/src/sys/CAMELO i386 kernconf pciconf -lv dmesg sysctl -a I'd be glad to provide additional information, just tell me what you need :) Regards, and thanks in advance. -- Ricardo Nabinger Sanchez GNU/Linux #140696 [http://counter.li.org] Slackware Linux + FreeBSD