3B2 crashes mysteriously

[Richard Meesters]

In article <1990Oct22.164803.24643 at sapphire.idbsu.edu>, jahn at sapphire.idbsu.edu (Greg Jahn) writes:
> In article <12793 at attcan.UUCP> ram at attcan.UUCP (Richard Meesters) writes:
> >In article <15406 at hydra.gatech.EDU>, jkg at 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). Only
| >> one of the machines is exhibiting this trouble - the rest have been up for
| >> a month with no problems. Another department here on campus is having the
| >> same problem with a 3B2/1000, only less frequently (once every 3-4 weeks).
| >> 
| >
| >We've seen some problems up here in Canada with kernel MMU fault (F_ACCESS) on
| >machines running SVR3.2.2 and TCP/IP.  The problem is apparently fixed in the 
| >3.2.3 release of UNIX.  I don't know if this release applies to your 3B2/310
| >though.  Best bet is to call the hotline (like you say you're going to do 
| >anyways).  They should recognize it as a known problem.
| 
| 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.  The hotline said to do
| a partial restore (non-trivial solution).  Then our system was stable
| for about two weeks, now it has failed twice in the last three days.
| The hotline didn't seem familiar with the problem.  DOES ANYONE OUT
| THERE KNOW WHAT"S GOING ON?
| 

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 
experience with it, it's an intermittant failure that may or may not be 
exhibited on a particular machine.  I've seen situations where on two 
virtually identical machines, one has the problem and the other doesn't.  
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.


Regards,

------------------------------------------------------------------------------
     Richard A Meesters                |
     Technical Support Specialist      |     Insert std.logo here
     AT&T Canada                       |
                                       |     "Waste is a terrible thing
     ATTMAIL: ....attmail!rmeesters    |      to mind...clean up your act"
     UUCP:  ...att!attcan!ram          |
------------------------------------------------------------------------------