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
>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
After enabling ACPI in my kernel I get these messages in dmesg:
---snip---
VESA: v2.0, 2496k memory, flags:0x0, mode table:0xc03b82e2 (122)
VESA: MagicGraph 256 AV 44K PRELIMINARY
ACPI-0299: *** Warning: Invalid table signature found
ACPI-0170: *** Error: AcpiLoadTables: Could not l
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
