Re: NTFS issue (was: Panic w/crash dump (looks like atomic.h problem))

2001-01-19 Thread Boris Popov
On Sat, 20 Jan 2001, Boris Popov wrote: > On Fri, 19 Jan 2001, Rogier Mulhuijzen wrote: > > > During normal operation on my NTFS partition I got no messages, so I took a > > bold step and added 'ip->i_devvp = ntmp->ntm_devvp;' just before the VREF call. > > You're absolutely right here.

Re: NTFS issue (was: Panic w/crash dump (looks like atomic.h problem))

2001-01-19 Thread Boris Popov
On Fri, 19 Jan 2001, Rogier Mulhuijzen wrote: > During normal operation on my NTFS partition I got no messages, so I took a > bold step and added 'ip->i_devvp = ntmp->ntm_devvp;' just before the VREF call. You're absolutely right here. This line definitely should be presented in the cod

NTFS issue (was: Panic w/crash dump (looks like atomic.h problem))

2001-01-19 Thread Rogier Mulhuijzen
a quick look at kldstat output pinpointed the ??'s in my stacktrace(see previous posts) to ntfs.ko. Compiled NTFS into my kernel and reproduced the crash. Taking a look at the trace now: #11 0xc01c0c97 in vref (vp=0x0) at machine/atomic.h:332 #12 0xc0239592 in ntfs_vgetex (mp=0xc0f7dc00, ino=4

RE: Panic w/crash dump (looks like atomic.h problem)

2001-01-18 Thread John Baldwin
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

Re: Panic w/crash dump (looks like atomic.h problem)

2001-01-18 Thread Dag-Erling Smorgrav
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

RE: Panic w/crash dump (looks like atomic.h problem)

2001-01-18 Thread Rogier Mulhuijzen
>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

RE: Panic w/crash dump (looks like atomic.h problem)

2001-01-18 Thread John Baldwin
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 >

Panic w/crash dump (looks like atomic.h problem)

2001-01-18 Thread Rogier Mulhuijzen
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 Kernel config file dmesg(8) outpu