Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!wuarchive!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!hamblin.math.byu.edu!news
From: jlp@hamblin.math.byu.edu (Jan L. Peterson)
Newsgroups: comp.sys.next
Subject: wierd panic problem with 68040
Message-ID: <JLP.91May21094547@phred.hamblin.math.byu.edu>
Date: 21 May 91 16:45:47 GMT
Sender: news@hamblin.math.byu.edu (Usenet News)
Organization: Brigham Young University
Lines: 29

Okay, folks.  I have just upgraded my NeXT Cube to 68040.  I'm running
NeXT Step 2.1.  Since the upgrade (last thursday) the system has
crashed about 20 times.  I saw the latest one. . . Here are the
contents of the last msgbuf.  (This information didn't end up anywhere
on the disk.  I thought savecore was supposed to try and save this
junk.) 

	unexpected kernel page fault failure
	trap: type 0x410 fcode 5 rw 3 faultaddr 0xc0
	trap: pc 0x406d3e4 sp 0x3fffe70 sr 0x2314
	trap cpu 0 th 0x100473c4 proc 0x10046e20 pid 123
	pcb 0x10e3a00c
	traceback: fp 0x10e3ad10
		.
		.
		.
	panic: (Cpu 0) MMU invalid descriptor during table walk

I have also seen this:
	panic: (Cpu 0) unwire: page not in pmap

Does it look like a memory problem to you or do I have a bad board
(mmu problem)?  The system has original NeXT 1MB SIMMs in SIMM banks 0
and 1, 3rd party 1MB SIMMs in bank 2, and 3rd party 4MB SIMMs in bank
3.

Any suggestions?

	-jan-
--
        Jan L. Peterson		Network Systems Manager
EMail:  jlp@hamblin.math.byu.edu
Mail:   Math Department -- 292 TMCB; BYU; Provo, UT 84602 (USA)
Phone:  +1 801 378 2183		FAX:  +1 801 378 2800