Hi, I have a 5.5-STABLE laptop thats been having issues lately, mostly related to memory. I bought new chips, and I think I narrowed it down to one of the Dimm slots being bad. I did a memtest for 25 hours and it seemed stable. I started up and started downloading a backup of over 5K emails. (All have to go through mimedefang, procmail and sendmail... So the system was a bit sluggish. I started to get things like :
Oct 10 22:06:29 himinbjorg kernel: KDB: stack backtrace: Oct 10 22:06:29 himinbjorg kernel: kdb_backtrace(c3053200,1,dbb54c04,dbb54bf0,c0 73ba78) at kdb_backtrace+0x29 Oct 10 22:06:29 himinbjorg kernel: getdirtybuf(dbb54be0,0,1,cc1c81e8,1) at getdi rtybuf+0x27 Oct 10 22:06:29 himinbjorg kernel: flush_deplist(c305354c,1,dbb54c04) at flush_d eplist+0x34 Oct 10 22:06:29 himinbjorg kernel: flush_inodedep_deps(c216d000,715e,c089bcf8,c0 808b16,ef) at flush_inodedep_deps+0x7d Oct 10 22:06:29 himinbjorg kernel: softdep_sync_metadata(dbb54ca0) at softdep_sy nc_metadata+0x8c Oct 10 22:06:29 himinbjorg kernel: ffs_fsync(dbb54ca0) at ffs_fsync+0x33e Oct 10 22:06:29 himinbjorg kernel: fsync(c3549600,dbb54d04,1,1,286) at fsync+0x1 03 Oct 10 22:06:29 himinbjorg kernel: syscall(2f,2f,bfbf002f,80fef20,0) at syscall+ 0x227 Oct 10 22:06:29 himinbjorg kernel: Xint0x80_syscall() at Xint0x80_syscall+0x1f Oct 10 22:06:29 himinbjorg kernel: --- syscall (95, FreeBSD ELF32, fsync), eip = 0x28181ca7, esp = 0xbfbf6d1c, ebp = 0xbfbf86e8 --- and Oct 10 22:08:21 himinbjorg kernel: KDB: stack backtrace: Oct 10 22:08:21 himinbjorg kernel: kdb_backtrace(c345fe80,1,daf32c04,daf32bf0,c0 73ba78) at kdb_backtrace+0x29 Oct 10 22:08:21 himinbjorg kernel: getdirtybuf(daf32be0,0,1,cc22e334,1) at getdi rtybuf+0x27 Oct 10 22:08:21 himinbjorg kernel: flush_deplist(c295a34c,1,daf32c04) at flush_d eplist+0x34 Oct 10 22:08:21 himinbjorg kernel: flush_inodedep_deps(c216d000,72b7,c089bcf8,c0 808b16,ef) at flush_inodedep_deps+0x7d Oct 10 22:08:21 himinbjorg kernel: softdep_sync_metadata(daf32ca0) at softdep_sy nc_metadata+0x8c Oct 10 22:08:21 himinbjorg kernel: ffs_fsync(daf32ca0) at ffs_fsync+0x33e Oct 10 22:08:21 himinbjorg kernel: fsync(c2bc0600,daf32d04,1,1,286) at fsync+0x1 03 Oct 10 22:08:21 himinbjorg kernel: syscall(bfbf002f,bfbf002f,bfbf002f,80fef20,0) at syscall+0x227 Oct 10 22:08:21 himinbjorg kernel: Xint0x80_syscall() at Xint0x80_syscall+0x1f Oct 10 22:08:21 himinbjorg kernel: --- syscall (95, FreeBSD ELF32, fsync), eip = 0x28181ca7, esp = 0xbfbf6d1c, ebp = 0xbfbf86e8 --- infact..................... himinbjorg% grep "KDB: stack" spool Oct 10 22:06:29 himinbjorg kernel: KDB: stack backtrace: Oct 10 22:06:29 himinbjorg kernel: KDB: stack backtrace: Oct 10 22:06:29 himinbjorg kernel: KDB: stack backtrace: Oct 10 22:08:21 himinbjorg kernel: KDB: stack backtrace: Oct 10 22:09:23 himinbjorg kernel: KDB: stack backtrace: Oct 10 22:09:57 himinbjorg kernel: KDB: stack backtrace: Oct 10 22:10:08 himinbjorg kernel: KDB: stack backtrace: Oct 10 22:10:43 himinbjorg kernel: KDB: stack backtrace: Since its 5.5, and the system seems to potentially not be "with it" hardware wise, think its worth persuing what happened here? Thanks, Tuc _______________________________________________ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"