From owner-freebsd-bugs Wed Apr 9 13:20:03 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id NAA14534 for bugs-outgoing; Wed, 9 Apr 1997 13:20:03 -0700 (PDT) Received: from spinner.DIALix.COM (root@spinner.dialix.com [192.203.228.67]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA14477; Wed, 9 Apr 1997 13:19:55 -0700 (PDT) Received: from spinner.DIALix.COM (peter@localhost.DIALix.oz.au [127.0.0.1]) by spinner.DIALix.COM (8.8.5/8.8.5) with ESMTP id EAA21495; Thu, 10 Apr 1997 04:19:51 +0800 (WST) Message-Id: <199704092019.EAA21495@spinner.DIALix.COM> X-Mailer: exmh version 2.0gamma 1/27/96 To: Mike Pritchard cc: jari@apeli.tky.hut.fi, freebsd-bugs@freefall.freebsd.org, freebsd-gnats-submit@freebsd.org Subject: Re: bin/3241 In-reply-to: Your message of "Wed, 09 Apr 1997 12:30:21 MST." <199704091930.MAA10872@freefall.freebsd.org> Date: Thu, 10 Apr 1997 04:19:50 +0800 From: Peter Wemm Sender: owner-bugs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk 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