From owner-freebsd-hackers Fri Dec 6 15:48:37 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id PAA18775 for hackers-outgoing; Fri, 6 Dec 1996 15:48:37 -0800 (PST) Received: from scanner.worldgate.com (scanner.worldgate.com [198.161.84.3]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id PAA18770 for ; Fri, 6 Dec 1996 15:48:34 -0800 (PST) Received: from znep.com (uucp@localhost) by scanner.worldgate.com (8.7.5/8.7.3) with UUCP id QAA27908; Fri, 6 Dec 1996 16:48:33 -0700 (MST) Received: from localhost (marcs@localhost) by alive.ampr.ab.ca (8.7.5/8.7.3) with SMTP id QAA20725; Fri, 6 Dec 1996 16:46:52 -0700 (MST) Date: Fri, 6 Dec 1996 16:46:51 -0700 (MST) From: Marc Slemko X-Sender: marcs@alive.ampr.ab.ca To: hackers@freebsd.org cc: Greg Skafte Subject: The alternate system clock has died! Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk We are seeing a system that occasionally gets into a state where things like top, vmstat, etc. give odd numbers. systat will give the message "The alternate system clock has died!". I remember talk of this problem before on the lists, but can't find it since the search engine at www.freebsd.org seems to be down. (anyone know where a plain-text ftpable copy of the list archives is?) Was this issue ever resolved? Does it cause any more serious problems? It looks like cp_time stops getting updated; would I be right to guess that cp_time is just an alternate clock used only for profiling type things? The server is running -stable, so I wouldn't be too suprised if it has been fixed in -current.