> Typically the above machine will panic with:
>
> panic: lockmgr: no context
> Stopped at      0x800fe860:     jr      ra
>                bdslot: nop
>
> or more infrequently:
> 
> panic: TLB out of universe: ksp 0xc490bf78 epc 0x8004b3d4 vaddr 0xcfb1f000
> Stopped at      0x800fe860:     jr      ra
>                 bdslot: nop
>
> db> machine tlb
> TLB  0 Hi 0xc4d9e000 Lo0=0x03fe9000 DG attr 3 Lo1=0x03fe8000 DG attr 3 sz=0
> TLB* 1 Hi 0x80000000 Lo0=0x00000000    attr 0 Lo1=0x00000000    attr 0 sz=0
> TLB* 2 Hi 0xc492a004 Lo0=0x00000000  G attr 0 Lo1=0x00000000  G attr 0 sz=0
> TLB* 3 Hi 0xc4952004 Lo0=0x00000000  G attr 0 Lo1=0x00000000  G attr 0 sz=0
> ...

Hey, it's redicous.  If the DDB output showed what's inside TLB
correctly, it would tell something very wrong are going on in TLB
management.  I suspect that it might be a rather common brokenness
across NetBSD/mips ports.

Tohru Nishimura