Date: Sun, 06 May 2018 07:30:17 +0000 From: bugzilla-noreply@freebsd.org To: net@FreeBSD.org Subject: [Bug 166724] [re] if_re watchdog timeout Message-ID: <bug-166724-7501-MCeqMybNMt@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-166724-7501@https.bugs.freebsd.org/bugzilla/> References: <bug-166724-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=3D166724 --- Comment #25 from zjk <zjk7@wp.pl> --- hw.re.msi_disable hw.re.msix_disable I tested this solution for a few days (it already exists somewhere on the internet). There is no visible effect (on my computers) - network is closing very quic= kly.=20 But - maybe it depends on the network card chipset? However, I highly recommend the analysis: https://forums.freebsd.org/threads/10-2-release-re0-watchdog-timeout.55306/= #post-337045 There are some extremely important remarks. One important tip - this may be the result of overloading the processor. In general - a problem for low-performance processors. Or vice versa: for the "computationally demanding" chipset of the network card, and finally the "programmatically extended" driver. Probably because the version of "built-in" driver for FreeBSD is so much "slimmed", in relation to the full version from Realtek (from the Realtek website). It may be intended to run on less-efficient processors. But I can not fully appreciate everything from this analysis. "Watchdog timeout" messages - also occur after stopping the transmission. Processor l= oad drops to several percent, but watchdog timeout messages still appear every = few seconds. In general - a reset is needed to restore the normal operation of the interface. As a solution, you can use "patch" - instead of, for example, limit the connection speed to 100 Mb, you can use, for example, dummynet for flow / b= and management. It is still not a solution to the problem of the driver itself. --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-166724-7501-MCeqMybNMt>