Hello, since the upgrade to Fedora 38, I keep getting errors in the logs that supposedly affect the AMG GPU.
Unfortunately, waking up from sleep mode sometimes doesn’t work with the current kernel and it also takes up to 30 seconds for the device to wake up and the login screen to be shown.
This is the excerpt from Gnome Log aka Protocol
19:59:39 reporter-system: System encountered a non-fatal error in gmc_v9_0_hw_fini()
WARNING: CPU: 0 PID: 617 at drivers/gpu/drm/amd/amdgpu/amdgpu_irq.c:600 amdgpu_irq_put+0x42/0x70 [amdgpu] [amdgpu]
Use the abrt command-line tool for further analysis or to report
the problem to the appropriate support site.
21:57:18 kernel: amdgpu 0000:03:00.0: amdgpu: SECUREDISPLAY: query securedisplay TA failed. ret 0x0
21:57:18 kernel: amdgpu 0000:03:00.0: amdgpu: Secure display: Generic Failure.
These messages were not displayed in version 37 and the question arises as to whether I am alone with this.
The network itself has not given any information.
Best regards
Did you check by lenovo.com/linux ?
Good morning, unfortunately this is not a certified Linux Lenovo laptop.
Unfortunately, I couldn’t find any information on this either.
Even a new installation does not bring any improvement and there are also other peculiarities in the logs. Waking up from the suspend mode by opening the screen sometimes doesn’t work at all, not even when you press a button and the laptop only reacts from the suspend mode after more than 30 seconds.
LG
To help you to debug we do at least need some more info’s.
A inxi -Fzx would help.
Here is the excerpt from inxi -Fzx
System:
Kernel: 6.2.15-300.fc38.x86_64 arch: x86_64 bits: 64 compiler: gcc
v: 2.39-9.fc38 Desktop: GNOME v: 44.1 Distro: Fedora release 38 (Thirty
Eight)
Machine:
Type: Laptop System: LENOVO product: 82A2 v: Yoga Slim 7 14ARE05
serial: <superuser required>
Mobo: LENOVO model: LNVNB161216 v: SDK0J40709 WIN
serial: <superuser required> UEFI: LENOVO v: DMCN44WW date: 03/17/2023
Battery:
ID-1: BAT1 charge: 54.1 Wh (100.0%) condition: 54.1/60.7 Wh (89.1%)
volts: 17.1 min: 15.4 model: Sunwoda L19D4PF4 status: discharging
CPU:
Info: 8-core model: AMD Ryzen 7 4800U with Radeon Graphics bits: 64
type: MT MCP arch: Zen 2 rev: 1 cache: L1: 512 KiB L2: 4 MiB L3: 8 MiB
Speed (MHz): avg: 1424 high: 1800 min/max: 1400/1800 boost: enabled cores:
1: 1397 2: 1400 3: 1400 4: 1397 5: 1400 6: 1400 7: 1400 8: 1400 9: 1400
10: 1400 11: 1400 12: 1800 13: 1397 14: 1400 15: 1397 16: 1400
bogomips: 57487
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Graphics:
Device-1: AMD Renoir vendor: Lenovo driver: amdgpu v: kernel arch: GCN-5
bus-ID: 03:00.0 temp: 27.0 C
Device-2: Chicony Integrated Camera type: USB driver: uvcvideo
bus-ID: 1-4:2
Display: wayland server: X.Org v: 22.1.9 with: Xwayland v: 22.1.9
compositor: gnome-shell driver: dri: radeonsi gpu: amdgpu
resolution: 1920x1080~60Hz
API: OpenGL v: 4.6 Mesa 23.0.3 renderer: AMD Radeon Graphics (renoir LLVM
16.0.1 DRM 3.49 6.2.15-300.fc38.x86_64) direct-render: Yes
Audio:
Device-1: AMD Renoir Radeon High Definition Audio vendor: Lenovo
driver: snd_hda_intel v: kernel bus-ID: 03:00.1
Device-2: AMD ACP/ACP3X/ACP6x Audio Coprocessor vendor: Lenovo
driver: snd_rn_pci_acp3x v: kernel bus-ID: 03:00.5
Device-3: AMD Family 17h/19h HD Audio vendor: Lenovo driver: snd_hda_intel
v: kernel bus-ID: 03:00.6
API: ALSA v: k6.2.15-300.fc38.x86_64 status: kernel-api
Server-1: PipeWire v: 0.3.70 status: active
Network:
Device-1: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel bus-ID: 01:00.0
IF: wlp1s0 state: up mac: <filter>
Bluetooth:
Device-1: Intel AX200 Bluetooth type: USB driver: btusb v: 0.8 bus-ID: 3-4:2
Report: rfkill ID: hci0 rfk-id: 0 state: up address: see --recommends
Drives:
Local Storage: total: 953.87 GiB used: 32.67 GiB (3.4%)
ID-1: /dev/nvme0n1 vendor: Samsung model: MZVLB1T0HBLR-000L2
size: 953.87 GiB temp: 28.9 C
Partition:
ID-1: / size: 530.42 GiB used: 32.31 GiB (6.1%) fs: btrfs
dev: /dev/nvme0n1p6
ID-2: /boot size: 973.4 MiB used: 340 MiB (34.9%) fs: ext4
dev: /dev/nvme0n1p2
ID-3: /boot/efi size: 275.8 MiB used: 33.5 MiB (12.1%) fs: vfat
dev: /dev/nvme0n1p1
ID-4: /home size: 530.42 GiB used: 32.31 GiB (6.1%) fs: btrfs
dev: /dev/nvme0n1p6
Swap:
ID-1: swap-1 type: zram size: 8 GiB used: 0 KiB (0.0%) dev: /dev/zram0
Sensors:
System Temperatures: cpu: 28.8 C mobo: N/A gpu: amdgpu temp: 27.0 C
Fan Speeds (RPM): N/A
Info:
Processes: 435 Uptime: 2h 7m Memory: 14.98 GiB used: 1.82 GiB (12.1%)
Init: systemd target: graphical (5) Compilers: N/A Packages: 30
note: see --rpm Shell: Bash v: 5.2.15 inxi: 3.3.26
The bios is up to date as of today.
There are also several messages for BTHd, USB Power and a missing ACPI entry that cannot be interpreted.
I think that the problem is not specific to Fedora, because Ubuntu 23.4 as Live Stick also shows these problems. My assumption lies in the kernel itself, because the old version 37 and the Ubuntu 21.4.4 LTS do not show these problems with the kernels of that time.
Unfortunately, I’m not a Linux expert, but in the future I’ll look to get a certified laptop when it retires. As a platform for experimentation, it was too up-to-date and too expensive.
lg
1 Like
You can alternatively use an older kernel like LTS, and check if the message desapear:
https://copr.fedorainfracloud.org/coprs/kwizart/kernel-longterm-6.1/
I have now imported the LTS kernel and there are differences, but there are still errors with kernel 6.1.28.200.
Kernel 6.1.28
16:20:16 bluetoothd: profiles/audio/media.c:client_ready_cb() No object received
16:20:14 gdm-session-wor: gkr-pam: unable to locate daemon control file
16:20:07 bluetoothd: profiles/audio/media.c:client_ready_cb() No object received
18:20:00 kernel: ucsi_acpi USBC000:00: PPM init failed (-110)
18:19:58 kernel: amdgpu 0000:03:00.0: amdgpu: SECUREDISPLAY: query securedisplay TA failed. ret 0x0
18:19:54 kernel: ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20220331/psobject-220)
Kernel 6.2.15.300
19:59:39 reporter-system: System encountered a non-fatal error in gmc_v9_0_hw_fini()
19:59:39 reporter-system: System encountered a non-fatal error in gmc_v9_0_hw_fini()
19:59:11 reporter-system: System encountered a non-fatal error in gmc_v9_0_hw_fini()
19:57:35 systemd: Failed to start app-gnome-user\x2ddirs\x2dupdate\x2dgtk-2447.scope - Application launched by gnome-session-binary.
19:57:34 bluetoothd: profiles/audio/media.c:client_ready_cb() No object received
19:57:32 gdm-session-wor: gkr-pam: unable to locate daemon control file
19:57:26 bluetoothd: profiles/audio/media.c:client_ready_cb() No object received
19:57:22 kernel: Bluetooth: hci0: Malformed MSFT vendor event: 0x02
21:57:19 kernel: ucsi_acpi USBC000:00: PPM init failed (-110)
21:57:18 kernel: amdgpu 0000:03:00.0: amdgpu: SECUREDISPLAY: query securedisplay TA failed. ret 0x0
21:57:18 kernel: amdgpu 0000:03:00.0: amdgpu: SECUREDISPLAY: query securedisplay TA failed. ret 0x0
21:57:18 kernel: amdgpu 0000:03:00.0: amdgpu: Secure display: Generic Failure.
21:57:13 kernel: ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20221020/psobject-220)
Behavior:
Please add on the top of your first request the behavior, so it is straight away visible what the problem is.
I added the title too. Otherwise it looks like you are just chasing errors 
Could you put also the command you used for the error log output? Best direct above your error listing.
If someone comes along with same hardware, we have same/similar output.
no no I’m not looking for mistakes. I’m just surprised that the Lenovo laptop behaved completely differently.
It’s also not that the laptop has problems with Fedora, it also has problems with other distributions with current kernel versions.
If you could possibly write me how I can analyze the WakeON after suspend, it would help me.
With the LTS version of the kernel, it currently takes about 5-10 seconds. With Rel 37, it woke up immediately with a button press or lid sensor.
Many thanks for your help
LG
Ok, outside of the kernel log you can use the bootlog:
# Display bootlog; same as pressing Esc while booting into fedora.
sudo sed $'s/\^\[/\E/g' /var/log/boot.log
An other way to display logs is the journalctl more about journalctl --help or man journalctl
Here an example:
journalctl --lines=8000 |grep -B 2 -A 2 -i "amdgup"
grep -B & -A means before and after and the numbers are lines; use whatever expression in between " "
1 Like
Thank you very much, I will have to deal with filtering the error messages.
Since this is quite extensive, a reply will take a little time.
My apologies and I’ll let you know when I find out more.
Best regards
1 Like
After some research it is proven that the kernel causes problems with the AMD GPUs.
This is even noticeable up to kernel 6.3.1 and mesa 23.03 
.
So it’s not a Fedora problem.
LG