>Number:         3781
>Category:       port-pmax
>Synopsis:       kernel stack overflow panic (with ktlbmiss)
>Confidential:   no
>Severity:       serious
>Priority:       low
>Responsible:    gnats-admin (GNATS administrator)
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Mon Jun 23 21:20:01 1997
>Last-Modified:
>Originator:     Simon Burge
>Organization:
	Telstra Corp, Australia.
>Release:        NetBSD-current 970623
>Environment:
System: NetBSD vlad 1.2G NetBSD 1.2G (MONA) #0: Mon Jun 23 11:15:24 EST 1997 simonb@mona:/usr/src/sys-970623/arch/pmax/compile/MONA pmax

>Description:
	I got a kernel panic just after a machine came up.  Details:

	    mona:~ 1# ntpdate timehost
	    ktlbmiss: PC 80030a08 RA 800438b4 ADR ffffc184
	    SR 800 CR 3000000c SP 8002ffe0
	    panic: kernel stack overflow
	    stacktrace_subr+48 (c504f000,0,0,8002ffec) ra 80033260 sz 128
	    stacktrace+18 (c504f000,0,0,8002ffec) ra 80122054 sz 32
	    80122008+4c (100,0,0,8002ffec) ra 80054ac0 sz 40
	    80054a60+60 (80135cd0,80132cc3,8002ffec,0) ra 80031140 sz 24
	    8003094c+7f4 (80135cd0,80132cc3,8002ffec,0) ra 0 sz 0
	    User-level: pid 672
	    syncing disks... 7 7 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 giving up
	    rebooting...

>How-To-Repeat:
	Don't know :(  The same sequence of events didn't cause the panic
	second time around.

	Michael Hitch has noticed similar panics in the past.
>Fix:
	Unknown.  This is just a place holder PR.  -current has some
	more debugging info for this case.  More later I hope...
>Audit-Trail:
>Unformatted: