From owner-freebsd-current@FreeBSD.ORG Sun Oct 19 22:27:02 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BDCB11065679 for ; Sun, 19 Oct 2008 22:27:02 +0000 (UTC) (envelope-from wjw@digiware.nl) Received: from mail.digiware.nl (www.tegenbosch28.nl [217.21.251.97]) by mx1.freebsd.org (Postfix) with ESMTP id 736668FC13 for ; Sun, 19 Oct 2008 22:27:02 +0000 (UTC) (envelope-from wjw@digiware.nl) Received: from localhost (localhost.digiware.nl [127.0.0.1]) by mail.digiware.nl (Postfix) with ESMTP id 1B64B174CD; Mon, 20 Oct 2008 00:27:01 +0200 (CEST) X-Virus-Scanned: amavisd-new at digiware.nl Received: from mail.digiware.nl ([127.0.0.1]) by localhost (rack1.digiware.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hg1SJZJGXN-p; Mon, 20 Oct 2008 00:26:55 +0200 (CEST) Received: from [192.168.2.10] (vaio [192.168.2.10]) by mail.digiware.nl (Postfix) with ESMTP id CAD4817498; Mon, 20 Oct 2008 00:26:54 +0200 (CEST) Message-ID: <48FBB431.4090102@digiware.nl> Date: Mon, 20 Oct 2008 00:26:57 +0200 From: Willem Jan Withagen Organization: Digiware Management User-Agent: Thunderbird 2.0.0.17 (Windows/20080914) MIME-Version: 1.0 To: Steve Kargl References: <48F90FC1.3040503@digiware.nl> <20081018002133.GA36113@troutmask.apl.washington.edu> In-Reply-To: <20081018002133.GA36113@troutmask.apl.washington.edu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Sun, 19 Oct 2008 23:03:11 +0000 Cc: current@freebsd.org Subject: Re: Freezing or stalling current system 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: Sun, 19 Oct 2008 22:27:02 -0000 Steve Kargl wrote: > On Sat, Oct 18, 2008 at 12:20:49AM +0200, Willem Jan Withagen wrote: >> I'm sort of assuming that the bge0: timeouts and coalesced links are due >> to the freezing. >> > > Does the following help? > Just a little... It now takes a little longer for the system to freeze, but eventally it will. The coalesced messages did not return. Just out of curiosity is also plugged in an fxp-card. And there it takes even longer for the system to freeze, but in the end it does freeze. The "funny" part is it once in a while is revivable by going into the kernel-debugger and then just continue. Sometimes a long wait (10 sec) will suffice, during which there is no keyboard response what so ever. But on other instances the system is dead in the water, and only a hardware reset gets it back. Something I'm still wondering if this only is with NFS traffic, or with all other types of network traffic. But I haven't tested thids. --WjW