From owner-freebsd-current@FreeBSD.ORG  Tue Jun 22 11:09:26 2004
Return-Path: <owner-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 32FF616A4CE; Tue, 22 Jun 2004 11:09:26 +0000 (GMT)
Received: from deliver.epitech.net (deliver.epitech.net [163.5.0.25])
	by mx1.FreeBSD.org (Postfix) with SMTP
	id 677D443D1D; Tue, 22 Jun 2004 11:09:25 +0000 (GMT)
	(envelope-from le-hen_j@epita.fr)
Received: from epita.fr ([10.42.1.60])
 by deliver.epitech.net (SAVSMTP 3.1.2.35) with SMTP id M2004062213041108567
 ; Tue, 22 Jun 2004 13:04:11 +0200
Received: from rocco (rocco.epita.fr [10.42.14.9])
	by epita.fr id i5MB9Ml21971
	Tue, 22 Jun 2004 13:09:22 +0200 (CEST)
Date: Tue, 22 Jun 2004 13:09:21 +0200
From: Jeremie Le Hen <jeremie.le-hen@epita.fr>
To: freebsd-current@freebsd.org
Message-ID: <20040622110921.GA9281@rocco.epita.fr>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.4i
cc: freebsd-mobile@freebsd.org
Subject: 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
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Jun 2004 11:09:26 -0000

Hi,

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 ?

(I'm not a kernel nor hardware guru, so I may have forget to give
revelant informations.  Please ask me if you want more informations.)

Regards,
-- 
Jeremie LE HEN aka TtZ/TataZ                          jeremie.le-hen@epita.fr
                                                                 ttz@epita.fr
Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread!