From owner-freebsd-stable@FreeBSD.ORG  Mon Jun 30 13:56:33 2003
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 8D1BB37B401
	for <stable@freebsd.org>; Mon, 30 Jun 2003 13:56:33 -0700 (PDT)
Received: from segfault.kiev.ua (segfault.kiev.ua [193.193.193.4])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 644F643FBF
	for <stable@freebsd.org>; Mon, 30 Jun 2003 13:56:29 -0700 (PDT)
	(envelope-from netch@iv.nn.kiev.ua)
Received: (from uucp@localhost)
	by segfault.kiev.ua (8) with UUCP id h6UKuPXC081851;
	Mon, 30 Jun 2003 23:56:25 +0300 (EEST)
	(envelope-from netch@iv.nn.kiev.ua)
Received: (from netch@localhost)
	by iv.nn.kiev.ua (8.12.8p1/8.12.8) id h5UKov7c002437;
	Mon, 30 Jun 2003 23:50:57 +0300 (EEST)
	(envelope-from netch)
Date: Mon, 30 Jun 2003 23:50:57 +0300
From: Valentin Nechayev <netch@iv.nn.kiev.ua>
To: Stijn Hoop <stijn@win.tue.nl>
Message-ID: <20030630205057.GA2249@iv.nn.kiev.ua>
References: <20030627115208.GC90536@pcwin002.win.tue.nl>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20030627115208.GC90536@pcwin002.win.tue.nl>
X-42: On
Organization: Dark side of coredump
cc: stable@freebsd.org
Subject: Re: alternate system clock has died
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Production branch of FreeBSD source code
	<freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 30 Jun 2003 20:56:33 -0000

 Fri, Jun 27, 2003 at 13:52:08, stijn (Stijn Hoop) wrote about "alternate system clock has died": 

SH> I'm getting the message in the subject when I run systat -vm on a lightly
SH> loaded server. Top shows interesting CPU usage %:
SH> CPU states:  0.0% user,  0.0% nice,  0.0% system,  0.0% interrupt,  0.0% idle

See LINT:

# Notes on APM
#  The flags takes the following meaning for apm0:
#    0x0020  Statclock is broken.
#  If apm is omitted, some systems require sysctl -w kern.timecounter.method=1
#  for correct timekeeping.

This is possibly the first thing should be done seeing dead statclock.
It was actual for SMP motherboards based on 440BX and similar chipsets.

> Could this have to do
> with the battery-backed CMOS clock?

Yes, statclock is RTC interrupts, but even if battery is dead, interrupts
should work.


-netch-