Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!cs.utexas.edu!tut.cis.ohio-state.edu!ucbvax!ulysses!wmb
From: wmb@ulysses.att.com (W M Brelsford)
Newsgroups: comp.sys.att
Subject: Re: 3B2 crashes mysteriously
Summary: Caused by attempted TCP/IP connections to down machines?
Message-ID: <13933@ulysses.att.com>
Date: 23 Oct 90 12:17:21 GMT
References: <15406@hydra.gatech.EDU> <12793@attcan.UUCP> <1990Oct22.164803.24643@sapphire.idbsu.edu>
Distribution: na
Organization: AT&T, Basking Ridge NJ
Lines: 29

In article <15406@hydra.gatech.EDU>, jkg@prism.gatech.EDU (Jim Greenlee) writes:
> I have a 3B2/310 that is crashing at seemingly random times (sometimes
> daily) due to a kernel MMU fault. This machine is on a local area network
> that has about 8 other 3B2s that are connected via RFS. We are running SVR
> 3.2 and WIN TCP/IP 3.0.1 (which we're using as the netspec for RFS).

In article <12793@attcan.UUCP> ram@attcan.UUCP (Richard Meesters) writes:
>We've seen some problems up here in Canada with kernel MMU fault (F_ACCESS) on
>machines running SVR3.2.2 and TCP/IP.

In article <1990Oct22.164803.24643@sapphire.idbsu.edu>, jahn@sapphire.idbsu.edu (Greg Jahn) writes:
> Don't bet on it (hotine support answers).  We are experiencing the same
> KERNEL MMU FAULT (F_ACCESS) problem.  We run a 3B2/600 SVR3.2.2, TCP/IP
> 3.0.1.  Our system was failing sometimes DURING going to 'init 3', and 
> other times at most 15 minutes after coming up.

We've been suffering with this problem (F_ACCESS) too, but it only
seems to occur when trying to access a system (via rlogin, rcp, etc.)
that is currently down.  And in such cases it always happens -- rather
than reporting "Connection timed out", it waits about 2 minutes and
crashes.  So we're very careful to comment out /etc/hosts lines for
systems that go down -- we have a daemon doing it.

We're running SVR3.1 with an older version of TCP/IP.  We were hoping
our upcoming upgrade to both would fix it..

Bill Brelsford
AT&T, Basking Ridge NJ
wmb@joplin.att.com