[amdgpu] freeze occurs when wayland is connected to a second monitor

[hidaris]

I didn't encounter this bug with ubuntu 21.10 and when I tried to use x11 in 22.04 everything was fine, so it seems to be related to mutter42. And my computer is an amd 47 4800u machine and should only have one integrated graphics card

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell 42.0-2ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
Uname: Linux 5.15.0-25-generic x86_64
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sun Apr 24 00:38:15 2022
DisplayManager: gdm3
InstallationDate: Installed on 2022-04-23 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
RelatedPackageVersions: mutter-common 42.0-3ubuntu2
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DisplayManager: gdm3
DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2022-04-26 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
Package: mutter
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
RelatedPackageVersions: mutter-common 42.0-3ubuntu2
Tags: jammy wayland-session
Uname: Linux 5.15.0-27-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True

[hidaris (hidaris1208)]

I'm not particularly sure how to provide more detailed information about this, but point me in the right direction if you need to and I'll do my best to help locate the problem

[Arnaud de Saint Méloir (arnaudsm)]

Same bug on 22.04, fresh install, Ryzen 5800U.
Workaround : Enable fractional scaling, plug, then disable it. Solved the issue permanently.

[Daniel van Vugt (vanvugt)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps:

1. Look in /var/crash for crash files and if found run:
    ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us.

3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1.

Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself.

[rc (rrrccc)]

same issue here, fresh install 22.04, nvidia 510.60.02 driver
in wayland session, if I plug-in a usb-c monitor, the system freezes. after I unplug the usb-c monitor the system resumes responsive. there is no need to press power button to hard reboot.
in X11 no such issue

[hidaris (hidaris1208)]

Thanks for your advice.
After reproduction the freezes error, it's strange that there is no crash files in /var/crash.
Could you please kindly check that when you're free?
Thanks again!

[hidaris (hidaris1208)]

I saw some error messages in the syslog that might be relevant, so post them first

[Daniel van Vugt (vanvugt)]

Comment #7 looks like a kernel or BIOS bug, but hopefully that's not the main issue.

Next time the freeze occurs please:

1. Wait 10 seconds.

2. Reboot.

3. Run:

   journalctl -b-1 > prevboot.txt

4. Attach the resulting text file here.

[hidaris (hidaris1208)]

Thanks, I put it in the attachment, this time there are many gnome shell related errors.

[hidaris (hidaris1208)]

The kernel or BIOS bug should not be the cause of the problem here, I get similar reports in 21.10 but it seems harmless, also in comment #7 there is mention of a dash to dock exception, I have tried disabling the dock inside extension manager but freeze still happens, so It seems to be a related issue, but not the cause of freeze happening.

[Daniel van Vugt (vanvugt)]

I'll assign this to the kernel too, in case it's a system call that's blocking.

[Daniel van Vugt (vanvugt)]

Maybe related: bug 1970495

[Daniel van Vugt (vanvugt)]

hidaris, are you plugging the monitor into the laptop or into a dock?

[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 1970043

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.

[hidaris (hidaris1208)]

apport information

[hidaris (hidaris1208)]

apport information

[hidaris (hidaris1208)]

apport information

[hidaris (hidaris1208)]

apport information

[hidaris (hidaris1208)]

apport information

[hidaris (hidaris1208)]

Yes I am using type-c to plug the monitor into my laptop and it looks a lot like the problem you quoted

[hidaris (hidaris1208)]

I'll try the driver you mentioned and get back to you later.

[hidaris (hidaris1208)]

I installed that driver and rebooted, but the problem persists. Also, no dock is used in my case, only usb-c.

[Daniel van Vugt (vanvugt)]

Thanks, though you don't need the evdi driver if there is no dock/adapter box. A monitor connected directly to a USB-C port is just a native DisplayPort connection.

[Daniel van Vugt (vanvugt)]

Also maybe related: bug 1969422

[hidaris (hidaris1208)]

Very strange, with comment 3 I can avoid freeze but have to turn on fractional scaling, not a permanent way to solve the problem, do I need to capture anything between the two states again?

[Daniel van Vugt (vanvugt)]

Fractional scaling certainly changes the display layout logic so it's a plausible if surprising workaround.

I would only ask anyone reading this to please verify you're not seeing any files left in /var/crash when the bug occurs.

[John A. Lewis (pointful)]

I am seeing the same problem with using a USB-C monitor connected directly to my laptop. I do have one crash file in /var/crash -- see attached. The file might be a red-herring though caused only by me trying to restart gnome-shell once it was stuck.

[Tobias Grundmann (lk-tobias-grundmann)]

same problem here.
Dell XPS13, intel graphics,
second monitor connected via USB-C Hub. Mouse connected to same hub can be moved for halve a second after plugging in the hub, then everything freezes. X11 works.

[Tobias Grundmann (lk-tobias-grundmann)]

boot log

[Tobias Grundmann (lk-tobias-grundmann)]

after enabling fractional scaling you can even disable it again after plugging in the hub/second monitor (useful because it's blurry).
So my workaround looks like this:
boot -> freeze -> unplug hub -> enable fractional scaling -> plug hub in again -> disable fractional scaling -> adjust display arrangement -> work

additional observation: when the displays freeze the taskbar is cut off halfway, like it wouldn't fit completely on the screen.

[Daniel van Vugt (vanvugt)]

John, please report your crash file using the 'ubuntu-bug' command. Or 'apport-cli' if that fails. Then you will get a new bug created.

[Launchpad Janitor (janitor)]

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

[hidaris (hidaris1208)]

This looks like a related question https://github.com/micheleg/dash-to-dock/issues/1705

copy log here:
Apr 09 01:36:01 satriani gnome-shell[118687]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->logical_monitors)' failed
Apr 09 01:36:01 satriani gnome-shell[118687]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed
Apr 09 01:36:01 satriani gnome-shell[118687]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->logical_monitors)' failed
Apr 09 01:36:01 satriani gnome-shell[118687]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed
Apr 09 01:36:01 satriani gnome-shell[118687]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->logical_monitors)' failed
Apr 09 01:36:01 satriani gnome-shell[118687]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed
Apr 09 01:36:01 satriani gnome-shell[118687]: meta_display_get_monitor_in_fullscreen: assertion 'monitor >= 0 && monitor < n_logical_monitors' failed
Apr 09 01:36:01 satriani gnome-shell[118687]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->logical_monitors)' failed
Apr 09 01:36:01 satriani gnome-shell[118687]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed
...
Apr 09 01:36:14 satriani gnome-shell[118687]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
                                                _loadFile@resource:///org/gnome/shell/ui/background.js:493:20
                                                _load@resource:///org/gnome/shell/ui/background.js:523:14
                                                _init@resource:///org/gnome/shell/ui/background.js:283:14
                                                Background@resource:///org/gnome/shell/ui/background.js:239:4
                                                getBackground@resource:///org/gnome/shell/ui/background.js:614:30
                                                _createBackgroundActor@resource:///org/gnome/shell/ui/background.js:785:49
                                                BackgroundManager@resource:///org/gnome/shell/ui/background.js:711:37
                                                _createBackgroundManager@resource:///org/gnome/shell/ui/layout.js:461:27
                                                _updateBackgrounds@resource:///org/gnome/shell/ui/layout.js:507:34
                                                _monitorsChanged@resource:///org/gnome/shell/ui/layout.js:571:14
Apr 09 01:36:14 satriani gnome-shell[118687]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
                                                _loadF...

[Daniel van Vugt (vanvugt)]

It looks like you have copied someone else's log from an unrelated bug? That shows bug 1717170 and bug 1965820. We don't need to discuss those here.

[Ivan Vergés (ivanverges)]

Comment #30 saved my day! I started to be affected by this bug just today, everything fine until now.