From owner-freebsd-net@freebsd.org Sun Apr 25 23:03:21 2021 Return-Path: Delivered-To: freebsd-net@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 6C8425EF0F4 for ; Sun, 25 Apr 2021 23:03:21 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.nyi.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 4FT3V12T0rz4jmG for ; Sun, 25 Apr 2021 23:03:21 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id 54B1D5EF0F2; Sun, 25 Apr 2021 23:03:21 +0000 (UTC) Delivered-To: net@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 535945EF58E for ; Sun, 25 Apr 2021 23:03:21 +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 4FT3V11nM4z4jbR for ; Sun, 25 Apr 2021 23:03:21 +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 3099A1CAA1 for ; Sun, 25 Apr 2021 23:03:21 +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 13PN3LbC055081 for ; Sun, 25 Apr 2021 23:03:21 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 13PN3LCx055080 for net@FreeBSD.org; Sun, 25 Apr 2021 23:03:21 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: net@FreeBSD.org Subject: [Bug 238411] igb(4): Wake on Lan not working with Intel I210 Date: Sun, 25 Apr 2021 23:03:18 +0000 X-Bugzilla-Reason: AssignedTo CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 12.0-RELEASE X-Bugzilla-Keywords: IntelNetworking, needs-qa, regression X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: abraham@gmx.at X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: net@FreeBSD.org X-Bugzilla-Flags: maintainer-feedback? mfc-stable13? 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 MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Apr 2021 23:03:21 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D238411 --- Comment #16 from Abraham122x --- Let's ask differently in reference to the non-modified FreeBSD drivers.=20 Regardless if I set "ifconfig igb0 wol" or not, I cannot enable the WOL fea= ture on my NICS. So for me it's not clear with which functionality from OS perspective I can influence the field "adapter->wol". My only workaround I found is to change the variable directly in the source code of the driver and overrule it. What I see from my theoretical analysis, the variables are stored in ROM at shutdown -> method "em_enable_phy_wakeup": E1000_WRITE_REG(hw, E1000_WUC, E1000_WUC_PHY_WAKE | E1000_WUC_PME_EN | E1000_WUC_APME); E1000_WRITE_REG(hw, E1000_WUFC, adapter->wol); At startup the register is read again: apme_mask =3D E1000_WUC_APME; eeprom_data =3D E1000_READ_REG(&adapter->hw, E1000_WUC); if (eeprom_data & apme_mask) adapter->wol =3D (E1000_WUFC_MAG | E1000_WUFC_MC); As the variable "adapter->wol" at startup seems to be zero, it means that t= he flag E1000_WUC_APME is not set, although it was written at shutdown. So seen from my hardware perspective, the ROM settings are not properly recognized at startup, hence "adapter->wol" is always zero. The variable ca= nnot be influenced by anything known to me. Is my analysis correct? Did I miss something? P.S: I have an E1000_DEV_ID_I210_COPPER_FLASHLESS installed. --=20 You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug.=