Date: Wed, 21 Apr 2021 19:35:18 +0000 From: bugzilla-noreply@freebsd.org To: net@FreeBSD.org Subject: [Bug 235524] igb(4): Ethernet interface loses active link state Message-ID: <bug-235524-7501-TOewELcDuh@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-235524-7501@https.bugs.freebsd.org/bugzilla/> References: <bug-235524-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=3D235524 Kevin Bowling <kbowling@freebsd.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kbowling@freebsd.org --- Comment #11 from Kevin Bowling <kbowling@freebsd.org> --- (In reply to mack from comment #10) This is a different issue. The realtek driver in FreeBSD is missing a lot = of critical workarounds for hardware issues, which is why you see the watchdog= .=20 You can try the "net/realtek-re-kmod" driver in ports which contains some of the workarounds needed and is tested by the vendor. I am interested in improving re(4) but to set expectations these are coloss= al tasks that cover 60 chipset variations and none of them are flawless, I don= 't have docs, and have to sneak this in between a dayjob. If you can provide = more info like the pciconf output that would make for a useful bug report (in a = new PR not this one which is not related). If you rely on the system in a material way I would switch to a vendor supported NIC, like Chelsio T4+, Mellanox CX4+, or intel ixgbe+. Chelsio h= as twisted pair options. --=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-235524-7501-TOewELcDuh>