Path: utzoo!attcan!uunet!samsung!emory!sol.ctr.columbia.edu!zaphod.mps.ohio-state.edu!usc!ucsd!network.ucsd.edu!siodo!laver
From: laver@siodo.UCSD.EDU (Mick Laver)
Newsgroups: comp.sys.att
Subject: Re: 3B2 crashes mysteriously
Message-ID: <345@siodo.UCSD.EDU>
Date: 27 Oct 90 04:49:24 GMT
References: <15406@hydra.gatech.EDU> <12793@attcan.UUCP> <1990Oct22.164803.24643@sapphire.idbsu.edu> <12840@attcan.UUCP>
Reply-To: laver@siodo.UUCP (Mick Laver)
Distribution: na
Organization: University of California, San Diego
Lines: 10

>Like I said, there's a problem running 3.2.2 UNIX with 3.0.1 TCP/IP, which 
>will cause the machines to intermittantly panic with a Kernel MMU Fault
>(F_ACCESS).  I don't know what the cause of the panic is, but in my 
....
>The only fix I know of is to upgrade the machine to UNIX 3.2.3.  I haven't 
>been able to find the fix seperately.

We have the same problem on both a 400 and 600 running 3.1.1. I've been
assured by the hotline folks that the 3.2 tcp/ip release will fix it.
Can anyone verify that?