From owner-freebsd-current@FreeBSD.ORG Thu Nov 17 20:46:59 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1140F16A41F; Thu, 17 Nov 2005 20:46:59 +0000 (GMT) (envelope-from gallatin@cs.duke.edu) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6132643D5C; Thu, 17 Nov 2005 20:46:53 +0000 (GMT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.13.4/8.13.4) with ESMTP id jAHKkjsn004777 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 17 Nov 2005 15:46:45 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.12.9p2/8.12.9/Submit) id jAHKkQQR058115; Thu, 17 Nov 2005 15:46:26 -0500 (EST) (envelope-from gallatin) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17276.60450.831340.357584@grasshopper.cs.duke.edu> Date: Thu, 17 Nov 2005 15:46:26 -0500 (EST) To: Matthew Dillon In-Reply-To: <200511171858.jAHIwOoc006061@apollo.backplane.com> References: <20051117010651.97608.qmail@web50303.mail.yahoo.com> <20051117143322.lvz347pzkcg480co@netchild.homeip.net> <200511171135.53903.jhb@freebsd.org> <200511171858.jAHIwOoc006061@apollo.backplane.com> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Cc: alan bryan , FreeBSD current mailing list , freebsd-current@freebsd.org, "Bjoern A. Zeeb" , Alexander Leidinger Subject: Re: [PATCH] nve(4) locking cleanup 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: Thu, 17 Nov 2005 20:46:59 -0000 I have a pair of DFI Nforce-4 based "NF4 ultra" boards, where the FreeBSD driver will never pass any traffic at all (and never has). Matthew Dillon writes: > At this point I believe that the remaining problems are entirely within > Nvidia's nvnet object module. I don't think there is anything we can do > about it short of NVidia coming out with an update (which isn't likely). At least on my boards, the Solaris "nfo" driver from http://homepage2.nifty.com/mrym3/taiyodo/eng works flawlessly. The object file they use has the same checksum as the one used by the FreeBSD driver. Note that this is at 100Mb/s speeds, and is used for NFS (client), and ssh sessions only. I haven't tried really hard to beat the snot out of it, but it has worked for months without me seeing a problem in daily use. > Now, linux *has* a native implementation of this driver that does not > use the Nvidia module, and I have gotten reports that it does not suffer > from the same problems. I'm working on a linux driver right now, and have enabled the the linux slab debugging stuff (similar to the type of malloc debugging we get with INVARIANTS). At boot (before I even load my driver), the forcedeth driver from 2.6.13.1 will receive corrupted frames. Anybody porting that driver should look out for buffer over/under flow issues in it... Drew