Date: Wed, 11 Apr 2018 10:35:29 -0400 From: Mike Tancsa <mike@sentex.net> To: "Rodney W. Grimes" <freebsd-rwg@pdx.rh.CN85.dnsmgr.net>, Alex Dupre <ale@freebsd.org> Cc: =?UTF-8?Q?BERTRAND_Jo=c3=abl?= <joel.bertrand@systella.fr>, hackers@freebsd.org Subject: Re: Realtek re(4) driver Message-ID: <74f139e0-4e6b-6efb-eff2-752997dce3b0@sentex.net> In-Reply-To: <201804111412.w3BECXhb028056@pdx.rh.CN85.dnsmgr.net> References: <201804111412.w3BECXhb028056@pdx.rh.CN85.dnsmgr.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 4/11/2018 10:12 AM, Rodney W. Grimes wrote: >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724 > > I have put that bug back on a public bug list (net@freebsd.org) so > that it appears in the nag mails sent out periodically. > > I think I might have some of that hardware around here, but not sure > if it is that specific chip. I do know that some "re(4)" cards > work just fine with FreeBSD, but others have issues, I suspect the > ones that have issues are ones that have hardware bugs that need > a specific software work around. Over the years I have had mixed results with re nics. Some work as expected, others with issues. I think a big part of the problem is that there are so many varieties out there. That being said, I run into similar issues on Linux from time to time with these NICs, so its not just a FreeBSD problem. Just the other week, on a new MSI RYZEN board (MS-7A34), I found I could wedge the onboard NIC without too much effort doing some network stress tests. (kernel is 4.4.0-119). Havent tried this board on FreeBSD however. ---Mike -- ------------------- Mike Tancsa, tel +1 519 651 3400 x203 Sentex Communications, mike@sentex.net Providing Internet services since 1994 www.sentex.net Cambridge, Ontario Canada
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?74f139e0-4e6b-6efb-eff2-752997dce3b0>