System hang during S3 test

Bug #1990330 reported by AceLan Kao
8
This bug affects 1 person
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://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.

AceLan Kao (acelankao)
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)
AceLan Kao (acelankao)
description: updated
Timo Aaltonen (tjaalton)
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
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

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!

AceLan Kao (acelankao)
tags: added: oem-priority originate-from-1986905 somerville
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

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

  * jammy/linux-oem-5.17: 5.17.0-1019.20 -proposed tracker (LP: #1989787)

  * Fix resume on AMD platforms when TBT monitor is plugged (LP: #1990920)
    - drm/amd/display: Detect dpcd_rev when hotplug mst monitor
    - drm/amd/display: Release remote dc_sink under mst scenario

  * pcieport 0000:00:1b.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal),
    type=Transaction Layer, (Requester ID) (LP: #1988797)
    - SAUCE: PCI/PTM: Cache PTM Capability offset
    - SAUCE: PCI/PTM: Add pci_upstream_ptm() helper
    - SAUCE: PCI/PTM: Separate configuration and enable
    - SAUCE: PCI/PTM: Add pci_suspend_ptm() and pci_resume_ptm()
    - SAUCE: PCI/PTM: Move pci_ptm_info() body into its only caller
    - SAUCE: PCI/PTM: Preserve RsvdP bits in PTM Control register
    - SAUCE: PCI/PTM: Reorder functions in logical order
    - SAUCE: PCI/PTM: Consolidate PTM interface declarations
    - SAUCE: PCI/PM: Always disable PTM for all devices during suspend
    - SAUCE: PCI/PM: Simplify pci_pm_suspend_noirq()

  * Fix AMDGPU: No video output and system hangs with two monitor (dGPU: W6400)
    (LP: #1989647)
    - drm/amd/display: Ignore First MST Sideband Message Return Error

  * System hang during S3 test (LP: #1990330)
    - memcg: add per-memcg total kernel memory stat
    - mm/memcg: revert ("mm/memcg: optimize user context object stock access")
    - mm/memcg: disable threshold event handlers on PREEMPT_RT
    - mm/memcg: protect per-CPU counter by disabling preemption on PREEMPT_RT
      where needed.
    - mm/memcg: opencode the inner part of obj_cgroup_uncharge_pages() in
      drain_obj_stock()
    - mm/memcg: protect memcg_stock with a local_lock_t
    - mm/memcg: disable migration instead of preemption in drain_all_stock().
    - mm/memremap: avoid calling kasan_remove_zero_shadow() for device private
      memory

  * To support Intel Maple Ridge Thunderbolt [8086:1134] (LP: #1990240)
    - thunderbolt: Add support for Intel Maple Ridge single port controller

  * Intel graphic driver is not probing[8086:468b] (LP: #1990242)
    - drm/i915: Add new ADL-S pci id

  * support independent clock and LED GPIOs for Intel IPU6 platforms
    (LP: #1989046)
    - SAUCE: platform/x86: int3472: support independent clock and LED GPIOs

 -- Timo Aaltonen <email address hidden> Tue, 27 Sep 2022 15:12:42 +0300

Changed in linux-oem-5.17 (Ubuntu Jammy):
status: Fix Committed → Fix Released
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
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.