>Number:         10187
>Category:       port-i386
>Synopsis:       consistent panic: lockmgr: no context
>Confidential:   no
>Severity:       critical
>Priority:       medium
>Responsible:    port-i386-maintainer
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Tue May 23 20:05:00 PDT 2000
>Closed-Date:
>Last-Modified:
>Originator:     John Hawkinson
>Release:        21 May 2000
>Organization:
MIT
>Environment:
	
System: NetBSD zorkmid.mit.edu 1.4Y NetBSD 1.4Y (ZORKMID-$Revision: 1.8 $) #120: Tue May 23 22:30:37 EDT 2000 jhawk@zorkmid.mit.edu:/usr/local/current-src/sys/arch/i386/compile/ZORKMID i386


>Description:
	Attempting to sync disks as part of a panic, 1.4Y consistently
panics with a lockmgr fault.

Simon Burge <simonb@netbsd.org> reported this to tech-kern on 15
May:

| Also, this hasn't been tested (nor is support complete yet) for working
| on kernel crash dumps.  That said, how does one force a crash dump these
| days?  On an i386:
| 
|        login: ~Stopped at      cpu_Debugger+0x4:       leave
|        db> sync
|        syncing disks... panic: lockmgr: no context
|        Stopped at      cpu_Debugger+0x4:       leave
|        db> 

>How-To-Repeat:
	Cause the machine to panic() for any reason...while trying to
sync discs, watch this happen.
>Fix:
	I dunno. This panic happens if curproc is NULL upon entry into
lockmgr(), but I don't know what causes curproc to go NULL, other than
cpu_switch(), and I'm presuming that's not what is going on here.
>Release-Note:
>Audit-Trail:
>Unformatted: