This is the same backtrace I got when I tried it too... The system would
get all the way through booting, then fam (I'm assuming) sent something to
rpcbind, which then caused this panic.
Ken
On Mon, 14 Jan 2002, Michael McGoldrick wrote:
> The trace was short, so I wrote the whole thing down.
>
On 14-Jan-02 Michael McGoldrick wrote:
> The trace was short, so I wrote the whole thing down.
That one is fixed already, re-cvsup. Also, you should probably be running with
INVARIANTS turned on in -current as that would give more useful error messages.
> _mtx_unlock_sleep(c232c834,0,0,0) at _
