From owner-freebsd-bugs  Thu Jan  4 09:00:23 1996
Return-Path: owner-bugs
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id JAA16195
          for bugs-outgoing; Thu, 4 Jan 1996 09:00:23 -0800 (PST)
Received: from mail.mks.com (mks-gate.mks.com [142.77.7.224])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id JAA16190
          for <freebsd-bugs@freebsd.org>; Thu, 4 Jan 1996 09:00:16 -0800 (PST)
Received: from mks.com (giga.mks.com [1.0.0.51])
	by mail.mks.com (8.6.8.1/DEKA-950919b) with SMTP id LAA02039
	for <freebsd-bugs@freebsd.org>; Thu, 4 Jan 1996 11:49:10 -0500
Received: from worf by mks.com (4.1/GIGA-950913a)
	id AA10174; Thu, 4 Jan 96 11:49:08 EST
To: freebsd-bugs@freebsd.org
Subject: Re: kern/921: 
Date: Thu, 04 Jan 1996 11:49:05 -0500
Message-Id: <6222.820774145@worf.mks.com>
From: "David J. Fiander" <davidf@mks.com>
Sender: owner-bugs@freebsd.org
Precedence: bulk

Well, it turns out that my hypothesis that the failure of
getrusage() is related uptime is wrong.  My machine managed to
last much long without breaking, but now, after only 2 hours up,
it's broken.  It seems that it's related to load.

Running X-Windows, a kernel compile, and view a few large images
with xv has, once again, caused getrusage() to fail.

And fixing calcru() so that it properly uses quad_t arithmetic
for the intermediate calculations, to avoid overflow, didn't
solve the problem either.

- David