On 18-Jan-01 Rogier Mulhuijzen wrote:
>
>>If you look at the traceback, vref() was called with a NULL vnode as its
>>parameter, so the panic is due to dereferencing a NULL pointer, not a bug in
>>the atomic ops. :) As to why the kernel was vref()'ing a NULL pointer, I
>>have
>>no idea.
>
>#11
Rogier Mulhuijzen <[EMAIL PROTECTED]> writes:
> My next question is, where are those ??'s from in #12 - #15? Could they be
> addresses in kernel modules?
Quite possibly.
> If so, how do I readable output from that, save compiling everything into
> the kernel statically?
Read the handbook sect
>If you look at the traceback, vref() was called with a NULL vnode as its
>parameter, so the panic is due to dereferencing a NULL pointer, not a bug in
>the atomic ops. :) As to why the kernel was vref()'ing a NULL pointer, I have
>no idea.
#11 0xc01c057f in vref (vp=0x0) at machine/atomic.h:33
On 18-Jan-01 Rogier Mulhuijzen wrote:
> Got a nice crash while running XMMS under X11 and running a 'make world -j
> 128 -DNOCLEAN' on ttyv0
>
> Current was cvsupped on the 17th in the morning (Central European Time) IIRC.
>
> Attached: script(1) output of gdb kernel trace
>
