On Fri, 13 Nov 1998 04:40:50 -0800 (PST) 
 Todd Whitesel <toddpw@best.com> wrote:

 > Well, Mark's fix for the cnopen() crash is working great, but I get another
 > panic right after it (argh!):
 > 
 > 	root file system type: ffs
 > 	panic: cpu_fork: curproc
 > 	Stopped in init at      _Debugger+0x10: ldmdb    r11, {r11, r13, r15}
 > 	db> tr
 > 	_Debugger(_Debugger+0x10)
 > 	_panic(_panic+0x14)
 > 	_cpu_fork(_cpu_fork+0x10)
 > 	_uvm_fork(_uvm_fork+0x10)
 > 	_fork1(_fork1+0x10)
 > 	_sys_fork(_sys_fork+0x10)
 > 	_syscall(_syscall+0x10)
 > 	db>
 > 
 > A ps list shows that the current process is the parent init (pid 1) which
 > has apparently just spawned a child init (pid 4) that has yet to exec.

This was a thinko in the kthread_create() changes I made.  It has been
fixed.  Look in vm_machdep.c and just remove those panic's if you want
to get running before tomorrow's SUP.

Jason R. Thorpe                                       thorpej@nas.nasa.gov
NASA Ames Research Center                            Home: +1 408 866 1912
NAS: M/S 258-5                                       Work: +1 650 604 0935
Moffett Field, CA 94035                             Pager: +1 650 940 5942