This bug is awaiting verification that the linux-oem-5.17/5.17.0-1006.6
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy' to 'verification-done-jammy'. If the
problem still exists, change the tag 'verification-needed-jammy' to
'verification-failed-jammy'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-jammy

-- 
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/1973104

Title:
  e1000e report hardware hang

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  In Progress
Status in linux-oem-5.17 source package in Jammy:
  Fix Committed

Bug description:
  [Impact]
  e1000e hardware unit hang after s2idle
  May 06 15:34:49 ubuntu kernel: e1000e 0000:00:1f.6 enp0s31f6: Detected 
Hardware Unit Hang:
                                   TDH <1>
                                   TDT <5>
                                   next_to_use <5>
                                   next_to_clean <1>
                                 buffer_info[next_to_clean]:
                                   time_stamp <1000587f0>
                                   next_to_watch <1>
                                   jiffies <1000589c0>
                                   next_to_watch.status <0>
                                 MAC Status <40080283>
                                 PHY Status <796d>
                                 PHY 1000BASE-T Status <3800>
                                 PHY Extended Status <3000>
                                 PCI Status <10>

  [Fix]
  Below commit fixes this issue
  
https://patchwork.ozlabs.org/project/intel-wired-lan/patch/20220508070905.1878172-1-sasha.nef...@intel.com/

  [Test]
  Verified on the target machine, and confirmed the issue is gone.

  [Where problems could occur]
  The impact is low, it keeps the GPT clock enabled for CSME when 
e1000e_pm_resume() is called. I can't see this may introduce any regression.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1973104/+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