From owner-freebsd-bugs  Wed Apr  9 13:30:03 1997
Return-Path: <owner-bugs>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id NAA15510
          for bugs-outgoing; Wed, 9 Apr 1997 13:30:03 -0700 (PDT)
Received: (from gnats@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id NAA15504;
          Wed, 9 Apr 1997 13:30:01 -0700 (PDT)
Date: Wed, 9 Apr 1997 13:30:01 -0700 (PDT)
Message-Id: <199704092030.NAA15504@freefall.freebsd.org>
To: freebsd-bugs
Cc: 
From: Peter Wemm <peter@spinner.DIALix.COM>
Subject: Re: bin/3241 
Reply-To: Peter Wemm <peter@spinner.DIALix.COM>
Sender: owner-bugs@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

The following reply was made to PR bin/3241; it has been noted by GNATS.

From: Peter Wemm <peter@spinner.DIALix.COM>
To: Mike Pritchard <mpp@freefall.freebsd.org>
Cc: jari@apeli.tky.hut.fi, freebsd-bugs@freefall.freebsd.org,
        freebsd-gnats-submit@freebsd.org
Subject: Re: bin/3241 
Date: Thu, 10 Apr 1997 04:19:50 +0800

 Mike Pritchard wrote:
 > Synopsis: times(3) returns only stime
 > 
 > The test program works correctly under 2.1.7 and 3.0-current.
 > I don't have a 2.2 system to test this on, so I can't verify
 > that it fails to work under 2.2 as reported in the PR.
 
 Most likely this was because the statclock got stalled.  This has been 
 recently fixed in -current.  A good way to test for this is to run "systat 
 -vmstat 1" and see if it says that "the alternate system clock has died".  
 If so, you should schedule a reboot since the process scheduler is 
 adversely affected.  Alternatively, if you have DDB loaded in the kernel, 
 you might try entering ddb, running the "show rtc" command, and exiting 
 with "c" (continue).  That might be enough to restart it.
 
 Cheers,
 -Peter