After upgrade to linux-image-5.13.0-27-generic, screen doesn't recover from blanking

Bug #1958494 reported by Sebastian Nohn
24
This bug affects 5 people
Affects Status Importance Assigned to Milestone
linux-signed-hwe-5.13 (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

After screen was blanked (meta-L; lid closed) it wakes up with an erratic pattern, it can't recover from (except power off, power on).

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.13.0-27-generic 5.13.0-27.29~20.04.1
ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-27-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu Jan 20 07:41:10 2022
InstallationDate: Installed on 2021-09-29 (112 days ago)
InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
SourcePackage: linux-signed-hwe-5.13
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Sebastian Nohn (sebastian-nohn) wrote :
Revision history for this message
Sebastian Nohn (sebastian-nohn) wrote :
Revision history for this message
Sebastian Nohn (sebastian-nohn) wrote (last edit ):

According to my logs, in the past few days these versions have worked fine:

5.10.0-1045.47-oem
5.11.0-37.41~20.04.2-generic

summary: - After upgrade to linux-image-5.13.0-27-generic, screen doesn't recovere
+ After upgrade to linux-image-5.13.0-27-generic, screen doesn't recover
from blanking
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in linux-signed-hwe-5.13 (Ubuntu):
status: New → Confirmed
Revision history for this message
Yury (zyrikby) wrote :

Exactly the same image, however before the login screen after a reboot.
Both available version of the kernel are affected: 5.13.0-23 and 5.13.0-25.
Works fine with 5.11.0-46

Revision history for this message
Sebastian Nohn (sebastian-nohn) wrote :

Problem can be reproduced with 5.13.0-28.31~20.04.1 as well.

Revision history for this message
Yegor Panov (maxpayne1986) wrote :

Problem reproduced with 5.13.0-30-generic (20.04.3 LTS)

Revision history for this message
Sebastian Nohn (sebastian-nohn) wrote :

Seems like it is fixed in kernel 5.14: https://gitlab.freedesktop.org/drm/amd/-/issues/1783

Any chance to get the fix backported to 20.04?

Revision history for this message
Yegor Panov (maxpayne1986) wrote (last edit ):

This is a tricky bug, it comes back sometimes from version to version. Will be great fix it in the 20.04.4 LTS

Revision history for this message
Sebastian Nohn (sebastian-nohn) wrote :

Seems fixed in linux-image-5.13.0-39-generic 5.13.0-39.44~20.04.1

Revision history for this message
Yegor Panov (maxpayne1986) wrote :

Good. I just install kernel 5.14.21 one month ago and all works fine for me

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.