Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 22 Aug 2024 20:31:58 +0000
From:      bugzilla-noreply@freebsd.org
To:        net@FreeBSD.org
Subject:   [Bug 166724] if_re(4): watchdog timeout
Message-ID:  <bug-166724-7501-e3clk4z3wf@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

dgilbert@eicat.ca changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |dgilbert@eicat.ca

--- Comment #117 from dgilbert@eicat.ca ---
I can trigger this on 14.1-p3.  Reliably.  To replicate:

- mount an NFS share from a relatively fast machine;
- extract a multigigabyte compressed archive.

On 15-CURRENT, I was replicating it, but I no longer have that test.  It wo=
uld
finish a poudriere run (if restarted enough) but it would consistently fail=
 the
last bit --- I believe it's signing the packages as that point (counting up=
 for
many minutes in %).

I have triggered it with "7z x .." and I have triggered it by using plasma's
file browser, right clicking and choosing "extract here" on an NFS share.

The hardware is a levono Neo 30a 24 Gen 3.  pciconf says (of the re0):

re0@pci0:2:0:0: class=3D0x020000 rev=3D0x15 hdr=3D0x00 vendor=3D0x10ec devi=
ce=3D0x8168
subvendor=3D0x17aa subdevice=3D0x375a
    vendor     =3D 'Realtek Semiconductor Co., Ltd.'
    device     =3D 'RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
Controller'
    class      =3D network
    subclass   =3D ethernet

When I trigger it, console says:

re0: watchdog timeout
re0: link state changed to DOWN
re0: link state changed to UP

When I trigger it, a running ping says:

root@strike:/home/dgilbert # ping 192.168.221.1
PING 192.168.221.1 (192.168.221.1): 56 data bytes
ping: sendto: No route to host
ping: sendto: No route to host
ping: sendto: No route to host
ping: sendto: No route to host
64 bytes from 192.168.221.1: icmp_seq=3D22 ttl=3D64 time=3D7490.585 ms
64 bytes from 192.168.221.1: icmp_seq=3D23 ttl=3D64 time=3D6472.741 ms
64 bytes from 192.168.221.1: icmp_seq=3D24 ttl=3D64 time=3D5445.312 ms
64 bytes from 192.168.221.1: icmp_seq=3D25 ttl=3D64 time=3D4444.340 ms
64 bytes from 192.168.221.1: icmp_seq=3D30 ttl=3D64 time=3D0.173 ms
64 bytes from 192.168.221.1: icmp_seq=3D31 ttl=3D64 time=3D0.457 ms
64 bytes from 192.168.221.1: icmp_seq=3D32 ttl=3D64 time=3D0.374 ms
64 bytes from 192.168.221.1: icmp_seq=3D33 ttl=3D64 time=3D0.377 ms
64 bytes from 192.168.221.1: icmp_seq=3D34 ttl=3D64 time=3D0.321 ms

The topology:

NFS server: FreeBSD 14.1-p3, 140T comprised of 4*4T disks and 2T of nvme ca=
che.
 128G RAM.  Threadripper.  10GE network.

NFS client:  This crappy free-to-me all-in-one.  1GE network.

--=20
You are receiving this mail because:
You are the assignee for the bug.
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-e3clk4z3wf>