Subject: VM related panic...
To: None <netbsd-bugs@sun-lamp.cs.berkeley.edu>
From: Jason Thorpe <thorpej@cs.orst.edu>
List: netbsd-bugs
Date: 05/21/1994 17:00:44
Here you go: (Apr 25 kernel on an i486, 16meg)

panic: unwire: page not in pmap
Stopped at _Debugger+0x4: leave
db> trace
_Debugger(f7bffdc5,5,0,f7bffeb0,f7bffda4) at _Debugger+0x4
_panic(f815c568) at _panic+0x54
_vm_fault_unwire(f84a6500,4000,7000,f845bf80,f7bffefc) at _vm_fault_unwire+0x32
_vm_map_entry_unwire(f84a6500,f845bf80) at _vm_map_entry_unwire+0x15
_vm_map_delete(f84a6500,0,f7bfe000,f84aad00,f84aad00) at _vm_map_delete+0x96
_vm_map_remove(f84a6500,0,f7bfe000) at _vm_map_remove+0x3f
_kexit(f84aad00,0,f7bfffb4,f8168437,f84aad00) at _kexit+0x8c
_rexit(f84aad00,f7bfff94,f7bfff8c,0,ffffffff) at _rexit+0x14
_syscall() at _syscall+0x12b
--- syscall (number 1) ---
0x10055861:
db>

The process that was exiting was in.gate, a tcp wrapper.  It appears
that the kernel did not want to free up the memory that it was using.
Here is it's entry in the process table:
 pid	proc	 addr	  uid	ppid	pgrp	flag	stat	comm	wchan
3543	f84aad00 f980c000 0	88	88	000121	3	in.gate

Ideas?  It's probably been fixed (I haven't dinked with i386 for a while),
but I thought I'd report it anyway, just in case...

Later...

-----------------------------------------------------------------------------
Jason R. Thorpe                thorpej@cs.orst.edu                   737-9533
OSU CS Support                    CSWest Room 12                     737-5567
      'These are my opinions and not necessarily those of anyone else.'
            NetBSD/Symmetry - Coming soon to a Sequent near you!

------------------------------------------------------------------------------