[amdgpu] Gnome Freezes When Second Display is Turned Off

[Arınç ÜNAL]

When second display is turned off, gnome will freeze for about 30 seconds before it starts working again. Sometimes, it freezes indefinitely with the screen glitching, forcing me to reboot. The indefinite freezing happens when I have a lot of windows open on both displays.

Wake up from suspend takes too long - about 30 seconds - and the “Join Displays” option changes to “Single Display” and the primary display option changes to the second display.

My graphics card is AMD Radeon VII. I run into this issue on a fresh Ubuntu 22.04 installation. Displays are 1440p and 1080p @ 144Hz.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DisplayManager: gdm3
DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2022-06-25 (18 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
Package: gnome-shell 42.2-0ubuntu0.2
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39
RelatedPackageVersions: mutter-common 42.2-0ubuntu1
Tags: jammy third-party-packages
Uname: Linux 5.15.0-41-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare 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 Libera.chat.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1981559/+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.]

[Daniel van Vugt (vanvugt)]

The screenshot in comment #1 looks like a kernel/driver bug. Do you always see that corruption when the bug happens?

Also, next time the bug happens, please wait for it to come back and then run:

  journalctl -b0 > journal.txt

and attach the resulting text file here.

[Daniel van Vugt (vanvugt)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal:

  apport-collect 1981559

When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs.

[Arınç ÜNAL (arinc9)]

apport information

[Arınç ÜNAL (arinc9)]

apport information

[Arınç ÜNAL (arinc9)]

apport information

[Arınç ÜNAL (arinc9)]

apport information

[Arınç ÜNAL (arinc9)]

apport information

[Arınç ÜNAL (arinc9)]

apport information

[Arınç ÜNAL (arinc9)]

> The screenshot in comment #1 looks like a kernel/driver bug. Do you always see that corruption when the bug happens?

No. Sometimes it just freezes for around 30 seconds and everything gets back to normal. Sometimes the behaviour on the screenshot happens and it won't ever get back to normal (I sat there for 5 minutes before giving up, had a bit of ghosting on the display afterwards because of the glitch keep turning the pixels on and off randomly.)

Here's the journal log for the ~30 seconds freeze. I disabled the second display at 07:58:33 and the main display started to be responsive at 07:59:19.

Thanks for looking over this!

[Daniel van Vugt (vanvugt)]

Thanks.

The log in comment #11 indeed shows amdgpu kernel driver errors in the time range you mention. So this is a kernel bug.

Please try these two kernels separately:

  https://kernel.ubuntu.com/~kernel-ppa/mainline/drm-tip/2022-07-08/amd64/
  https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.18.11/amd64/

When testing each you need to download all the .deb files and install them together:

  sudo dpkg -i *.deb

[Arınç ÜNAL (arinc9)]

I have tried both kernels and can happily say the issue does not exist! It's so snappy now, much faster than Windows 11.

Sorry for wasting your time, I should've tried newer kernels before opening a bug report. I'm not sure how to close the bug report.

[Daniel van Vugt (vanvugt)]

No problem - this bug is still open and still valid. If you have time then please try to figure out which kernel version fixed it between 5.15 and 5.18.11 ...

https://kernel.ubuntu.com/~kernel-ppa/mainline/

[Arınç ÜNAL (arinc9)]

I have tried 5.17 and 5.16. The issue is not there. It's not fixed on 5.15.54 too. So it's fixed somewhere between 5.15 and 5.16.

[Daniel van Vugt (vanvugt)]

Thanks. If you can identify the exact revision 5.15.x or 5.16.y that fixed it then that would be most helpful. But if you don't have time then that's fine.

[Daniel van Vugt (vanvugt)]

Actually we have 5.19 on the way in Ubuntu 22.10 so you don't need to do anything more. We can declare it fix committed already.