From owner-freebsd-questions@FreeBSD.ORG Fri Dec 2 21:38:59 2005 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 61A4316A41F for ; Fri, 2 Dec 2005 21:38:59 +0000 (GMT) (envelope-from LukeD@pobox.com) Received: from thorn.pobox.com (vds.fauxbox.com [208.210.124.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2F95443D5F for ; Fri, 2 Dec 2005 21:38:56 +0000 (GMT) (envelope-from LukeD@pobox.com) Received: from thorn (localhost [127.0.0.1]) by thorn.pobox.com (Postfix) with ESMTP id 056D2B1 for ; Fri, 2 Dec 2005 16:39:18 -0500 (EST) Received: from pool-71-112-205-160.sttlwa.dsl-w.verizon.net (pool-71-112-205-160.sttlwa.dsl-w.verizon.net [71.112.205.160]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by thorn.sasl.smtp.pobox.com (Postfix) with ESMTP id 8E81C16BD for ; Fri, 2 Dec 2005 16:39:17 -0500 (EST) Date: Fri, 2 Dec 2005 13:38:49 -0800 (PST) From: Luke Dean X-X-Sender: lukas@border.crystalsphere.multiverse To: freebsd-questions@freebsd.org Message-ID: <20051202132504.T782@border.crystalsphere.multiverse> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Subject: Troubleshooting a lockup X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Luke Dean List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Dec 2005 21:38:59 -0000 I run a headless machine that has sporadic lockup problems, and I need some advice on what I can do to gather enough information to give me some idea of what's causing it. The machine acts as a router, DNS, web server, mail server, nfs server, firewall, and lots of other services. These problems started occurring after I upgraded from FreeBSD 5.4 to 6.0 and installed a secondary hard drive controller. Before that it ran perfectly for months at a time. That's a lot of variables to rule out. When the lockups occur, both network interfaces just plain die. Also, if I bring over a monitor and plug it in, I can't get a video signal, even if I tap the keyboard to wake it up. The lights on the keyboard still work, so I don't believe the box is completely frozen. The only option I have is to hit the reset button. Inspection of /var/log/messages never gives me any clues, except for one time I saw one message about my rl0 interface getting a watchdog timeout, but that was only one time and I can't imagine why a failure on one network interface would cause both network interfaces to stop responding. Inspection of the httpd logs just gives me an idea of about what time the lockup occurred, since there's no activity after that point. I don't know of any other log files that might be of assistance. I thought about trying to configure a dump device, but I don't believe the machine is panicing, except perhaps when I hit the reset button. I may try to figure out some way to disable the power management on the video, hook up a monitor, and leave "top" running on it to see if that gives me any clues. I plan on googling for "serial terminal" this afternoon. Any other suggestions?