Suspend screen bug Gnome and Gnome with video card AMD RX6500XT

Bug #1994485 reported by greenmandd
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Suspend screen bug Gnome 42 and Gnome 43 with video card AMD RX6500XT

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: gnome-shell 43.0-1ubuntu2
ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
Uname: Linux 5.19.0-23-generic x86_64
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Wed Oct 26 09:35:26 2022
DisplayManager: gdm3
InstallationDate: Installed on 2022-10-26 (0 days ago)
InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
RelatedPackageVersions: mutter-common 43.0-1ubuntu4
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
greenmandd (sunget) wrote :
Revision history for this message
greenmandd (sunget) wrote :

After I lock my screen and let it blank, moving the mouse or pressing any key on the keyboard won't wake it up. This bug i can represent on Gnome 38, 42 and 43 only with video card AMD RX6500XT

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

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.

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.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

If no evidence of a crash can be found then next time it happens please:

1. Wait 10 seconds.

2. Reboot.

3. Run:

   journalctl -b-1 > prevboot.txt

4. Attach the resulting text file here.

Changed in gnome-shell (Ubuntu):
status: New → Incomplete
Revision history for this message
greenmandd (sunget) wrote :

Hello Daniel, sorry for my late replay. I have replaced AMD RX6500XT with another model and unfortunately i wont be able to produce crash report.

Changed in gnome-shell (Ubuntu):
status: Incomplete → Invalid
Revision history for this message
greenmandd (sunget) wrote :
Download full text (283.8 KiB)

Hello Daniel, i was able once again to test RX6500XT. I am sending journal request stat

дек 23 17:14:11 d-3600xt-22 kernel: Linux version 5.15.0-56-generic (buildd@lcy02-amd64-004) (gcc (Ubuntu 11.3.0-1ubuntu1~22.04) 11.3.0, GNU ld (GNU Binutils for Ubuntu) 2.38) #62-Ubuntu SMP Tue Nov 22 19:54:14 UTC 2022 (Ubuntu 5.15.0-56.62-generic 5.15.64)
дек 23 17:14:11 d-3600xt-22 kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.15.0-56-generic root=UUID=ef78856e-f2f2-432c-afef-3b130732924c ro quiet splash vt.handoff=7
дек 23 17:14:11 d-3600xt-22 kernel: KERNEL supported cpus:
дек 23 17:14:11 d-3600xt-22 kernel: Intel GenuineIntel
дек 23 17:14:11 d-3600xt-22 kernel: AMD AuthenticAMD
дек 23 17:14:11 d-3600xt-22 kernel: Hygon HygonGenuine
дек 23 17:14:11 d-3600xt-22 kernel: Centaur CentaurHauls
дек 23 17:14:11 d-3600xt-22 kernel: zhaoxin Shanghai
дек 23 17:14:11 d-3600xt-22 kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
дек 23 17:14:11 d-3600xt-22 kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
дек 23 17:14:11 d-3600xt-22 kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
дек 23 17:14:11 d-3600xt-22 kernel: x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256
дек 23 17:14:11 d-3600xt-22 kernel: x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'compacted' format.
дек 23 17:14:11 d-3600xt-22 kernel: signal: max sigframe size: 1776
дек 23 17:14:11 d-3600xt-22 kernel: BIOS-provided physical RAM map:
дек 23 17:14:11 d-3600xt-22 kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009ffff] usable
дек 23 17:14:11 d-3600xt-22 kernel: BIOS-e820: [mem 0x00000000000a0000-0x00000000000fffff] reserved
дек 23 17:14:11 d-3600xt-22 kernel: BIOS-e820: [mem 0x0000000000100000-0x0000000009bfefff] usable
дек 23 17:14:11 d-3600xt-22 kernel: BIOS-e820: [mem 0x0000000009bff000-0x0000000009ffffff] reserved
дек 23 17:14:11 d-3600xt-22 kernel: BIOS-e820: [mem 0x000000000a000000-0x000000000a1fffff] usable
дек 23 17:14:11 d-3600xt-22 kernel: BIOS-e820: [mem 0x000000000a200000-0x000000000a210fff] ACPI NVS
дек 23 17:14:11 d-3600xt-22 kernel: BIOS-e820: [mem 0x000000000a211000-0x000000000affffff] usable
дек 23 17:14:11 d-3600xt-22 kernel: BIOS-e820: [mem 0x000000000b000000-0x000000000b01ffff] reserved
дек 23 17:14:11 d-3600xt-22 kernel: BIOS-e820: [mem 0x000000000b020000-0x00000000bb434fff] usable
дек 23 17:14:11 d-3600xt-22 kernel: BIOS-e820: [mem 0x00000000bb435000-0x00000000bcb77fff] reserved
дек 23 17:14:11 d-3600xt-22 kernel: BIOS-e820: [mem 0x00000000bcb78000-0x00000000bcba5fff] ACPI data
дек 23 17:14:11 d-3600xt-22 kernel: BIOS-e820: [mem 0x00000000bcba6000-0x00000000bd280fff] ACPI NVS
дек 23 17:14:11 d-3600xt-22 kernel: BIOS-e820: [mem 0x00000000bd281000-0x00000000bddfefff] reserved
дек 23 17:14:11 d-3600xt-22 kernel: BIOS-e820: [mem 0x00000000bddff000-0x00000000beffffff] usable
дек 23 17:14:11 d-3600xt-22 kernel: BIOS-e820: [mem 0x00000000bf000000-0x00000000bfffffff] reserved
дек 23 17:14:11 d-3600xt-22 kernel: BIOS-e820: [mem 0x00000000f0000000-0x00000000f7ffffff] reserved
дек 23 17:14:11 d-3600xt-22 kernel: BIOS-e820: [mem 0x00000000fd200000-0x00000000fd2fffff] reserved
д...

Changed in gnome-shell (Ubuntu):
status: Invalid → New
Revision history for this message
greenmandd (sunget) wrote (last edit ):

With different AMD CPU`s (Ryzon family 36000XT, 3800XT, 3900X, 5600X) and B450 and B550 chipsets i am getting the same issue when i lock the screen. The interesting thing is that with Intel CPU (i5-7500) and motherboard chipset (H270), this issue is not present. I was able to wake up the PC from idle without any problems.

Revision history for this message
Daniel van Vugt (vanvugt) wrote (last edit ):

In comment #6 it looks like gnome-shell is stuck on a bug in the amdgpu kernel driver. But I should have been able to tell that from the beginning...

дек 23 17:09:14 d-3600xt-22 kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0 timeout, signaled seq=2186, emitted seq=2188
дек 23 17:09:14 d-3600xt-22 kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process gnome-shell pid 1818 thread gnome-shel:cs0 pid 1835
дек 23 17:09:14 d-3600xt-22 kernel: amdgpu 0000:0c:00.0: amdgpu: GPU reset begin!

tags: added: amdgpu
affects: gnome-shell (Ubuntu) → linux (Ubuntu)
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 1994485

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
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
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.