panic: bufwrite: buffer is not busy???

[Eugene Grosbein]

> Assuming your kernel is built with debug symbols (which is the default), one
> thing you can do to aid in debugging is this:
> 
> gdb /boot/kernel/kernel
> (gdb) l *0xffffffff803cc979
> 
> Where the 0xfff<blah> bit is the part of the 'instruction pointer' value
> above after the colon (:) and then send the output of that in your e-mail to
> the list.  This allows us to the source line at which the fault occurred.

I'd glad to, but just found that HDD crash on my buildbox took away obj directory
for this NanoBSD... I'll rebuild it again do this next time (it won't take much time, sigh).

Btw, I did not know of this way to debug, thanks.