Re: Help to find cause of recurring crash
On 5/16/06, fbsd [EMAIL PROTECTED] wrote: Hello All, I'm running a home email server and twice in the last week it has rebooted itself and been unable to restart due to corruption of the filesystem. I found the following in /var/log/messages May 16 17:46:07 hpvectra syslogd: kernel boot file is /boot/kernel/kernel May 16 17:46:07 hpvectra kernel: May 16 17:46:07 hpvectra kernel: May 16 17:46:07 hpvectra kernel: Fatal trap 12: page fault while in kernel mode May 16 17:46:07 hpvectra kernel: fault virtual address= 0x1c May 16 17:46:07 hpvectra kernel: fault code= supervisor write, page not present May 16 17:46:07 hpvectra kernel: instruction pointer= 0x20:0xc062c5e8 May 16 17:46:07 hpvectra kernel: stack pointer= 0x28:0xe5079c50 May 16 17:46:07 hpvectra kernel: frame pointer= 0x28:0xe5079c64 May 16 17:46:07 hpvectra kernel: code segment= base 0x0, limit 0xf, type 0x1b May 16 17:46:07 hpvectra kernel: = DPL 0, pres 1, def32 1, gran 1 May 16 17:46:07 hpvectra kernel: processor eflags= interrupt enabled, resume, IOPL = 0 May 16 17:46:07 hpvectra kernel: current process= 52 (vnlru) May 16 17:46:07 hpvectra kernel: trap number= 12 May 16 17:46:07 hpvectra kernel: panic: page fault May 16 17:46:07 hpvectra kernel: Uptime: 5d7h4m50s May 16 17:46:07 hpvectra kernel: Dumping 1023 MB (2 chunks) May 16 17:46:07 hpvectra kernel: chunk 0: 1MB (159 pages) ... ok May 16 17:46:07 hpvectra kernel: chunk 1: 1023MB (261872 pages) 1007 991 975 959 943 927 911 895 879 863 847 831 815 799 783 767 751 735 719 703 687 671 655 639 623 607 591 575 559 543 527 511 495 479 463 447 431 415 399 383 367 351 335 319 303 287 271 255 239 223 207 191 175 159 143 127 111 95 79 63 47 31 15 ... ok May 16 17:46:07 hpvectra kernel: May 16 17:46:07 hpvectra kernel: Dump complete May 16 17:46:07 hpvectra kernel: Automatic reboot in 15 seconds - press a key on the console to abort May 16 17:46:07 hpvectra kernel: Rebooting... The only thing I can see (read: understand) is: the process that caused the kernel panic is vnlru: vnlru flushes and frees vnodes when the system hits the kern.maxvnodes limit. This kernel thread sits mostly idle, and only activates if you have a huge amount of RAM and are accessing tens of thousands of tiny files. (from http://www.unixguide.net/freebsd/faq/10.31.shtml) So, consider increasing kern.maxvnodes if your system deals with such a huge amount of files. Thanks in advance, Hope this helps, Ron -- Pietro Cerutti icq #117293691 - ASCII Ribbon Campaign - against HTML e-mail and proprietary attachments www.asciiribbon.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Help to find cause of recurring crash
Pietro Cerutti wrote: On 5/16/06, fbsd [EMAIL PROTECTED] wrote: Hello All, I'm running a home email server and twice in the last week it has rebooted itself and been unable to restart due to corruption of the filesystem. I found the following in /var/log/messages May 16 17:46:07 hpvectra syslogd: kernel boot file is /boot/kernel/kernel May 16 17:46:07 hpvectra kernel: May 16 17:46:07 hpvectra kernel: May 16 17:46:07 hpvectra kernel: Fatal trap 12: page fault while in kernel mode May 16 17:46:07 hpvectra kernel: fault virtual address= 0x1c May 16 17:46:07 hpvectra kernel: fault code= supervisor write, page not present May 16 17:46:07 hpvectra kernel: instruction pointer= 0x20:0xc062c5e8 May 16 17:46:07 hpvectra kernel: stack pointer= 0x28:0xe5079c50 May 16 17:46:07 hpvectra kernel: frame pointer= 0x28:0xe5079c64 May 16 17:46:07 hpvectra kernel: code segment= base 0x0, limit 0xf, type 0x1b May 16 17:46:07 hpvectra kernel: = DPL 0, pres 1, def32 1, gran 1 May 16 17:46:07 hpvectra kernel: processor eflags= interrupt enabled, resume, IOPL = 0 May 16 17:46:07 hpvectra kernel: current process= 52 (vnlru) May 16 17:46:07 hpvectra kernel: trap number= 12 May 16 17:46:07 hpvectra kernel: panic: page fault May 16 17:46:07 hpvectra kernel: Uptime: 5d7h4m50s May 16 17:46:07 hpvectra kernel: Dumping 1023 MB (2 chunks) May 16 17:46:07 hpvectra kernel: chunk 0: 1MB (159 pages) ... ok May 16 17:46:07 hpvectra kernel: chunk 1: 1023MB (261872 pages) 1007 991 975 959 943 927 911 895 879 863 847 831 815 799 783 767 751 735 719 703 687 671 655 639 623 607 591 575 559 543 527 511 495 479 463 447 431 415 399 383 367 351 335 319 303 287 271 255 239 223 207 191 175 159 143 127 111 95 79 63 47 31 15 ... ok May 16 17:46:07 hpvectra kernel: May 16 17:46:07 hpvectra kernel: Dump complete May 16 17:46:07 hpvectra kernel: Automatic reboot in 15 seconds - press a key on the console to abort May 16 17:46:07 hpvectra kernel: Rebooting... The only thing I can see (read: understand) is: the process that caused the kernel panic is vnlru: vnlru flushes and frees vnodes when the system hits the kern.maxvnodes limit. This kernel thread sits mostly idle, and only activates if you have a huge amount of RAM and are accessing tens of thousands of tiny files. (from http://www.unixguide.net/freebsd/faq/10.31.shtml) So, consider increasing kern.maxvnodes if your system deals with such a huge amount of files. Thanks in advance, Hope this helps, Ron Thanks Pietro, I will do that. However I don't think 1GB of RAM is so big and as a home server I would be lucky to deal with more than a couple of hundred emails per day. So if anyone can shed any more light it will be appreaciated. Thanks Ron ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Help to find cause of recurring crash
On 5/16/06, fbsd [EMAIL PROTECTED] wrote: Pietro Cerutti wrote: On 5/16/06, fbsd [EMAIL PROTECTED] wrote: Hello All, I'm running a home email server and twice in the last week it has rebooted itself and been unable to restart due to corruption of the filesystem. I found the following in /var/log/messages May 16 17:46:07 hpvectra syslogd: kernel boot file is /boot/kernel/kernel May 16 17:46:07 hpvectra kernel: May 16 17:46:07 hpvectra kernel: May 16 17:46:07 hpvectra kernel: Fatal trap 12: page fault while in kernel mode May 16 17:46:07 hpvectra kernel: fault virtual address= 0x1c May 16 17:46:07 hpvectra kernel: fault code= supervisor write, page not present May 16 17:46:07 hpvectra kernel: instruction pointer= 0x20:0xc062c5e8 May 16 17:46:07 hpvectra kernel: stack pointer= 0x28:0xe5079c50 May 16 17:46:07 hpvectra kernel: frame pointer= 0x28:0xe5079c64 May 16 17:46:07 hpvectra kernel: code segment= base 0x0, limit 0xf, type 0x1b May 16 17:46:07 hpvectra kernel: = DPL 0, pres 1, def32 1, gran 1 May 16 17:46:07 hpvectra kernel: processor eflags= interrupt enabled, resume, IOPL = 0 May 16 17:46:07 hpvectra kernel: current process= 52 (vnlru) May 16 17:46:07 hpvectra kernel: trap number= 12 May 16 17:46:07 hpvectra kernel: panic: page fault May 16 17:46:07 hpvectra kernel: Uptime: 5d7h4m50s May 16 17:46:07 hpvectra kernel: Dumping 1023 MB (2 chunks) May 16 17:46:07 hpvectra kernel: chunk 0: 1MB (159 pages) ... ok May 16 17:46:07 hpvectra kernel: chunk 1: 1023MB (261872 pages) 1007 991 975 959 943 927 911 895 879 863 847 831 815 799 783 767 751 735 719 703 687 671 655 639 623 607 591 575 559 543 527 511 495 479 463 447 431 415 399 383 367 351 335 319 303 287 271 255 239 223 207 191 175 159 143 127 111 95 79 63 47 31 15 ... ok May 16 17:46:07 hpvectra kernel: May 16 17:46:07 hpvectra kernel: Dump complete May 16 17:46:07 hpvectra kernel: Automatic reboot in 15 seconds - press a key on the console to abort May 16 17:46:07 hpvectra kernel: Rebooting... The only thing I can see (read: understand) is: the process that caused the kernel panic is vnlru: vnlru flushes and frees vnodes when the system hits the kern.maxvnodes limit. This kernel thread sits mostly idle, and only activates if you have a huge amount of RAM and are accessing tens of thousands of tiny files. (from http://www.unixguide.net/freebsd/faq/10.31.shtml) So, consider increasing kern.maxvnodes if your system deals with such a huge amount of files. Thanks in advance, Hope this helps, Ron Thanks Pietro, I will do that. However I don't think 1GB of RAM is so big and as a home server I would be lucky to deal with more than a couple of hundred emails per day. I wouldn't trust in suppositions ;-) check whether vfs.maxvnodes (max vnodes allowed) minus vfs.numvnodes (number of actual vnodes) is nearly zero. So if anyone can shed any more light it will be appreaciated. Thanks Ron -- Pietro Cerutti icq #117293691 - ASCII Ribbon Campaign - against HTML e-mail and proprietary attachments www.asciiribbon.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Help to find cause of recurring crash
On Tue, 16 May 2006 21:09:20 +1000 fbsd [EMAIL PROTECTED] wrote: Hello All, I'm running a home email server and twice in the last week it has rebooted itself and been unable to restart due to corruption of the filesystem. I found the following in /var/log/messages May 16 17:46:07 hpvectra syslogd: kernel boot file is /boot/kernel/kernel May 16 17:46:07 hpvectra kernel: May 16 17:46:07 hpvectra kernel: May 16 17:46:07 hpvectra kernel: Fatal trap 12: page fault while in kernel mode May 16 17:46:07 hpvectra kernel: fault virtual address= 0x1c May 16 17:46:07 hpvectra kernel: fault code= supervisor write, page not present May 16 17:46:07 hpvectra kernel: instruction pointer= 0x20:0xc062c5e8 May 16 17:46:07 hpvectra kernel: stack pointer= 0x28:0xe5079c50 May 16 17:46:07 hpvectra kernel: frame pointer= 0x28:0xe5079c64 May 16 17:46:07 hpvectra kernel: code segment= base 0x0, limit 0xf, type 0x1b May 16 17:46:07 hpvectra kernel: = DPL 0, pres 1, def32 1, gran 1 May 16 17:46:07 hpvectra kernel: processor eflags= interrupt enabled, resume, IOPL = 0 May 16 17:46:07 hpvectra kernel: current process= 52 (vnlru) May 16 17:46:07 hpvectra kernel: trap number= 12 May 16 17:46:07 hpvectra kernel: panic: page fault May 16 17:46:07 hpvectra kernel: Uptime: 5d7h4m50s May 16 17:46:07 hpvectra kernel: Dumping 1023 MB (2 chunks) May 16 17:46:07 hpvectra kernel: chunk 0: 1MB (159 pages) ... ok May 16 17:46:07 hpvectra kernel: chunk 1: 1023MB (261872 pages) 1007 991 975 959 943 927 911 895 879 863 847 831 815 799 783 767 751 735 719 703 687 671 655 639 623 607 591 575 559 543 527 511 495 479 463 447 431 415 399 383 367 351 335 319 303 287 271 255 239 223 207 191 175 159 143 127 111 95 79 63 47 31 15 ... ok May 16 17:46:07 hpvectra kernel: May 16 17:46:07 hpvectra kernel: Dump complete May 16 17:46:07 hpvectra kernel: Automatic reboot in 15 seconds - press a key on the console to abort May 16 17:46:07 hpvectra kernel: Rebooting... When I turn on the monitor I see that the reboot has not been successful due to / was not properly dismounted and it is asking for fsck to be run manually. When I do that everything is fine again. You can save yourself some hassle by enabling fsck_y_enable=yes in /etc/rc.conf. If the initial fsck fails, it will try again with fsck -y. If that fails, you've got serious trouble. That will make the reboots a _little_ less of a problem for you, but it's only paint over the rust. What you really need to do is set up your system for kernel debugging: http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug.html This will allow you to collect enough information that a developer can help. However, before doing that, I would upgrade to 6.1, in case the problem has already been fixed. Additionally, FreeBSD is heavily tested enough that kernel panics are _usually_ the result of failing hardware. I'd get ahold of a memtest86 CD and test your RAM before doing much else. -- Bill Moran Collaborative Fusion Inc. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Help to find cause of recurring crash
Ron, Is this the HP Vectra server that has the onboard Adaptec SCSI controller, and are you running SCSI drives on it? If so, there's another guy that has one of these servers and was complaining about bugs in the adaptec driver sometime last year causing a similar issue. I told him to send-pr it but I don't think anything came of that. I would say you have a 80% chance it's what they call: non-compliant hardware It is well known that HP has a microcode license from Adaptec, they and Compaq have modified Adaptec's microcode before. It is really annoying when they do it and put their modded microcode into Adaptec's cards - I have had before on my desk, 2 identical Adaptec SCSI cards, that when both placed in a Compaq desktop will boot up with identical firmware version numbers with one exception - one of them has a trailing S on the firmware version number - and both work exactly the same in the Compaq, yet take the Adaptec card that was purchased from retail and put it in another system and it works fine, but take the adaptec card that was purchased from Compaq/HP spares and it will not work in any other system. It's enough to piss off an idiot. Ted -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of fbsd Sent: Tuesday, May 16, 2006 4:09 AM To: freebsd-questions@freebsd.org Subject: Help to find cause of recurring crash Hello All, I'm running a home email server and twice in the last week it has rebooted itself and been unable to restart due to corruption of the filesystem. I found the following in /var/log/messages May 16 17:46:07 hpvectra syslogd: kernel boot file is /boot/kernel/kernel May 16 17:46:07 hpvectra kernel: May 16 17:46:07 hpvectra kernel: May 16 17:46:07 hpvectra kernel: Fatal trap 12: page fault while in kernel mode May 16 17:46:07 hpvectra kernel: fault virtual address= 0x1c May 16 17:46:07 hpvectra kernel: fault code= supervisor write, page not present May 16 17:46:07 hpvectra kernel: instruction pointer= 0x20:0xc062c5e8 May 16 17:46:07 hpvectra kernel: stack pointer= 0x28:0xe5079c50 May 16 17:46:07 hpvectra kernel: frame pointer= 0x28:0xe5079c64 May 16 17:46:07 hpvectra kernel: code segment= base 0x0, limit 0xf, type 0x1b May 16 17:46:07 hpvectra kernel: = DPL 0, pres 1, def32 1, gran 1 May 16 17:46:07 hpvectra kernel: processor eflags= interrupt enabled, resume, IOPL = 0 May 16 17:46:07 hpvectra kernel: current process= 52 (vnlru) May 16 17:46:07 hpvectra kernel: trap number= 12 May 16 17:46:07 hpvectra kernel: panic: page fault May 16 17:46:07 hpvectra kernel: Uptime: 5d7h4m50s May 16 17:46:07 hpvectra kernel: Dumping 1023 MB (2 chunks) May 16 17:46:07 hpvectra kernel: chunk 0: 1MB (159 pages) ... ok May 16 17:46:07 hpvectra kernel: chunk 1: 1023MB (261872 pages) 1007 991 975 959 943 927 911 895 879 863 847 831 815 799 783 767 751 735 719 703 687 671 655 639 623 607 591 575 559 543 527 511 495 479 463 447 431 415 399 383 367 351 335 319 303 287 271 255 239 223 207 191 175 159 143 127 111 95 79 63 47 31 15 ... ok May 16 17:46:07 hpvectra kernel: May 16 17:46:07 hpvectra kernel: Dump complete May 16 17:46:07 hpvectra kernel: Automatic reboot in 15 seconds - press a key on the console to abort May 16 17:46:07 hpvectra kernel: Rebooting... When I turn on the monitor I see that the reboot has not been successful due to / was not properly dismounted and it is asking for fsck to be run manually. When I do that everything is fine again. Can anybody help me find the cause of the crash? What extra information is needed and how do I find that information? I'm relatively new to FreeBSD. Thanks in advance, Ron PS Other information that may be of help: I'm running 6.0 release, X is not running no users are logged in, cursor sits at the login screen running programs include, fetchmail daemon, dovecot, procmail, clamassassin, clamd, only strange behaviour noted is the following error messages May 11 03:02:51 hpvectra sendmail[5729]: NOQUEUE: SYSERR(root): readqf: cannot open ./dfk49H9AXd016830: No such file or directory May 11 03:02:51 hpvectra sendmail[5729]: NOQUEUE: SYSERR(root): readqf: cannot open ./dfk49H9Ahr016830: No such file or directory May 11 03:02:51 hpvectra sendmail[5729]: NOQUEUE: SYSERR(root): readqf: cannot open ./dfk49H9Amm016830: No such file or directory May 11 03:02:51 hpvectra sendmail[5729]: NOQUEUE: SYSERR(root): readqf: cannot open ./dfk49H9A5E016830: No such file or directory May 11 03:02:51 hpvectra sendmail[5729]: NOQUEUE: SYSERR(root): readqf: cannot open ./dfk49H9AHZ016830: No such file or directory May 11 03:02:51 hpvectra sendmail[5729]: NOQUEUE: SYSERR(root): readqf: cannot open ./dfk49Hlokm016830: No such file or directory May 11 03:02:51 hpvectra sendmail[5729]: NOQUEUE: SYSERR(root): readqf: cannot open ./dfk49HrgQC016830: No such file or directory May 11 03:02:51 hpvectra sendmail[5729]: NOQUEUE: SYSERR(root): readqf: cannot
Re: Help to find cause of recurring crash
Bill Moran wrote: On Tue, 16 May 2006 21:09:20 +1000 fbsd [EMAIL PROTECTED] wrote: Hello All, I'm running a home email server and twice in the last week it has rebooted itself and been unable to restart due to corruption of the filesystem. I found the following in /var/log/messages May 16 17:46:07 hpvectra syslogd: kernel boot file is /boot/kernel/kernel May 16 17:46:07 hpvectra kernel: May 16 17:46:07 hpvectra kernel: May 16 17:46:07 hpvectra kernel: Fatal trap 12: page fault while in kernel mode May 16 17:46:07 hpvectra kernel: fault virtual address= 0x1c May 16 17:46:07 hpvectra kernel: fault code= supervisor write, page not present May 16 17:46:07 hpvectra kernel: instruction pointer= 0x20:0xc062c5e8 May 16 17:46:07 hpvectra kernel: stack pointer= 0x28:0xe5079c50 May 16 17:46:07 hpvectra kernel: frame pointer= 0x28:0xe5079c64 May 16 17:46:07 hpvectra kernel: code segment= base 0x0, limit 0xf, type 0x1b May 16 17:46:07 hpvectra kernel: = DPL 0, pres 1, def32 1, gran 1 May 16 17:46:07 hpvectra kernel: processor eflags= interrupt enabled, resume, IOPL = 0 May 16 17:46:07 hpvectra kernel: current process= 52 (vnlru) May 16 17:46:07 hpvectra kernel: trap number= 12 May 16 17:46:07 hpvectra kernel: panic: page fault May 16 17:46:07 hpvectra kernel: Uptime: 5d7h4m50s May 16 17:46:07 hpvectra kernel: Dumping 1023 MB (2 chunks) May 16 17:46:07 hpvectra kernel: chunk 0: 1MB (159 pages) ... ok May 16 17:46:07 hpvectra kernel: chunk 1: 1023MB (261872 pages) 1007 991 975 959 943 927 911 895 879 863 847 831 815 799 783 767 751 735 719 703 687 671 655 639 623 607 591 575 559 543 527 511 495 479 463 447 431 415 399 383 367 351 335 319 303 287 271 255 239 223 207 191 175 159 143 127 111 95 79 63 47 31 15 ... ok May 16 17:46:07 hpvectra kernel: May 16 17:46:07 hpvectra kernel: Dump complete May 16 17:46:07 hpvectra kernel: Automatic reboot in 15 seconds - press a key on the console to abort May 16 17:46:07 hpvectra kernel: Rebooting... When I turn on the monitor I see that the reboot has not been successful due to / was not properly dismounted and it is asking for fsck to be run manually. When I do that everything is fine again. You can save yourself some hassle by enabling fsck_y_enable=yes in /etc/rc.conf. If the initial fsck fails, it will try again with fsck -y. If that fails, you've got serious trouble. That will make the reboots a _little_ less of a problem for you, but it's only paint over the rust. What you really need to do is set up your system for kernel debugging: http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug.html This will allow you to collect enough information that a developer can help. However, before doing that, I would upgrade to 6.1, in case the problem has already been fixed. Additionally, FreeBSD is heavily tested enough that kernel panics are _usually_ the result of failing hardware. I'd get ahold of a memtest86 CD and test your RAM before doing much else. Good tip Bill re fsck. I'll do that. I'll also upgrade and run memtest. Ron ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Help to find cause of recurring crash
Ted Mittelstaedt wrote: Ron, Is this the HP Vectra server that has the onboard Adaptec SCSI controller, and are you running SCSI drives on it? If so, there's another guy that has one of these servers and was complaining about bugs in the adaptec driver sometime last year causing a similar issue. I told him to send-pr it but I don't think anything came of that. I would say you have a 80% chance it's what they call: non-compliant hardware It is well known that HP has a microcode license from Adaptec, they and Compaq have modified Adaptec's microcode before. It is really annoying when they do it and put their modded microcode into Adaptec's cards - I have had before on my desk, 2 identical Adaptec SCSI cards, that when both placed in a Compaq desktop will boot up with identical firmware version numbers with one exception - one of them has a trailing S on the firmware version number - and both work exactly the same in the Compaq, yet take the Adaptec card that was purchased from retail and put it in another system and it works fine, but take the adaptec card that was purchased from Compaq/HP spares and it will not work in any other system. It's enough to piss off an idiot. Ted -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of fbsd Sent: Tuesday, May 16, 2006 4:09 AM To: freebsd-questions@freebsd.org Subject: Help to find cause of recurring crash Hello All, I'm running a home email server and twice in the last week it has rebooted itself and been unable to restart due to corruption of the filesystem. I found the following in /var/log/messages May 16 17:46:07 hpvectra syslogd: kernel boot file is /boot/kernel/kernel May 16 17:46:07 hpvectra kernel: May 16 17:46:07 hpvectra kernel: May 16 17:46:07 hpvectra kernel: Fatal trap 12: page fault while in kernel mode May 16 17:46:07 hpvectra kernel: fault virtual address= 0x1c May 16 17:46:07 hpvectra kernel: fault code= supervisor write, page not present May 16 17:46:07 hpvectra kernel: instruction pointer= 0x20:0xc062c5e8 May 16 17:46:07 hpvectra kernel: stack pointer= 0x28:0xe5079c50 May 16 17:46:07 hpvectra kernel: frame pointer= 0x28:0xe5079c64 May 16 17:46:07 hpvectra kernel: code segment= base 0x0, limit 0xf, type 0x1b May 16 17:46:07 hpvectra kernel: = DPL 0, pres 1, def32 1, gran 1 May 16 17:46:07 hpvectra kernel: processor eflags= interrupt enabled, resume, IOPL = 0 May 16 17:46:07 hpvectra kernel: current process= 52 (vnlru) May 16 17:46:07 hpvectra kernel: trap number= 12 May 16 17:46:07 hpvectra kernel: panic: page fault May 16 17:46:07 hpvectra kernel: Uptime: 5d7h4m50s May 16 17:46:07 hpvectra kernel: Dumping 1023 MB (2 chunks) May 16 17:46:07 hpvectra kernel: chunk 0: 1MB (159 pages) ... ok May 16 17:46:07 hpvectra kernel: chunk 1: 1023MB (261872 pages) 1007 991 975 959 943 927 911 895 879 863 847 831 815 799 783 767 751 735 719 703 687 671 655 639 623 607 591 575 559 543 527 511 495 479 463 447 431 415 399 383 367 351 335 319 303 287 271 255 239 223 207 191 175 159 143 127 111 95 79 63 47 31 15 ... ok May 16 17:46:07 hpvectra kernel: May 16 17:46:07 hpvectra kernel: Dump complete May 16 17:46:07 hpvectra kernel: Automatic reboot in 15 seconds - press a key on the console to abort May 16 17:46:07 hpvectra kernel: Rebooting... When I turn on the monitor I see that the reboot has not been successful due to / was not properly dismounted and it is asking for fsck to be run manually. When I do that everything is fine again. Can anybody help me find the cause of the crash? What extra information is needed and how do I find that information? I'm relatively new to FreeBSD. Thanks in advance, Ron PS Other information that may be of help: I'm running 6.0 release, X is not running no users are logged in, cursor sits at the login screen running programs include, fetchmail daemon, dovecot, procmail, clamassassin, clamd, only strange behaviour noted is the following error messages May 11 03:02:51 hpvectra sendmail[5729]: NOQUEUE: SYSERR(root): readqf: cannot open ./dfk49H9AXd016830: No such file or directory May 11 03:02:51 hpvectra sendmail[5729]: NOQUEUE: SYSERR(root): readqf: cannot open ./dfk49H9Ahr016830: No such file or directory May 11 03:02:51 hpvectra sendmail[5729]: NOQUEUE: SYSERR(root): readqf: cannot open ./dfk49H9Amm016830: No such file or directory May 11 03:02:51 hpvectra sendmail[5729]: NOQUEUE: SYSERR(root): readqf: cannot open ./dfk49H9A5E016830: No such file or directory May 11 03:02:51 hpvectra sendmail[5729]: NOQUEUE: SYSERR(root): readqf: cannot open ./dfk49H9AHZ016830: No such file or directory May 11 03:02:51 hpvectra sendmail[5729]: NOQUEUE: SYSERR(root): readqf: cannot open ./dfk49Hlokm016830: No such file or directory May 11 03:02:51 hpvectra sendmail[5729]: NOQUEUE: SYSERR(root): readqf: cannot open ./dfk49HrgQC016830: No such file or directory May 11 03:02:51 hpvectra sendmail[5729]: NOQUEUE:
