Date: Thu, 17 Nov 2005 15:46:26 -0500 (EST) From: Andrew Gallatin <gallatin@cs.duke.edu> To: Matthew Dillon <dillon@apollo.backplane.com> Cc: alan bryan <alanbryan1234@yahoo.com>, FreeBSD current mailing list <current@freebsd.org>, freebsd-current@freebsd.org, "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net>, Alexander Leidinger <Alexander@leidinger.net> Subject: Re: [PATCH] nve(4) locking cleanup Message-ID: <17276.60450.831340.357584@grasshopper.cs.duke.edu> In-Reply-To: <200511171858.jAHIwOoc006061@apollo.backplane.com> References: <20051117010651.97608.qmail@web50303.mail.yahoo.com> <Pine.BSF.4.53.0511171134430.80787@e0-0.zab2.int.zabbadoz.net> <20051117143322.lvz347pzkcg480co@netchild.homeip.net> <200511171135.53903.jhb@freebsd.org> <200511171858.jAHIwOoc006061@apollo.backplane.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?17276.60450.831340.357584>