Date: Sat, 27 Apr 2019 11:13:04 +0000 From: bugzilla-noreply@freebsd.org To: net@FreeBSD.org Subject: [Bug 236962] Realtek RTL8111/8168/8411 erratically drops network connection Message-ID: <bug-236962-7501-cNFCKE7tsG@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-236962-7501@https.bugs.freebsd.org/bugzilla/> References: <bug-236962-7501@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D236962 Konstantin Belousov <kib@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kib@FreeBSD.org --- Comment #6 from Konstantin Belousov <kib@FreeBSD.org> --- Some time ago I started using https://www.gigabyte.com/Motherboard/GA-J3455N-D3H-rev-10#ov for my home server. In-tree driver stops operating with dreaded 'device timeout', and the official realtek driver caused some weird hangs of the whole machine. I was not able to figure out what is missing in the in-tree driver. But for the realtek code, the cause appeared quite silly. Since chips are able to do jumbo, but not scatter-gather, they allocated 9K clusters for rx fill always, even if interface was configured for standard 1500 MTU. At some time (2-3 weeks for my workload) memory becomes fragmented enough that driver cannot refill rx, and due to the interface mutex, this cascaded to everything that touched network. I added a knob to disable jumbo and re-imported several revisions of the vendor driver there: https://github.com/kostikbel/rere After that I am quite happy running stable/11 for a year without an issue. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-236962-7501-cNFCKE7tsG>