From owner-freebsd-current@FreeBSD.ORG Tue Nov 3 00:23:03 2009 Return-Path: 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 DFE87106566C for ; Tue, 3 Nov 2009 00:23:03 +0000 (UTC) (envelope-from freebsd-current@m.gmane.org) Received: from lo.gmane.org (lo.gmane.org [80.91.229.12]) by mx1.freebsd.org (Postfix) with ESMTP id 9A6FD8FC1E for ; Tue, 3 Nov 2009 00:23:03 +0000 (UTC) Received: from list by lo.gmane.org with local (Exim 4.50) id 1N57Ap-0000xJ-1k for freebsd-current@freebsd.org; Tue, 03 Nov 2009 01:22:59 +0100 Received: from 78-1-134-182.adsl.net.t-com.hr ([78.1.134.182]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 03 Nov 2009 01:22:59 +0100 Received: from ivoras by 78-1-134-182.adsl.net.t-com.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 03 Nov 2009 01:22:59 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-current@freebsd.org From: Ivan Voras Date: Tue, 03 Nov 2009 01:22:35 +0100 Lines: 25 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: 78-1-134-182.adsl.net.t-com.hr User-Agent: Thunderbird 2.0.0.21 (X11/20090612) In-Reply-To: Sender: news 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Nov 2009 00:23:04 -0000 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. Good luck!