In message <20000523202353.B16862@dr-evil.shagadelic.org>, Jason R Thorpe write
>This is not i386-specific.

Wasn't clear to me, thanks.

>curproc is NULL when the system is idle.  If you then get an interrupt
>which leads to a panic, curproc is obviously still NULL and the problem
>occurs.

OK, sure.

Is lockmgr() not supposed to be called in an interrupt context -- who
is to blame here?

>The alternative, of course, is for lockmgr() to simply dereference NULL
>when it attempts to store the pid of the locking process in the lock
>structure.
>
>Which do you prefer?  Random kernel fault or meaningful panic? :-)

Ha, ha.

--jhawk