From owner-freebsd-current@FreeBSD.ORG  Tue Nov  3 01:02:12 2009
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id C9ECB106566C
	for <freebsd-current@freebsd.org>; Tue,  3 Nov 2009 01:02:12 +0000 (UTC)
	(envelope-from weldon@excelsusphoto.com)
Received: from mx0.excelsus.net (emmett.excelsus.com [74.93.113.252])
	by mx1.freebsd.org (Postfix) with ESMTP id B8BE58FC15
	for <freebsd-current@freebsd.org>; Tue,  3 Nov 2009 01:02:11 +0000 (UTC)
Received: (qmail 2224 invoked by uid 89); 3 Nov 2009 01:02:08 -0000
Received: from unknown (HELO localhost) (127.0.0.1)
	by localhost.excelsus.com with SMTP; 3 Nov 2009 01:02:08 -0000
Date: Mon, 2 Nov 2009 20:02:08 -0500 (EST)
From: Weldon S Godfrey 3 <weldon@excelsusphoto.com>
X-X-Sender: weldon@emmett.excelsus.com
To: Ivan Voras <ivoras@freebsd.org>
In-Reply-To: <hcnt4c$12i$1@ger.gmane.org>
Message-ID: <alpine.BSF.2.00.0911021952220.1264@emmett.excelsus.com>
References: <alpine.BSF.2.00.0911020747560.80499@emmett.excelsus.com>
	<hcnt4c$12i$1@ger.gmane.org>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Mailman-Approved-At: Tue, 03 Nov 2009 02:42:56 +0000
Cc: freebsd-current@freebsd.org
Subject: Re: FreeBSD 8.0 - network stack crashes?
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 03 Nov 2009 01:02:12 -0000

If memory serves me right, sometime around Tomorrow, Ivan Voras told me:

> Weldon S Godfrey 3 wrote:
>
>> I don't know how to troubleshoot this further on the server since I am not 
>> getting any problems indicated in logging, panics, cores, etc.
>
> If you have console access to the system, the generic advice would be to 
> compile a kernel with the kernel debugger - options KDB and DDB (see 
> http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug-online-ddb.html), 
> enter the debugger, force a kernel dump file to be created (by entering "call 
> doadump") and then proceed with post-mortem examination of the kernel at your 
> leisure (e.g. from a remote ssh console, etc).
>
> See 
> http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug-deadlocks.html 
> for instructions on what information to collect.
>
> If you can provoke your problem with using WITNESS that would probably be 
> great, but it will slow down your production machine noticeably. When WITNESS 
> is enabled you might also get more information - such as LOR warnings, which 
> you should also collect.
>
> Keep the dump file, someone might ask you for more information.
>

Thanks, I will work on trying to get a system with those enabled.

Another thought that came to mind that this sounds like some sort of 
network buffer exhaustion. Is there anything to look for there?