Hey all, I'm a bit curious as to why my 4.6 Release box (stripped down and patched) rebooted this morning. I've had this problem before when I tried to skimp and use cheap memory, but this box has great memory (can't remember which brand) and has been running 4.4 release for a year, then 4.6 release for the last 3 months - both without a problem. Last Saturday I got a phone call that this box was down and had remote hands reboot and fsck -y the thing so I'm not sure what's happening. This is the error from /var/run/messages regarding today's reboot; Saturday's problem left no logs. ------------------------------------------------- Oct 14 03:07:20 mas01 /kernel: Fatal trap 12: page fault while in kernel mode Oct 14 03:07:20 mas01 /kernel: mp_lock = 00000002; cpuid = 0; lapic.id = 00000000 Oct 14 03:07:20 mas01 /kernel: fault virtual address = 0x30000008 Oct 14 03:07:20 mas01 /kernel: fault code = supervisor read, page not present Oct 14 03:07:20 mas01 /kernel: instruction pointer = 0x8:0xc0216818 Oct 14 03:07:20 mas01 /kernel: stack pointer = 0x10:0xebaa5bc8 Oct 14 03:07:20 mas01 /kernel: frame pointer = 0x10:0xebaa5bfc Oct 14 03:07:20 mas01 /kernel: code segment = base 0x0, limit 0xfffff, type 0x1b Oct 14 03:07:20 mas01 /kernel: = DPL 0, pres 1, def32 1, gran 1 Oct 14 03:07:20 mas01 /kernel: processor eflags = interrupt enabled, resume, IOPL = 0 Oct 14 03:07:20 mas01 /kernel: current process = 1705 (find) Oct 14 03:07:20 mas01 /kernel: interrupt mask = bio <- SMP: XXX Oct 14 03:07:20 mas01 /kernel: trap number = 12 Oct 14 03:07:20 mas01 /kernel: panic: page fault Oct 14 03:07:20 mas01 /kernel: mp_lock = 00000002; cpuid = 0; lapic.id = 00000000 Oct 14 03:07:20 mas01 /kernel: boot() called on cpu#0
===== ----------------------------------------------------------- Heavy metal made me do it. ----------------------------------------------------------- __________________________________________________ Do You Yahoo!? Yahoo! Health - Feel better, live better http://health.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message