On Thu, Mar 18, 2004 at 06:53:38PM -0500, Small, Jim wrote: > I've tried only using one NIC that doesn't share any IRQs (no bridging or > shared interrupts). Like I said, this box ran for months without locking > running BSD/OS. What could be causing it to hard lock? > > Is there some kernel option I can use to help debug the problem? Are there > any troublesome modules I should eliminate? You could try enabling the sysreq key. That is, in /etc/sysctl.conf, set this: # Controls the System Request debugging functionality of the kernel kernel.sysrq = 1 then run "sysctl -p" Then, when the system hangs, on the console hit 'alt-prntscrn-P' to see where the processors are locked. alt-prntscrn-H will show you other commands you might want to try. A serial console is needed to collect or view all the output. Setting NMI watchdog could also be helpful. Do that by putting "nmi_watchdog=1" in the options of the kernel line in grub.conf. The system should oops if it locks up. -- Norman Gaywood, Systems Administrator School of Mathematics, Statistics and Computer Science University of New England, Armidale, NSW 2351, Australia norm@xxxxxxxxxxxxxxxxx Phone: +61 (0)2 6773 2412 http://turing.une.edu.au/~norm Fax: +61 (0)2 6773 3312 Please avoid sending me Word or PowerPoint attachments. See http://www.fsf.org/philosophy/no-word-attachments.html
