Date: Sun, 11 Dec 2005 09:55:29 +0800 From: David Xu <davidxu@freebsd.org> To: Pascal Hofstee <caelian@gmail.com> Cc: "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net>, FreeBSD current mailing list <current@freebsd.org> Subject: Re: nve(4) patch - please test! Message-ID: <439B8711.2090501@freebsd.org> In-Reply-To: <1134240701.767.3.camel@synergy.odyssey.homeunix.org> References: <20051209175607.C23668@maildrop.int.zabbadoz.net> <1134240701.767.3.camel@synergy.odyssey.homeunix.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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 ?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?439B8711.2090501>