System hang during S3 test
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
HWE Next |
Fix Released
|
Undecided
|
Unassigned | ||
linux (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Jammy |
Fix Released
|
Undecided
|
Unassigned | ||
Kinetic |
Fix Released
|
Undecided
|
Unassigned | ||
linux-oem-5.17 (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Jammy |
Fix Released
|
Undecided
|
AceLan Kao | ||
Kinetic |
Invalid
|
Undecided
|
Unassigned |
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:/
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_
[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.
Changed in linux-oem-5.17 (Ubuntu): | |
status: | New → Invalid |
Changed in linux-oem-5.17 (Ubuntu Jammy): | |
status: | New → In Progress |
assignee: | nobody → AceLan Kao (acelankao) |
description: | updated |
Changed in linux-oem-5.17 (Ubuntu Jammy): | |
status: | In Progress → Fix Committed |
Changed in linux (Ubuntu): | |
status: | New → Fix Released |
Changed in linux (Ubuntu Jammy): | |
status: | New → Fix Released |
tags: | added: oem-priority originate-from-1986905 somerville |
Changed in linux (Ubuntu Kinetic): | |
status: | New → Fix Released |
Changed in linux-oem-5.17 (Ubuntu Kinetic): | |
status: | New → Invalid |
Changed in hwe-next: | |
status: | New → Fix Released |
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!