From owner-freebsd-current@FreeBSD.ORG Tue Jun 22 15:21:12 2004 Return-Path: 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 0E12416A4CE; Tue, 22 Jun 2004 15:21:12 +0000 (GMT) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id BBEA943D5D; Tue, 22 Jun 2004 15:21:11 +0000 (GMT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.12.10/8.12.10) id i5MFL6Hv079446; Tue, 22 Jun 2004 10:21:06 -0500 (CDT) (envelope-from dan) Date: Tue, 22 Jun 2004 10:21:05 -0500 From: Dan Nelson To: Jeremie Le Hen Message-ID: <20040622152105.GG86471@dan.emsphone.com> References: <20040622110921.GA9281@rocco.epita.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040622110921.GA9281@rocco.epita.fr> X-OS: FreeBSD 5.2-CURRENT X-message-flag: Outlook Error User-Agent: Mutt/1.5.6i cc: freebsd-current@freebsd.org cc: freebsd-mobile@freebsd.org Subject: Re: Weird rtc interrupt rate X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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: Tue, 22 Jun 2004 15:21:12 -0000 In the last episode (Jun 22), Jeremie Le Hen said: > I have a Dell Latitude CPx laptop running FreeBSD 5.2-CURRENT. I > have been using FreeBSD on this laptop for a long time, and the > problem I'm going to describe also happened while it was running > 4.6-STABLE. > > Sometimes, when wathing at my processes using top(1), all CPU states > are 0.00. Since ps(1) shows the same behaviour, this is not a bug in > top(1). But when this problem happens (this seems to be completly > random), vmstat(8) shows a weird interrupt rate for rtc : > > # z6po:root# vmstat -i | sed -n '1p; /rtc/p;' > # interrupt total rate > # irq8: rtc 7584528 115 > > or, two hours later, while the computer was 100% idle : > > # z6po:tataz$ vmstat -i | sed -n '1p; /rtc/p;' > # interrupt total rate > # irq8: rtc 7584528 101 > > AFAIK, rtc interrupts rate should be something like 127 or 128. What > could make the rate being so unstable ? It's not unstable; it just stopped completely and the average is slowly falling. I had this happen to one of my servers a few weeks ago as well. You can determine exactly when it stopped by counting 7584528/128 ~= 59254 seconds forward from the time your system booted. Mine died after about a week of uptime, and I didn't see anything interesting in the logs. A reboot fixed it. -- Dan Nelson dnelson@allantgroup.com