From owner-freebsd-bugs  Fri Nov  1 04:00:06 1996
Return-Path: owner-bugs
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id EAA22071
          for bugs-outgoing; Fri, 1 Nov 1996 04:00:06 -0800 (PST)
Received: (from gnats@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id EAA22033;
          Fri, 1 Nov 1996 04:00:03 -0800 (PST)
Date: Fri, 1 Nov 1996 04:00:03 -0800 (PST)
Message-Id: <199611011200.EAA22033@freefall.freebsd.org>
To: freebsd-bugs
Cc: 
From: Bruce Evans <bde@zeta.org.au>
Subject: Re: bin/1927: User CPU time getting accounting as system time
Reply-To: Bruce Evans <bde@zeta.org.au>
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: Bruce Evans <bde@zeta.org.au>
To: markd@Grizzly.COM, Tor.Egge@idt.ntnu.no
Cc: bde@zeta.org.au, FreeBSD-gnats-submit@FreeBSD.ORG
Subject: Re: bin/1927: User CPU time getting accounting as system time
Date: Fri, 1 Nov 1996 22:48:43 +1100

 >>> 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.
 >
 >Although user time appears to be working, the above returns
 >
 >interrupt      total      rate
 >clk0 irq0     4836779      100
 >rtc0 irq8     6191284      128
 
 The rtc seems to be working too.
 
 >Which module you you suggest?
 
 One you write :-).  (Copy an example module and add the above line to it.)
 
 Bruce