From owner-freebsd-bugs  Wed Oct 30 07:40:07 1996
Return-Path: owner-bugs
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id HAA13808
          for bugs-outgoing; Wed, 30 Oct 1996 07:40:07 -0800 (PST)
Received: (from gnats@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id HAA13769;
          Wed, 30 Oct 1996 07:40:03 -0800 (PST)
Date: Wed, 30 Oct 1996 07:40:03 -0800 (PST)
Message-Id: <199610301540.HAA13769@freefall.freebsd.org>
To: freebsd-bugs
Cc: 
From: Peter Wemm <peter@spinner.DIALix.COM>
Subject: Re: bin/1927: User CPU time getting accounting as system time 
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/1927; it has been noted by GNATS.

From: Peter Wemm <peter@spinner.DIALix.COM>
To: Tor Egge <Tor.Egge@idt.ntnu.no>
Cc: freebsd-gnats-submit@freefall.freebsd.org
Subject: Re: bin/1927: User CPU time getting accounting as system time 
Date: Wed, 30 Oct 1996 23:35:43 +0800

 Tor Egge wrote:
 >> I ran an CPU intensive job, timing it with /usr/bin/time and the result 
 was
 >>      2097.84 real         0.00 user      2013.06 sys
 >  
 >Try "vmstat -i; sleep 2; vmstat -i" to see if RTC interrupts are still
 >being generated. If not, you may load an lkm that performs an
 >"rtcin(RTC_INTR)" call to restart the RTC interrupt.
 
 This shows up rather dramatically on "systat -vmstat".  It loudly yells 
 "The alternate system clock has died!" and switches elsewhere.
 
 Hmm, It's interesting that systat has got special case code to detect 
 this....
 
 Is it really that expensive to do a simple watchdog for this event?
 
 >  - Tor Egge
 
 Cheers,
 -Peter