Panic on page fault during /bin/mv

Hi,

	I got a panic on a Toshiba laptop Satellite A135-S4527
(Intel Pentium dual-core processor T2080) running 7-STABLE as of
November, 8th.

FreeBSD nexxus.fedaykin.here 7.0-BETA2 FreeBSD 7.0-BETA2 #5: Thu Nov  8 23:44:48 BRST 2007     lioux_at_nexxus:/usr/obj/usr/src/sys/LIOUX  i386

        The panic happened on a page fault during a routine mv(1)
operation on a UFS2 filesystem. No zfs on this system. Swap is
untouched.

        Further information is attached. Let me know if there is
anything I can do to help.

	Files can also be downloaded:

- My kernel configuration
http://people.FreeBSD.org/~lioux/panic/KERNCONF
- kgdb(1) backtrace
http://people.FreeBSD.org/~lioux/panic/crash.1.log
- My system's dmesg
http://people.FreeBSD.org/~lioux/panic/dmesg.boot
- My system's pciconf(8)
http://people.FreeBSD.org/~lioux/panic/pciconf.txt
- My system's uname(1)
http://people.FreeBSD.org/~lioux/panic/uname.txt
- Crash dump /var/crash/info file
http://people.FreeBSD.org/~lioux/panic/info.1
- archivers/lzma compressed core dump
http://people.FreeBSD.org/~lioux/panic/vmcore.1.lzma
- archivers/lzma compressed kernel with debug symbols
http://people.FreeBSD.org/~lioux/panic/kernel.debug.lzma

	Regards,

ps: To uncompress the lzma compressed files, proceed as following

# cd /usr/ports/archivers/lzma
# make install clean
# lzma d vmcore.1.lzma vmcore.1
# lzma d kernel.debug.lzma kernel.debug

so that you can access vmcore.1 and kernel.debug

---------------

Fatal trap 12: page fault while in kernel mode
cpuid = 1; apic id = 01
fault virtual address   = 0x88
fault code              = supervisor read, page not present
instruction pointer     = 0x20:0xc069922c
stack pointer           = 0x28:0xe699fa8c
frame pointer           = 0x28:0xe699fb44
code segment            = base 0x0, limit 0xfffff, type 0x1b
                        = DPL 0, pres 1, def32 1, gran 1
processor eflags        = interrupt enabled, resume, IOPL = 0
current process         = 80409 (mv)
trap number             = 12

#8  0xc069922c in _sx_xunlock (sx=Cannot access memory at address 0x866
) at /usr/src/sys/kern/kern_sx.c:308
308             KASSERT(sx->sx_lock != SX_LOCK_DESTROYED,
Current language:  auto; currently c
(kgdb) list
303     void
304     _sx_xunlock(struct sx *sx, const char *file, int line)
305     {
306
307             MPASS(curthread != NULL);
308             KASSERT(sx->sx_lock != SX_LOCK_DESTROYED,
309                 ("sx_xunlock() of destroyed sx _at_ %s:%d", file, line));
310             _sx_assert(sx, SA_XLOCKED, file, line);
311             curthread->td_locks--;
312             WITNESS_UNLOCK(&sx->lock_object, LOP_EXCLUSIVE, file, line);

-- 
Mario S F Ferreira - DF - Brazil - "I guess this is a signature."
feature, n: a documented bug | bug, n: an undocumented feature