From owner-freebsd-current@FreeBSD.ORG  Sun Dec 11 01:55:01 2005
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 DC0E716A427;
	Sun, 11 Dec 2005 01:55:00 +0000 (GMT)
	(envelope-from davidxu@freebsd.org)
Message-ID: <439B8711.2090501@freebsd.org>
Date: Sun, 11 Dec 2005 09:55:29 +0800
From: David Xu <davidxu@freebsd.org>
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: Pascal Hofstee <caelian@gmail.com>
References: <20051209175607.C23668@maildrop.int.zabbadoz.net>
	<1134240701.767.3.camel@synergy.odyssey.homeunix.org>
In-Reply-To: <1134240701.767.3.camel@synergy.odyssey.homeunix.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net>,
	FreeBSD current mailing list <current@freebsd.org>
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
	<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: Sun, 11 Dec 2005 01:55:01 -0000

Pascal Hofstee wrote:

>On Fri, 2005-12-09 at 20:28 +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.
>>    
>>
>
>Just thought i'd say that this patch also makes the onboard nve chip on
>my EPOX 9NDA3+ (likely the same chip as David Xu's 9NDA3J board).
>
>I still get the occasional sputter of an nve0 device timeout(x) though x
>seems to be a constant "1" .. instead of the typical climbing towards 64
>i have seen happening on other nve-boards.
>
>  
>
Yes, I occasionally got timeout(x) too, annoyance is machine is stalled
when the driver is resetting the device, I can not move mouse and type in
key, can this be avoided ?