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.
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.
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.
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)
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.
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.