From owner-freebsd-hackers  Sat Dec  7 01:31:19 1996
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.4/8.8.4) id BAA18071
          for hackers-outgoing; Sat, 7 Dec 1996 01:31:19 -0800 (PST)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19])
          by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id BAA18066
          for <hackers@FreeBSD.org>; Sat, 7 Dec 1996 01:31:14 -0800 (PST)
Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.3/8.6.9) id UAA21725; Sat, 7 Dec 1996 20:26:07 +1100
Date: Sat, 7 Dec 1996 20:26:07 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199612070926.UAA21725@godzilla.zeta.org.au>
To: hackers@FreeBSD.org, marcs@znep.com
Subject: Re: The alternate system clock has died!
Cc: skafte@worldgate.com
Sender: owner-hackers@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

>"The alternate system clock has died!".  I remember talk of this problem
>
>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?

Not resolved.  It stops scheduling from working fairly.  The statistics
clock is used for scheduling, for division of process time into
real/user/sys and for profiling type things.

Kicking the clock by setting the kernel variable `ipending' to 0x100
will probably restart it.

Bruce