This bug was fixed in the package linux-oem-5.17 - 5.17.0-1016.17

---------------
linux-oem-5.17 (5.17.0-1016.17) jammy; urgency=medium

  * jammy/linux-oem-5.17: 5.17.0-1016.17 -proposed tracker (LP:
#1983905)

  * drm/i915, turbostat: Support for ADL-N, RPL-P (LP: #1987265)
    - tools/power turbostat: Introduce support for RaptorLake
    - tools/power turbostat: Support RAPTORLAKE P
    - drm/i915/rpl-s: Add stepping info
    - drm/i915: Add RPL-S PCI IDs
    - drm/i915/adl-n: Enable ADL-N platform
    - drm/i915/rpl-p: Add PCI IDs
    - drm/i915/adl-n: Add PCH Support for Alder Lake N
    - drm/i915/adl-n: Add stepping info

  * CVE-2021-33655
    - fbcon: Disallow setting font bigger than screen size
    - fbcon: Prevent that screen size is smaller than font size
    - fbmem: Check virtual screen sizes in fb_set_var()

  * Add proper runtime PM support to Realtek PCIe cardreader (LP: #1963615)
    - misc: rtsx: Rework runtime power management flow
    - misc: rtsx: Cleanup power management ops
    - misc: rtsx: Quiesce rts5249 on system suspend
    - misc: rtsx: conditionally build rtsx_pm_power_saving()
    - misc: rtsx: rts522a rts5228 rts5261 support Runtime PM

  * Fix non-working I219 ethernet after s2idle (LP: #1986751)
    - Revert "e1000e: Fix possible HW unit hang after an s0ix exit"

  * Fix invalid MAC address after hotplug tbt dock (LP: #1942999)
    - SAUCE: igc: wait for the MAC copy when enabled MAC passthrough

  * AMD Rembrandt: DP tunneling fails with Thunderbolt monitors (LP: #1983143)
    - drm/amd/display: Fix new dmub notification enabling in DM
    - SAUCE: thunderbolt: Add DP out resource when DP tunnel is discovered.

  * Enable speaker and mute LEDs for HP laptops (LP: #1982990)
    - ALSA: hda/realtek: Enable speaker and mute LEDs for HP laptops

  * Fix drm/amd/pm: enable ASPM by default (LP: #1966680)
    - drm/amd: Refactor `amdgpu_aspm` to be evaluated per device
    - drm/amd: Use amdgpu_device_should_use_aspm on navi umd pstate switching
    - drm/amdgpu: vi: disable ASPM on Intel Alder Lake based systems

  * CVE-2021-33061
    - ixgbe: add the ability for the PF to disable VF link state
    - ixgbe: add improvement for MDD response functionality
    - ixgbevf: add disable link state

  [ Ubuntu: 5.17.0-8.8~22.04.8 ]

  * jammy/linux-hwe-5.17: 5.17.0-8.8~22.04.8 -proposed tracker (LP: #1983907)
  * Packaging resync (LP: #1786013)
    - debian/dkms-versions -- update from kernel-versions (main/2022.08.08)
  * GPIO character device v1 API not enabled in kernel (LP: #1953613)
    - [Config] Enable CONFIG_GPIO_CDEV_V1
  * refactoring of overlayfs fix to properly support shiftfs (LP: #1983640)
    - SAUCE: for aufs mmap: print the virtual file path
    - SAUCE: overlayfs: fix incorrect mnt_id of files opened from map_files
  * Audio mute key (f5) LED and Mic mute key (f8) LED are no function on HP
    440/450/640/650 G9 (LP: #1982716)
    - ALSA: hda/realtek: fix mute/micmute LEDs for HP machines

 -- Timo Aaltonen <timo.aalto...@canonical.com>  Mon, 22 Aug 2022
13:50:21 +0300

** Changed in: linux-oem-5.17 (Ubuntu Jammy)
       Status: Confirmed => Fix Released

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-33061

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-33655

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.17 in Ubuntu.
https://bugs.launchpad.net/bugs/1986751

Title:
  Fix non-working I219 ethernet after s2idle

Status in HWE Next:
  New
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux-oem-5.17 source package in Jammy:
  Fix Released

Bug description:
  [Impact]
  I219 may stop working after s2idle. The link is up but failed to get an
  IP address from DHCP server.

  [Fix]
  Revert the workaround patch "e1000e: Fix possible HW unit hang after an
  s0ix exit" so the new fix "e1000e: Enable GPT clock before sending
  message to CSME" can work.

  [Test]
  With the patch applied, the I219 device always get ip address and all
  the functionalities are working.

  [Where problems could occur]
  It's really hard to say since the interaction between I219 and Intel ME
  is very arcane. The good thing is that the fix is limited to e1000e.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1986751/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to     : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to