Hi, just wanted to provide another data point -- my CATS board exhibits the
same behavior if I compile a -current kernel (from 11/12/1998). tr and ps
reveal the same crash point.

Off Topic:
I have a fix for the USB driver to enable it to handle high-speed devices --
how do I go about submitting it? I haven't contributed code to NetBSD
before; is there some special mailing list to mail patches to?

---
Edwin Foo
Compaq Computer Corp. - Cambridge Research Lab 
MIT EECS BS '98, M. Eng. '99


-----Original Message-----
From: Todd Whitesel [mailto:toddpw@best.com]
Sent: Friday, November 13, 1998 7:41 AM
To: port-arm32@netbsd.org
Subject: My CATS box is _still_ crashing on boot.


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.

Todd Whitesel
toddpw @ best.com