From owner-freebsd-bugs  Wed Oct 30 06:40:05 1996
Return-Path: owner-bugs
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id GAA01036
          for bugs-outgoing; Wed, 30 Oct 1996 06:40:05 -0800 (PST)
Received: (from gnats@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id GAA01029;
          Wed, 30 Oct 1996 06:40:03 -0800 (PST)
Date: Wed, 30 Oct 1996 06:40:03 -0800 (PST)
Message-Id: <199610301440.GAA01029@freefall.freebsd.org>
To: freebsd-bugs
Cc: 
From: Tor Egge <Tor.Egge@idt.ntnu.no>
Subject: Re: bin/1927: User CPU time getting accounting as system time
Reply-To: Tor Egge <Tor.Egge@idt.ntnu.no>
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: Tor Egge <Tor.Egge@idt.ntnu.no>
To: markd@grizzly.com
Cc: FreeBSD-gnats-submit@freebsd.org
Subject: Re: bin/1927: User CPU time getting accounting as system time
Date: Wed, 30 Oct 1996 15:29:02 +0100

 > 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.
 
 - Tor Egge