Pedro Martelletto wrote: > If you can still reproduce the problem with the latest snapshot, > please break into ddb, use 'ps' to see the PID of the 'reboot' > process, and get us the output of 'tr /p 0t<PID> '.
Here it is, I took a photo so the transscript may contain errors. ddb> tr /p 0t1847 sleep_finish(e8a0cc8,8,e8a0c0e,d0336e92,e8a08cc8) at sleep_finish+0x38 sleep_finish(e8a0cc8,1,8,d0698380,0) at sleep_finish+0x38 tsleep(d766d1dc,8,d0698380,0) at tsleep+0x7a lockmgr(d766d1dc,7,0,d032f3b7,90) at lockmgr+0x255 ufs_lock(e8a08d48,0,d077dc40,0,d0740a40) at ufs_lock+0x20 VOP_LOCK(d766c0b0,7,d763a2d0,108,8) at VOP_LOCK+0x2e vclean(d766c0b0,0,d763a2d0,1,0) at vclean+0x3c vflush_vnode(d766c0b0,e8a08df8,0,1) at vflush_vnode+0x6a vfs_mount_foreach_vnode(d1672800,d035b018,e8a08df8,d036241a) at vfs_mount_foreach_vnode+0x2b vflush(d1672800,0,2,2) at vflush+0x2a ffs_flushfiles(d1672800,2,d763a2d0,d1672800,0) at ffs_flushfile+0x4d ffs_unmount(d1672800,80000,d763a2d0,0,d1672800) at ffs_unmount+0x135 dounmount(d1672800,80000,d763a2d0,0) at dounmount+0x64 vfs_unmountall(d077d220,0,0,d073faa4) at vfs_unmountall+0x8f vfs_shutdown(0,d763a2d0,e8a08f20,d033943a,0) at vfs_shutdown+0x70 boot(0,0,0,0,d073ea98) at boot+0x196 sys_reboot(d763a2d0,e8a08f68,e8a08f58,ffffffff,1fb) at sys_reboot+0x26 syscall() at syscall+0x24a --- syscall (number 55) --- 0x1c0009b5: ddb> _ # Han
