Subject: port-i386/10187: consistent panic: lockmgr: no context
To: None <email@example.com>
From: John Hawkinson <firstname.lastname@example.org>
Date: 05/23/2000 20:04:13
>Synopsis: consistent panic: lockmgr: no context
>Arrival-Date: Tue May 23 20:05:00 PDT 2000
>Originator: John Hawkinson
>Release: 21 May 2000
System: NetBSD zorkmid.mit.edu 1.4Y NetBSD 1.4Y (ZORKMID-$Revision: 1.8 $) #120: Tue May 23 22:30:37 EDT 2000 email@example.com:/usr/local/current-src/sys/arch/i386/compile/ZORKMID i386
Attempting to sync disks as part of a panic, 1.4Y consistently
panics with a lockmgr fault.
Simon Burge <firstname.lastname@example.org> reported this to tech-kern on 15
| 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
Cause the machine to panic() for any reason...while trying to
sync discs, watch this happen.
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.