On Thu, 28 Sep 2000, Jason R Thorpe wrote:

> On Thu, Sep 28, 2000 at 09:54:39PM +0300, Eduardo Horvath wrote:
> 
>  > Log Message:
>  > Fix the `trap type 0x10' problem.  Apparently, something has changed and
>  > now makes use of lockmgr().  Since we broke into the debugger from an interrupt,
>  > we don't have a curproc, so when lockmgr() tries to find our PID it barfs,
>  > causing another break into DDB which then calls the mysterious code that
>  > calls lockmgr() again.....
>  > 
>  > So set doing_shutdown while we're in DDB so lockmgr ignores locks.
> 
> Bad to just ignore it.  What is calling lockmgr?  Got a trace?

Can't get a trace.  Either it loops forever or does a longjmp back into
DDB and we lose the trace.


Eduardo Horvath