https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724
--- Comment #35 from Alex Dupre <a...@freebsd.org> --- I don't think I've ever said this issue is good :-) What I said is that in my environment when I switched to 11.2-RELEASE it was happening less frequently. With the FreeBSD driver is easy to detect it, because it prints the timeout message and resets the interface after 5 ticks, effectively interrupting any connections for a few seconds. The Realtek driver doesn't reset the interface and doesn't print the message, so a short timeout might go unnoticed. To add new info to the thread, recently I've tried to increase the watchdog timeout of the FreeBSD driver, changing it from 5 to 50 ticks. Well, the result was that the connection interruption lasted longer, so the interface seems really stuck and the reset the only solution. In the last months I've also tried Realtek drivers 1.94.01 and 1.95 (the one I'm currently running) and I'm not seeing differences from the 1.93, in my scenario it seems to work good enough (== I'm not able to detect any connection drop during normal usage, that doesn't mean they are not happening at all). --- Comment #36 from zjk <z...@wp.pl> --- Ok, ok Alex - I understand. Therefore, for doubters - I added 2 posts earlier chart from monitorix. For a 24/7 server - you can see how the link hangs (and this happens on a server that has not too heavy load...), only the reset restores a longer good response. For problem solvers - I must add: on most computers I use lagg. Evidently this "overlay" on the driver increases the frequency of hanging (compared to computers with re without lagg). But this is a separate problem for a separate thread. -- You are receiving this mail because: You are on the CC list 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"
