Date: Mon, 07 Nov 2022 20:54:48 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 266973] [e1000] incorrect behavior when media and mediaopt are set to 100BaseTX full-duplex Message-ID: <bug-266973-227-h1KvCaasbn@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-266973-227@https.bugs.freebsd.org/bugzilla/> References: <bug-266973-227@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=3D266973 --- Comment #3 from Kristof Provost <kp@freebsd.org> --- I'm struggling to make sense of this. I can't quite follow how the code produces this PHY access pattern, and can also not work out why we end up getting link when dtrace instrumented, and not when it's not. Unless we're = not waiting long enough for the PHY to do its thing, but I also can't see evide= nce of that in the dtrace output. There are two series of what looks like a wait for link pattern in the dtra= ce output> That is, this: 26=C2=A0=C2=A0 4923=C2=A0=C2=A0 e1000_read_phy_reg_82580:entry read(0x1) 26=C2=A0=C2=A0 4924=C2=A0 e1000_read_phy_reg_82580:return =3D> 0x7949 I'd assume that's produced by e1000_phy_has_link_generic() where we do 2x iterations of read_reg(PHY_STATUS), and check for the MII_SR_LINK_STATUS fl= ag. That flag (0x0004) is not set in any of these reads, and yet ifconfig does later report "status: active". --=20 You are receiving this mail because: 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-266973-227-h1KvCaasbn>