From owner-freebsd-bugs  Tue Mar  4 01:05:38 1997
Return-Path: <owner-bugs>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id BAA08010
          for bugs-outgoing; Tue, 4 Mar 1997 01:05:38 -0800 (PST)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA08005
          for <bugs@freebsd.org>; Tue, 4 Mar 1997 01:05:34 -0800 (PST)
Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.3/8.6.9) id UAA01832 for bugs@freebsd.org; Tue, 4 Mar 1997 20:01:11 +1100
Date: Tue, 4 Mar 1997 20:01:11 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199703040901.UAA01832@godzilla.zeta.org.au>
To: bugs@freebsd.org
Subject: statclock stopped
Sender: owner-bugs@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

The statclock stopped on one of my systems after running for 19 days.
I fixed it by running a `show rtc' command in ddb.  This happens to
read the clock status register, which is the normal way to keep the
clock interrupting.  The status register had the unusual value 0xf0
in it.  0xd0 is normal.  0x20 is `alarm intr'.

Bruce