Subject: Re: -current TLB panics on 3100?
To: William O Ferry <woferry@iname.com>
From: Michael L. Hitch <mhitch@lightning.msu.montana.edu>
List: port-pmax
Date: 11/07/1999 13:07:30
On Sun, 7 Nov 1999, William O Ferry wrote:

> 	Has anybody heard of anything like this?  Any clue what I could to about it?  
...
> trap: TLB miss (load or instr. fetch) in kernel mode
> status=0x8fc34, cause=0x30000000, epc=0x8014b628, vaddr=0x100
                                        ^^^^^^^^^^
> pid=251 cmd=xntpd usp=0x7ffffce0 ksp=0xc2163e90
> stopped in xntpd at  trap+0x2f4:	lw	a2,0(v1)
                       ^^^^^^^^^^
  Is trap+0x2f4 the same address as 0x8014b628?

  Is this a GENERIC, or custom kernel?

  I'm trying to figure out where the TLB miss occurred.  It looks like it
could be a NULL pointer problem, but I can't tell for certain without
seeing what code was actually being executed.

  Try doing "x/i 0x8014b60,10" at the DDB prompt - that should display
some of the code around that execption.

> 	Any help would be greatly appreciated.  Thanks in advance.

  I've been working on some MIPS3 related problems with -current, so I've
got a -current GENERIC kernel (as well as few custom kernels) to test
with.  My 3100 isn't connected at the moment, since I needed the 5000/50
connected to test other things.  [I originally was working on the MI SCSI
code, before I got sidetracked with other -current problems.  Once I got
the MI SCSI straighted out, I was going to switch the 5000/50 to the 3100
and see what I can do for MI SCSI support on the 3100.]

--
Michael L. Hitch			mhitch@montana.edu
Computer Consultant
Information Technology Center
Montana State University	Bozeman, MT	USA