display standby not wakeable

[RevAngel]

Hello! And all the best for 2021.

I am quite new to this, so please excuse if I am not getting it right.

I am sleeping with music by night. Since I changed to kernel 5.10.4 my system cannot be "woken up" from display standby any more. I have a two minutes timer of inactivity to turn my display off. Everything works as expected when the display is in the standby state for a couple of hours. But when it is in this state for over 6 hours it cannot be woken up again. The screen stays black, the display stays in standby mode.

In the background it seems the system works fine. I can change the volume of the still running music, can even alt-F4 close the music player (Audacious).

I am running Ubuntu 20.04.1 LTS linux 5.10.4-051004-generic Kernel 5.10.4

Only some of the methods shown below this posts worked on my system for gathering more data, ubuntu-bug linux brought an error about a non existent package, cat /proc/version_sig... brought an error about file or folder not found.

lspci-vnvn.log is attached.

System specs:
AMD 2400G using APU for display output, mesa drivers libegl-mesa 21.0~git2012200730.f9ceab~oibaf~f
X370 chipset mainboard (biostar)
16GB RAM DDR4 2933

Please let me know if you need more data and how to gather it. Thank you!

Rev
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.14
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2019-08-28 (494 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
Package: linux (not installed)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
Tags: focal
Uname: Linux 5.10.4-051004-generic x86_64
UnreportableReason: The running kernel is not an Ubuntu kernel
UpgradeStatus: Upgraded to focal on 2020-04-24 (255 days ago)
UserGroups: adm audio cdrom dialout dip fax lpadmin plugdev sambashare saned scanner sudo
_MarkForUpload: True

[Ubuntu Foundations Team Bug Bot (crichton)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1909895/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

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 1909895

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.

[RevAngel (revangel)]

apport information

[Jouni Mettala (jouni-mettala)]

It seems you don't have Ubuntu kernel installed. So ubuntu-bug doesn't work. Perhaps apport-collect doesn't work either. Known steps to reproduce takes several hours.

Please add number of last working kernel. Also did you test v5.11-rc2?

There could be useful information in system logs. You could look folder /var/log where dmesg.0 and Xorg.0.log.old are probably most useful files.

[RevAngel (revangel)]

Last working kernel is either linux-image-unsigned-5.10.1-051001-generic or linux-image-unsigned-5.10.3-051003-generic. Sorry that I cannot specify which one it is, because I only have the uninstallations found in a log (Synaptic). On Ukuu logs I only found the last install log and then a big gap to July (for whatever reason).

But since it is not an official Ubuntu Kernel and therefore not an official Ubuntu bug I uploaded the same information to https://bugzilla.kernel.org/show_bug.cgi?id=211027

If there is reason this bug report here seems wrong, please feel free to close it.

Thank you for all the work you do!

Rev