Date: Sun, 17 Mar 2024 21:23:25 +0000 From: bugzilla-noreply@freebsd.org To: net@FreeBSD.org Subject: [Bug 166724] if_re(4): watchdog timeout Message-ID: <bug-166724-7501-iFiQfwVIXg@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 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 netw= ork load (as minimum small load vs huge load). Frankly speaking, even on 12.x sometimes (quite rarely) there was such loos= es of connectivity, but very rare. no any "watchdog timeouts" - just lost of connectivity, I guess=20 re0@pci0:3:0:0: class=3D0x020000 rev=3D0x02 hdr=3D0x00 vendor=3D0x10ec devi= ce=3D0x8168 subvendor=3D0x1458 subdevice=3D0xe000 vendor =3D 'Realtek Semiconductor Co., Ltd.' device =3D 'RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet Controller' class =3D network subclass =3D 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=3D6 ttl=3D64 time=3D13123.658 ms 64 bytes from 172.22.2.5: icmp_seq=3D7 ttl=3D64 time=3D12122.371 ms 64 bytes from 172.22.2.5: icmp_seq=3D8 ttl=3D64 time=3D11120.850 ms 64 bytes from 172.22.2.5: icmp_seq=3D9 ttl=3D64 time=3D10112.358 ms 64 bytes from 172.22.2.5: icmp_seq=3D10 ttl=3D64 time=3D9107.387 ms 64 bytes from 172.22.2.5: icmp_seq=3D11 ttl=3D64 time=3D8055.572 ms 64 bytes from 172.22.2.5: icmp_seq=3D12 ttl=3D64 time=3D7040.134 ms 64 bytes from 172.22.2.5: icmp_seq=3D13 ttl=3D64 time=3D6012.834 ms 64 bytes from 172.22.2.5: icmp_seq=3D14 ttl=3D64 time=3D5010.828 ms 64 bytes from 172.22.2.5: icmp_seq=3D15 ttl=3D64 time=3D4009.945 ms 64 bytes from 172.22.2.5: icmp_seq=3D16 ttl=3D64 time=3D3007.644 ms 64 bytes from 172.22.2.5: icmp_seq=3D17 ttl=3D64 time=3D2006.117 ms 64 bytes from 172.22.2.5: icmp_seq=3D18 ttl=3D64 time=3D1004.582 ms 64 bytes from 172.22.2.5: icmp_seq=3D19 ttl=3D64 time=3D2.977 ms 64 bytes from 172.22.2.5: icmp_seq=3D20 ttl=3D64 time=3D0.784 ms 64 bytes from 172.22.2.5: icmp_seq=3D21 ttl=3D64 time=3D0.464 ms looks like packets was buffered somewhere Also have such in logs after recovering:=20 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 fi= red 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 --=20 You are receiving this mail because: You are on the CC list for the bug. 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-166724-7501-iFiQfwVIXg>