Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/3/84; site delftcc.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!allegra!mit-eddie!genrad!decvax!decwrl!pyramid!pesnta!phri!delftcc!sam
From: sam@delftcc.UUCP (Sam Kendall)
Newsgroups: net.bugs.v7,net.unix-wizards
Subject: Codata (V7): strange memory faults crash the system
Message-ID: <113@delftcc.UUCP>
Date: Tue, 10-Dec-85 02:56:56 EST
Article-I.D.: delftcc.113
Posted: Tue Dec 10 02:56:56 1985
Date-Received: Thu, 12-Dec-85 05:25:21 EST
Organization: Delft Consulting Corp., New York
Lines: 23
Keywords: Codata
Xref: watmath net.bugs.v7:224 net.unix-wizards:16064

The problem: periodically (lately once or twice a day) the system
decides that there should be lots of memory faults.  Most commands you
type die horrible deaths; eventually your shell dies and you are gone.
Likewise for the other users.  The only solution is to reboot.

The system: Codata 3300 (a 68000 box) running Unisis 3.1.1 (Codata's
UniSoft V7).  Lots of serial I/O (netnews, 2 modems), disks (3 Atasis,
each with several ~10 MB filesystems; and we are frozen forever at 52
system disk buffers, no more), and load (netnews, some large interactive
programs).  All three of these factors have increased recently.  We have
1.3MB of RAM and rarely swap.

Has anyone seen something like this on a Codata, on a UniSoft V7 system,
or on any V7 system?  Maybe some inconsistency in the memory management
(?).  If it were something simple, like this happens iff processes start
swapping--but that doesn't seem to be it.  Any solutions for a
binary-only machine, with no new system releases expected ever?

----
Sam Kendall			     allegra \
Delft Consulting Corp.		seismo!cmcl2  ! delftcc!sam
(212) 243-8700			       ihnp4 /
ARPA: delftcc!sam@nyu.ARPA or @nyu-cmcl2.ARPA