Date: Wed, 19 Feb 2020 16:32:18 +0000 From: bugzilla-noreply@freebsd.org To: net@FreeBSD.org Subject: [Bug 208205] re0 watchdog timeout Message-ID: <bug-208205-7501-AEhJpLXPmT@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-208205-7501@https.bugs.freebsd.org/bugzilla/> References: <bug-208205-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=3D208205 Chris Hutchinson <portmaster@bsdforge.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |portmaster@bsdforge.com --- Comment #33 from Chris Hutchinson <portmaster@bsdforge.com> --- FWIW we ran into this problem when we opted to become a public CPAN mirror (perl.org). Which necessitated adding 2 more ports, and delegating 2 additional addresses. We used a 2 port RealTek adapter. About an hour into going live. The watchdog(8) timeouts began spamming the logs. The solution was to bump 2 entries in sysctl.conf(5): kern.ipc.nmbjumbop (245550 by default) and kern.ipc.nmbclusters (491100 by default) as in FreeBSD 11, these numbers are too small -- at least for these NICs. How high you bump them depends upon the load and traffic on your NICs. As a rule of thumb I would suggest bumping them up a quarter of their original values until watchdog shuts up. All the while accessing any performance changes. We're now on 12, and moving to 13 shortly. 12 did NOT exhibit this problem, because the numbers are much higher by default. HTH --Chris --=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-208205-7501-AEhJpLXPmT>