Re: 5.1-CURRENT rebooting (multile systems) -- How to troubleshoot?
On Sat, 18 Oct 2003, Tom Parquette wrote: My question is, if the system fails (I'm assuming these are panics) how do I get the machine to NOT automatically reboot so I can copy down the failure information? (Unless these are logged somewhere I have not found yet.) Try hooking up a serial console and logging a system run with boot -v, overnight. Make sure that you have all of the kernel debug options in GENERIC in your kernel as they will provide insight that can help trace the problem. Regards, Andre Guibert de Bruet | Enterprise Software Consultant Silicon Landmark, LLC. | http://siliconlandmark.com/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.1-CURRENT rebooting (multile systems) -- How to troubleshoot?
Andre Guibert de Bruet wrote: On Sat, 18 Oct 2003, Tom Parquette wrote: My question is, if the system fails (I'm assuming these are panics) how do I get the machine to NOT automatically reboot so I can copy down the failure information? (Unless these are logged somewhere I have not found yet.) Try hooking up a serial console and logging a system run with boot -v, overnight. Make sure that you have all of the kernel debug options in GENERIC in your kernel as they will provide insight that can help trace the problem. Additionally, set your kernel up for debugging. This will allow you to get a great deal of information after a crash. This section of the developer's handbook will talk you through it: http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug.html -- Bill Moran Potential Technologies http://www.potentialtech.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
5.1-CURRENT rebooting (multile systems) -- How to troubleshoot?
Hi. This is the third time I've tried to write this Email. Things keep failing out from under me. This did not happen before I cvsuped Oct 14 to get around the -pthread problem with ports. Either my server (I NFS mount /home from the server machine) or the desktop machine have failed unpredictably multiple times. Sometimes under load, sometimes it appears they fail overnight when only setiathome is running on them. They are dual processor Athlon machines. I have not seen any messages from any of these failures. I have seen one failure on the server that indiated a page fault in kernel mode. I didn't write all of the information down because I thought it would be logged in one of the logs. Wrong again idiot!! I do not have any doc on these and generic searches didn't turn up anything I can hang my hat on. My question is, if the system fails (I'm assuming these are panics) how do I get the machine to NOT automatically reboot so I can copy down the failure information? (Unless these are logged somewhere I have not found yet.) I'm frustrated because I cannot get any information on the failures to even begin to formulate a sane posting to the list. Sorry for the rambling posting. I'm venting a little. I'm used to fixing mainframe system software. I am still trying to learn the skills on my own for FreeBSD. TIA for any help. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.1-CURRENT rebooting (multile systems) -- How to troubleshoot?
* Tom Parquette ([EMAIL PROTECTED]) wrote: My question is, if the system fails (I'm assuming these are panics) how do I get the machine to NOT automatically reboot so I can copy down the failure information? (Unless these are logged somewhere I have not found yet.) You can make the system wait for a key press instead of rebooting. options PANIC_REBOOT_WAIT_TIME=-1 see /sys/conf/NOTES -- Giovanni P. Tirloni gpt at tirloni.org Fingerprint: 8C3F BEC5 79BD 3E9B EDB8 72F4 16E8 BA5E D031 5C26 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
