From owner-freebsd-current@FreeBSD.ORG Fri Dec 9 22:26:12 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from [127.0.0.1] (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 0B48316A41F; Fri, 9 Dec 2005 22:26:11 +0000 (GMT) (envelope-from davidxu@freebsd.org) Message-ID: <439A049E.9020907@freebsd.org> Date: Sat, 10 Dec 2005 06:26:38 +0800 From: David Xu User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.7.10) Gecko/20050806 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Bjoern A. Zeeb" References: <20051209175607.C23668@maildrop.int.zabbadoz.net> In-Reply-To: <20051209175607.C23668@maildrop.int.zabbadoz.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: FreeBSD current mailing list Subject: Re: nve(4) patch - please test! 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: Fri, 09 Dec 2005 22:26:12 -0000 Bjoern A. Zeeb wrote: > Hi, > > everyone out there who had only seen timeouts like > nve0: device timeout (4) > on nve and __never got it working at all__ please try this patch[1] > which made my nve working from 0 to 99. > > I still can get timeouts by for example flood pinging another machine > on the local LAN but it all recovers on it's own and I can work on > that machine and do things like find / over ssh without losing > connectivity. Fixing the timeouts will be another problem that needs > to be addressed later. > > Greetings > Bjoern A. Zeeb > > > [1] http://sources.zabbadoz.net/freebsd/patchset/nve-20051209-01.diff It saves the nve on my EPOX 9nda3j board! it is a NForce3 250 GB, it is working now, oh, you are my hero! David Xu