Date: Thu, 07 May 2020 11:57:49 +0000 From: bugzilla-noreply@freebsd.org To: net@FreeBSD.org Subject: [Bug 166724] [re] if_re watchdog timeout Message-ID: <bug-166724-7501-ruQeF45iZO@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 Jan Przybylak <jplx256@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jplx256@gmail.com --- Comment #46 from Jan Przybylak <jplx256@gmail.com> --- I'm also experiencing this on 12.1-RELEASE-p4. While networking usually wor= ks, large transfers seem to kill the driver, which can only be fixed by rebooti= ng. When this happens, `dmesg` will be filled with: re0: watchdog timeout re0: link state changed to DOWN re0: link state changed to UP These three messages repeat forever until the machine is rebooted. Restarti= ng the interface with ifconfig did not fix it. This typically happens when I create a large backup (I use borgmatic) to an SFTP server on my local network. The affected machine is an Odroid H2 which I use as NAS. It's got two Realt= ek RTL8111G NICs, which I am not able to replace (It's a Single Board Computer, the NICs are soldered to the board and there are no PCI slots). --=20 You are receiving this mail because: 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-ruQeF45iZO>