Date: Sun, 08 Dec 2024 19:48:20 +0000 From: bugzilla-noreply@freebsd.org To: net@FreeBSD.org Subject: [Bug 166724] if_re(4): watchdog timeout Message-ID: <bug-166724-7501-eFw1haxTp4@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 Petre Rodan <petre.rodan@subdimension.ro> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |petre.rodan@subdimension.ro --- Comment #124 from Petre Rodan <petre.rodan@subdimension.ro> --- I had the same 're0: watchdog timeout' bug on my Gigabyte B450 AORUS M motherboard (bios F67c). I simply could not log into FreeBSD (14.1 and 14.2) since the network service kept being restarted due to re0 getting stuck with the above mentioned error. this was 100% reproducible on my triple boot system: start windows 10 powerdown powerup, start FreeBSD reo: watchdog timeout in order to get rid of the error I had to either completely unplug the power cord from the system before starting FreeBSD or booting into Linux first. Today I found that a better solution is to install net/realtek-re-kmod and disabling the rx/tx offloading via ifconfig_re0=3D"DHCP -rxcsum -txcsum -rxcsum6 -txcsum6" --=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-eFw1haxTp4>