[Bug 166724] if_re(4): watchdog timeout

From: <bugzilla-noreply_at_freebsd.org>
Date: Sun, 17 Mar 2024 21:23:25 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724

vova@fbsd.ru changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |vova@fbsd.ru

--- Comment #115 from vova@fbsd.ru ---
Also have problems with in-tree if_re

After upgrade 12.3 -> 14.0 it started to loose connectivity every ~10-30
minutes, for 0.5-10 minutes ... wich is pity, does not depends much on network
load (as minimum small load vs huge load).

Frankly speaking, even on 12.x sometimes (quite rarely) there was such looses
of connectivity, but very rare.

no any "watchdog timeouts" - just lost of connectivity, I guess 


re0@pci0:3:0:0: class=0x020000 rev=0x02 hdr=0x00 vendor=0x10ec device=0x8168
subvendor=0x1458 subdevice=0xe000
    vendor     = 'Realtek Semiconductor Co., Ltd.'
    device     = 'RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
Controller'
    class      = network
    subclass   = ethernet

somehow ping which was run after recover:

# ping 172.22.2.5
PING 172.22.2.5: 56 data bytes
...
ping: sendto: Host is down
ping: sendto: Host is down
ping: sendto: Host is down
ping: sendto: Host is down
...
64 bytes from 172.22.2.5: icmp_seq=6 ttl=64 time=13123.658 ms
64 bytes from 172.22.2.5: icmp_seq=7 ttl=64 time=12122.371 ms
64 bytes from 172.22.2.5: icmp_seq=8 ttl=64 time=11120.850 ms
64 bytes from 172.22.2.5: icmp_seq=9 ttl=64 time=10112.358 ms
64 bytes from 172.22.2.5: icmp_seq=10 ttl=64 time=9107.387 ms
64 bytes from 172.22.2.5: icmp_seq=11 ttl=64 time=8055.572 ms
64 bytes from 172.22.2.5: icmp_seq=12 ttl=64 time=7040.134 ms
64 bytes from 172.22.2.5: icmp_seq=13 ttl=64 time=6012.834 ms
64 bytes from 172.22.2.5: icmp_seq=14 ttl=64 time=5010.828 ms
64 bytes from 172.22.2.5: icmp_seq=15 ttl=64 time=4009.945 ms
64 bytes from 172.22.2.5: icmp_seq=16 ttl=64 time=3007.644 ms
64 bytes from 172.22.2.5: icmp_seq=17 ttl=64 time=2006.117 ms
64 bytes from 172.22.2.5: icmp_seq=18 ttl=64 time=1004.582 ms
64 bytes from 172.22.2.5: icmp_seq=19 ttl=64 time=2.977 ms
64 bytes from 172.22.2.5: icmp_seq=20 ttl=64 time=0.784 ms
64 bytes from 172.22.2.5: icmp_seq=21 ttl=64 time=0.464 ms

looks like packets was buffered somewhere

Also have such in logs after recovering: 
Mar 17 17:33:49 srv kernel: Limiting open port RST response from 1346 to 187
packets/sec

looks like all "stalled" TCP streams packates was delivered and got RSTs fired
back.

turning on debug on interface - did not provide any new diagnostics
ifconfig re0 -tso -tso4 -tso6 -vlanhwcsum -vlanhwtso -rxcsum -txcsum
- did not helped as well (on 12.x -vlanhwtso probably helped)

what was helped - switchover to the port net/realtek-re-kmod

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.