From nobody Mon Nov 07 20:54:48 2022 X-Original-To: bugs@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4N5k4m3J6Jz4gMRY for ; Mon, 7 Nov 2022 20:54:48 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4N5k4m0v5wz3jKk for ; Mon, 7 Nov 2022 20:54:48 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 4N5k4l6l2PzFv5 for ; Mon, 7 Nov 2022 20:54:47 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 2A7Kslos011960 for ; Mon, 7 Nov 2022 20:54:47 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 2A7KslYV011959 for bugs@FreeBSD.org; Mon, 7 Nov 2022 20:54:47 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f 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 Date: Mon, 07 Nov 2022 20:54:48 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 13.1-STABLE X-Bugzilla-Keywords: IntelNetworking X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: kp@freebsd.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated List-Id: Bug reports List-Archive: https://lists.freebsd.org/archives/freebsd-bugs List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-bugs@freebsd.org MIME-Version: 1.0 ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1667854488; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=jfmVnzp8OGPn2o6VJ1x4QezacrcIBdvKLaiRnu8Nf5o=; b=Du0fQsjMRLjdcQejs9LNsyGFAl4sxbhGPtplaRsj50FC//uoY+I9Y1BINQMTNC+x2hj4J9 8v6aAJ5rMalVenRbBpkFH2GzIpqrxJcHxXXaS8zSdTXnSdV/IT6yU5fHVd+51MaBrCMoXa w2KTm9SFSKnRTw4Up8ufhCogHwuraXaLbaXYtwu7cM09MkUSkO9WUcVr9oXvZ55IfZnmDD EqbszbCN3jx1LxOmuresgLw93nm+oBuYysxffQIOC2+NsmNu5TgHBqRDH/BG81XHGKDeo2 ycOSeCp01q9VqB0VlyGxxmHcHmWgZRGMbGhkEQpzVTCyoHBGbcl6Q7EXvwyQtg== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1667854488; a=rsa-sha256; cv=none; b=U37URbKDJhcsTTNyoUMwDt3KMiqybBPXzifAVu8YhwkhXPZXxBgizzW4ermzniA87oA0Jx L/G2TcdQFbDfbnRIujxTj+Jtcd2HgENAFUNkG30kTSlznp/csjLpAu3lvvweWke7JZQAIe /uK5u3NUm+EqXRZk+rUfvL8QhLbhc0nN1Ag4fSd3nuzClaP8z60IwrHGMLAwVhZyZbZYgy EKIsdoLLgMYAWP+XLsoaXrrAMEOsO4Af77a9WhUtQZMppb4n5RFy+5fiNuYfpO/2UnMPdy y5mCAGVl/1V7fCjSzX5scteR335QsOGSFtl3qTtxz6hVe0kq/C7m/L1zHuc5oA== ARC-Authentication-Results: i=1; mx1.freebsd.org; none X-ThisMailContainsUnwantedMimeParts: N https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D266973 --- Comment #3 from Kristof Provost --- 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.=