Date: Tue, 24 Apr 2018 10:34:49 +0200 From: Joerg Sonnenberger <joerg@bec.de> To: freebsd-hackers@freebsd.org, hackers@freebsd.org Subject: Re: Realtek re(4) driver Message-ID: <20180424083449.GB11959@britannica.bec.de> In-Reply-To: <17a3825a-03f4-0760-8d4f-1ce28a48cfdd@FreeBSD.org> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Apr 11, 2018 at 12:51:09PM +0200, Alex Dupre wrote: > David Wolfskill wrote: > >> I use a diskless workstation. With re driver provided by FreeBSD kernel > >> (9/10/11.x), system randomly crashed because ethernet driver stalls (and > >> datarate is always less than 300mbps). With official realtek driver > >> (v194.01), system now runs as expected (with datarate up to 1 Gbps). > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724 > > Anyone interested in taking the bounty or contributing to it? Perhaps > the FreeBSD Foundation should jump in? A starting point would be: (1) what hardware offload features are enabled (2) whether a specific direction is the problem (3) correlate traffic on both ends, i.e. what packets are dropped "on the wire" The most likely cause of any problem here is a missing workaround for a hardware bug or Realtek deciding that some specific tuning is necessary for certain chips. It is nearly impossible to fix this kind of bugs without having access to the hardware and a way to reproduce it. Comparing with a working driver might be possible, but it is extremely tideous. Joerg
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20180424083449.GB11959>