The issue should be fixed in 6.8.0-44.44 by below commit

commit 27e70aa72937bcfd08ffc10727ad315f9763e6ac
Author: Hui Wang <[email protected]>
Date:   Thu Jul 18 16:57:16 2024 +0800

    e1000e: move force SMBUS near the end of enable_ulp function
    
    BugLink: https://bugs.launchpad.net/bugs/2073358
    
    The commit 861e8086029e ("e1000e: move force SMBUS from enable ulp
    function to avoid PHY loss issue") introduces a regression on
    PCH_MTP_I219_LM18 (PCIID: 0x8086550A). Without the referred commit, the
    ethernet works well after suspend and resume, but after applying the
    commit, the ethernet couldn't work anymore after the resume and the
    dmesg shows that the NIC link changes to 10Mbps (1000Mbps originally):
    
        [   43.305084] e1000e 0000:00:1f.6 enp0s31f6: NIC Link is Up 10 Mbps 
Full Duplex, Flow Control: Rx/Tx
    
    Without the commit, the force SMBUS code will not be executed if
    "return 0" or "goto out" is executed in the enable_ulp(), and in my
    case, the "goto out" is executed since FWSM_FW_VALID is set. But after
    applying the commit, the force SMBUS code will be ran unconditionally.
    
    Here move the force SMBUS code back to enable_ulp() and put it
    immediately ahead of hw->phy.ops.release(hw), this could allow the
    longest settling time as possible for interface in this function and
    doesn't change the original code logic.
    
    The issue was found on a Lenovo laptop with the ethernet hw as below:
    00:1f.6 Ethernet controller [0200]: Intel Corporation Device [8086:550a]
    (rev 20).
    
    And this patch is verified (cable plug and unplug, system suspend
    and resume) on Lenovo laptops with ethernet hw: [8086:550a],
    [8086:550b], [8086:15bb], [8086:15be], [8086:1a1f], [8086:1a1c] and
    [8086:0dc7].
    
    Fixes: 861e8086029e ("e1000e: move force SMBUS from enable ulp function to 
avoid PHY loss issue")
    Signed-off-by: Hui Wang <[email protected]>
    Acked-by: Vitaly Lifshits <[email protected]>
    Tested-by: Naama Meir <[email protected]>
    Reviewed-by: Simon Horman <[email protected]>
    Reviewed-by: Paul Menzel <[email protected]>
    Signed-off-by: Tony Nguyen <[email protected]>
    Tested-by: Zhang Rui <[email protected]>
    Signed-off-by: Jacob Keller <[email protected]>
    Link: 
https://lore.kernel.org/r/20240528-net-2024-05-28-intel-net-fixes-v1-1-dc8593d2b...@intel.com
    Signed-off-by: Jakub Kicinski <[email protected]>
    (cherry picked from commit bfd546a552e140b0a4c8a21527c39d6d21addb28)
    Signed-off-by: Aaron Ma <[email protected]>
    Acked-by: Thibault Ferrante <[email protected]>
    Acked-by: Noah Wager <[email protected]>
    Acked-by: Andrei Gherzan <[email protected]>
    Signed-off-by: Roxana Nicolescu <[email protected]>

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2078656

Title:
  NIC speed down to 10 Mbps after resuming from suspend

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.8/+bug/2078656/+subscriptions


-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to