Date: Wed, 11 Apr 2018 17:19:18 +0200 From: Alex Dupre <ale@FreeBSD.org> To: gljennjohn@gmail.com, hackers@freebsd.org Subject: Re: Realtek re(4) driver Message-ID: <c46e7216-0d22-d7d5-0452-75178a74dd46@FreeBSD.org> In-Reply-To: <20180411155432.78b23bbe@ernst.home> References: <CAA3ZYrCdBWi%2BXSge%2BYfDH73a5QpaK0oOVTABb2k16NA5xUx%2BdA@mail.gmail.com> <f76f167d-c37f-3673-11c3-094a3fb13186@multiplay.co.uk> <20180411121404.71a07fef@ernst.home> <8919d821-2200-a2aa-87c3-bcad16bc75fb@systella.fr> <20180411104533.GC1134@albert.catwhisker.org> <17a3825a-03f4-0760-8d4f-1ce28a48cfdd@FreeBSD.org> <20180411155432.78b23bbe@ernst.home>
next in thread | previous in thread | raw e-mail | index | archive | help
Gary Jennejohn wrote: > Reading the bugzilla shows that this is a comples problem with no > obvious error source. > > One poster notes that he could transfer 300+GB of data error-free > using rsync, but with NFS he encountered problesm after a few GB. > To me this is an indictment of the NFS implementation used and > not of the re driver itself. I agree that is a complex problem with a non obvious solution, I have also used many re cards successfully and others not, but surely it's not a NFS issue. I can tell you more, I've used successfully a re card for years, and started seeing issues with the same card after upgrading my upstream connection to gigabit. The only thing that link all bug reports (and there are tons) is the use of re card sustaining gigabit (duplex) transfers. And I couldn't find similar reports for other chipsets that might lead to think it's a generic FreeBSD issue. Everything is possible, but the main suspect is the re driver. -- Alex Dupre
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?c46e7216-0d22-d7d5-0452-75178a74dd46>