Kernel panic doing du

[Warren Toomey <wkt@xxxxxxxx>]

After cvsupping today (Sat May 29) and rebuilding a kernel, I'm seeing a 
kernel panic when I do cd /usr; du. Going back to a kernel dated May 13
lets du complete with no problems. Here are details; let me know if more 
are required (it's my 1st dfly panic report).
	Warren

IdlePTD at phsyical address 0x003f5000
PCB @003493e0 EIP=c0177ed6 ESP=d118f958 EBP=d118f964
initial pcb at physical address 0x003493e0
panicstr: page fault
panic messages:
---
Fatal trap 12: page fault while in kernel mode
fault virtual address   = 0xc00b
fault code              = supervisor read, page not present
instruction pointer     = 0x8:0xd0f37cc2
stack pointer           = 0x10:0xd118fa68
frame pointer           = 0x10:0xd118fa98
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         = 670 (du)
current thread          = pri 6
interrupt mask          = none
trap number             = 12
panic: page fault

(kgdb) where
#0  dumpsys () at ../../kern/kern_shutdown.c:500
#1  0xc0177ccb in boot (howto=256) at ../../kern/kern_shutdown.c:333
#2  0xc01780fc in poweroff_wait (junk=0xc02f3a6a, howto=-1070648178)
    at ../../kern/kern_shutdown.c:612
#3  0xc02a1f31 in trap_fatal (frame=0xd118fa28, eva=49163)
    at ../../i386/i386/trap.c:1092
#4  0xc02a1b35 in trap_pfault (frame=0xd118fa28, usermode=0, eva=49163)
    at ../../i386/i386/trap.c:981
#5  0xc02a182c in trap (frame={tf_fs = -789381096, tf_es = -785776624,
      tf_ds = -785776624, tf_edi = -786892000, tf_esi = -1070534144,
      tf_ebp = -786892136, tf_isp = -786892204, tf_ebx = -786892096,
      tf_edx = -786892112, tf_ecx = -1057352352, tf_eax = 49047,
      tf_trapno = 12, tf_err = 0, tf_eip = -789349182, tf_cs = 8,
      tf_eflags = 66199, tf_esp = -786892096, tf_ss = -786891944})
    at ../../i386/i386/trap.c:561
#6  0xd0f37cc2 in ?? ()
#7  0xc01b55f3 in vn_stat (vp=0xd12a71c0, sb=0xd118fb58, td=0xc672af40)
    at vnode_if.h:354
#8  0xc01b1c65 in kern_stat (nd=0xd118fbb8, st=0xd118fb58)
    at ../../kern/vfs_syscalls.c:1610
#9  0xc01b1d72 in lstat (uap=0xd118fc40) at ../../kern/vfs_syscalls.c:1655
#10 0xc02a224e in syscall2 (frame={tf_fs = 134545455, tf_es = 47,
      tf_ds = -1078001617, tf_edi = 134546944, tf_esi = 134547016,
      tf_ebp = -1077939088, tf_isp = -786891404, tf_ebx = 672151436,
      tf_edx = 134533120, tf_ecx = 0, tf_eax = 190, tf_trapno = 12,
      tf_err = 2, tf_eip = 671839796, tf_cs = 31, tf_eflags = 663,
      tf_esp = -1077939228, tf_ss = 47}) at ../../i386/i386/trap.c:1297
#11 0xc029188a in Xint0x80_syscall ()

P.S I did boot -s; fsck (no -p); mount -a, multi-user mode, login, cd 
/usr; du, so I don't think the filesystems were corrupt.