From owner-freebsd-questions@FreeBSD.ORG Mon Jun 25 13:50:45 2007 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 229D816A421 for ; Mon, 25 Jun 2007 13:50:45 +0000 (UTC) (envelope-from freebsd-questions-local@be-well.ilk.org) Received: from mail1.sea5.speakeasy.net (mail1.sea5.speakeasy.net [69.17.117.3]) by mx1.freebsd.org (Postfix) with ESMTP id 0152413C45A for ; Mon, 25 Jun 2007 13:50:44 +0000 (UTC) (envelope-from freebsd-questions-local@be-well.ilk.org) Received: (qmail 4641 invoked from network); 25 Jun 2007 13:50:44 -0000 Received: from dsl092-078-145.bos1.dsl.speakeasy.net (HELO be-well.ilk.org) ([66.92.78.145]) (envelope-sender ) by mail1.sea5.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 25 Jun 2007 13:50:43 -0000 Received: by be-well.ilk.org (Postfix, from userid 1147) id 9F64A28444; Mon, 25 Jun 2007 09:50:42 -0400 (EDT) To: "SigmaX asdf" References: From: Lowell Gilbert Date: Mon, 25 Jun 2007 09:50:42 -0400 In-Reply-To: (SigmaX asdf's message of "Sun\, 24 Jun 2007 17\:44\:38 -0400") Message-ID: <448xa8gn2l.fsf@be-well.ilk.org> User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.99 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: freebsd-questions@freebsd.org Subject: Re: Regular Freezes X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-questions@freebsd.org List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Jun 2007 13:50:45 -0000 "SigmaX asdf" writes: > My FreeBSD 6.1 gateway box keeps freezing totally. It seems to happen > when there's a large burst of network traffic on my internal interface > (i.e. download, flash movie, I-radio). > > I've already done a memtest, and it came out clean. Any ideas as to > what logs might help me trouble shoot? I'd still estimate that hardware is more likely than not to be the cause of the problem; perhaps a power issue. If you can get the kernel to dump into the debugger after the freeze, that would be a big help. You didn't mention what kind of Ethernet hardware is involved, but you could search for past problems that others may have had. Even on my fairly low-volume home servers (and firewall), I have found that low-quality Ethernet hardware has caused a lot of problems...