From owner-freebsd-bugs  Wed Nov 15 21:59:04 1995
Return-Path: owner-bugs
Received: (from root@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id VAA24158
          for bugs-outgoing; Wed, 15 Nov 1995 21:59:04 -0800
Received: from bunyip.cc.uq.oz.au (pp@bunyip.cc.uq.oz.au [130.102.2.1])
          by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id VAA24139
          for <bugs@freebsd.org>; Wed, 15 Nov 1995 21:58:56 -0800
Received: from cc.uq.oz.au by bunyip.cc.uq.oz.au 
          id <26499-0@bunyip.cc.uq.oz.au>; Thu, 16 Nov 1995 15:55:20 +1000
Received: from netfl15a.devetir.qld.gov.au 
          by pandora.devetir.qld.gov.au (8.6.10/DEVETIR-E0.3a) with ESMTP 
          id PAA24099 for <bugs@freebsd.org>; Thu, 16 Nov 1995 15:00:27 +1000
Received: from localhost by netfl15a.devetir.qld.gov.au (8.6.8.1/DEVETIR-0.1) 
          id EAA23381 for <bugs@freebsd.org>; Thu, 16 Nov 1995 04:59:21 GMT
Message-Id: <199511160459.EAA23381@netfl15a.devetir.qld.gov.au>
X-Mailer: exmh version 1.6.4 10/10/95
To: bugs@freebsd.org
Subject: Heavy paging buggers secondary system clock
X-Face: 3}heU+2?b->-GSF-G4T4>jEB9~FR(V9lo&o>kAy=Pj&;oVOc<|pr%I/VSG"ZD32J>5gGC0N 
        7gj]^GI@M:LlqNd]|(2OxOxy@$6@/!,";-!OlucF^=jq8s57$%qXd/ieC8DhWmIy@J1AcnvSGV\|*! 
        >Bvu7+0h4zCY^]{AxXKsDTlgA2m]fX$W@'8ev-Qi+-;%L'CcZ'NBL!@n?}q!M&Em3*eW7,093nOeV8 
        M)(u+6D;%B7j\XA/9j4!Gj~&jYzflG[#)E9sI&Xe9~y~Gn%fA7>F:YKr"Wx4cZU*6{^2ocZ!YyR
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Thu, 16 Nov 1995 14:59:19 +1000
From: Stephen Hocking <sysseh@devetir.qld.gov.au>
Sender: owner-bugs@freebsd.org
Precedence: bulk

When my 8Mb machine is paging heaving (a fistful of xterms, AUIS ez, exmh & a 
make world) running systat will at some time (after a few hours, it happened 
in the middle of the night) systat -vmstat will revert to the pigs display, 
with the message "The alternate system clock has died!". After this has 
happened, it will always happen. Top will also then die with a FP error (div 
by 0) after this point. This (systat & top) continues until the system is 
rebooted. I think this is also responsible for some of my NAS problems (which 
depends on itimer to clock the sound flow) during times of heavy system load.


	Stephen
-- 

        I do not speak for the Worker's Compensation Board of Queensland -
                     They don't pay me enough for that!