This bug is awaiting verification that the linux-oem-5.17/5.17.0-1019.20
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!

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

Title:
  System hang during S3 test

Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Released
Status in linux-oem-5.17 source package in Jammy:
  Fix Committed

Bug description:
  [Impact]
  It hangs while doing S3 test on the platform with CPU Intel(R) Pentium(R) 
Silver N6005 @ 2.00GHz

  [Fix]
  Can't reproduce this issue with v5.18-rc1 kernel, so bisecting the kernel and 
found this below commit
  567511462387 mm/memcg: protect memcg_stock with a local_lock_t
  For safty, I backported the series of the patch
  https://www.spinics.net/lists/cgroups/msg31595.html
  But I still can reproduce the issue after applied those patches on top of 
5.17 oem kernel.
  So, I did a second round of bisecting and found below commit is required, too
  a74c6c00b1cb mm/memremap: avoid calling kasan_remove_zero_shadow() for device 
private memory

  [Test]
  Done the S3 test 400 times on the target and it's still working well.

  [Where problems could occur]
  Hard to evaluate the impact, but from the overnight test, the memory usage is 
still low, so there should be no memory leakage, and can't find any fix patch 
for those applied commits from upstream and linux-next trees.
  The patches are all from v5.18-rc1, so we only need them to be applied on 
oem-5.17 kernel, and will let QA to do thoroughly tests.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990330/+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