https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208205
--- Comment #24 from zjk <z...@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 quickly. 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 load 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 / band management. It is still not a solution to the problem of the driver itself. -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
