Fix resume failure on Tongfang GMxZGxx Barebone

Bug #1936583 reported by Werner Sembach
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Undecided
Unassigned
Hirsute
Won't Fix
Undecided
Unassigned

Bug Description

SRU Justification:

Impact:
The Tongfang GMxZGxx Barebone and propably also other new AMD based laptops fail to resume after suspend, and reboot instead with the 5.11 or earlier kernel.

Fix:
There is a quirk in newer linux kernel that can easily applied to 5.11 also.

Testcase:
A colleauge tested on a Tongfang GMxZGxx. The Ubuntu 5.11 kernel without the patch fails to resume, with the patch the issue is gone.

Patch on upstream:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d1658268e43980c071dbffc3d894f6f6c4b6732a

Commit-hash:
d1658268e43980c071dbffc3d894f6f6c4b6732a

Werner Sembach (matombo)
description: updated
Revision history for this message
Werner Sembach (matombo) wrote (last edit ):

(I messed up: The patch is already in 5.11, what I somehow missed when checking for it.)

Scratch that: the patch is only in 5.4 not in 5.11

Revision history for this message
Mario Limonciello (superm1) wrote :

FYI, that patch is intended specifically for s2idle, which will not work on those older kernels without significant other backports. Are you sure that this patch alone really helps the issue?

Revision history for this message
Werner Sembach (matombo) wrote :

Yes, this patch alone fixed the problem.

I tested 5.11.0-26 today, which has this patch included and it works now ^^.

Changed in linux (Ubuntu Hirsute):
status: New → Fix Committed
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1936583

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Werner Sembach (matombo) wrote :

The issue was fixed in focal hwe 5.11.0-26 kernel in proposed, but props up in hwe 5.11.0-27 again because hwe-27 is directly based on hwe-25 and not on -26

Very unusual pattern in the kernel log: https://kernel.ubuntu.com/git/ubuntu/ubuntu-focal.git/log/?h=Ubuntu-hwe-5.11-5.11.0-27.29_20.04.1
Hirsute-25 + HWE Alterations -> HWE-25 + Patches + Additional HWE Alternations -> HWE-27
as oposed to the normal way https://kernel.ubuntu.com/git/ubuntu/ubuntu-focal.git/log/?h=Ubuntu-hwe-5.11-5.11.0-26.28_20.04.1
Hirsute-26 + HWE Alterations -> HWE-26

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Werner Sembach (matombo) wrote (last edit ):

Seems to be fixed again in 5.11.0-34

Revision history for this message
Brian Murray (brian-murray) wrote :

The Hirsute Hippo has reached End of Life, so this bug will not be fixed for that release.

Changed in linux (Ubuntu Hirsute):
status: Fix Committed → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers