Re: This is a testmail!

[CToID]

Subject and the content LGTM.
--
Best,
ID

Re: Random freezing on GNOME with AMDGPU

[CToID]

On 2024-07-03 Wed 19:31 UTC+0800, Richard  said:
Have the same issue, though it's pretty much impossible to reproduce it 
reliably. But it seems to be a general issue with the AMDGPU driver in 
Linux 6.1+:
https://bbs.archlinux.org/viewtopic.php?id=292673=2 



It also seems to already have an official tracker: 
https://gitlab.freedesktop.org/drm/amd/-/issues/3163 



Best
Richard



Thanks, good to know I'm not the only one encountering this problem.

--
Best,
ID

Random freezing on GNOME with AMDGPU

[CToID]

Hello folks,

I wonder if any of you who is using an AMD GPU (especially newer ones) 
has encountered the same problem as I do.


My problem is that sometimes the screen just freezes entirely, and I 
have to switch to another TTY and back in order to get it unstuck.  But 
the same freeze will usually happen again after I get the things 
unstuck.  Restart my PC doesn't fix the problem.


Here are some informations about my system:

- CPU/GPU: AMD Ryzen 7 PRO 7840U w/ Radeon 780M Graphics
- vainfo output: in attachment `vainfo-output`
- system log: in attachment `sys-log`

I do find a workaround online somewhere, that is to set 
`amdgpu.vm_update_mode=3` kernel parameter, and it seems to fix the problem.


I never have this kind of problem on Linux distros I used before Debian 
(Void, OpenSUSE,) so if anyone has some idea why this happens, please 
give me some advice, thanks!


--
Best,

IDvainfo: VA-API version: 1.17 (libva 2.12.0)
vainfo: Driver version: Mesa Gallium driver 22.3.6 for AMD Radeon Graphics 
(gfx1103_r1, LLVM 15.0.6, DRM 3.54, 6.6.13+bpo-amd64)
vainfo: Supported profile and entrypoints
  VAProfileH264ConstrainedBaseline: VAEntrypointVLD
  VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice
  VAProfileH264Main   : VAEntrypointVLD
  VAProfileH264Main   : VAEntrypointEncSlice
  VAProfileH264High   : VAEntrypointVLD
  VAProfileH264High   : VAEntrypointEncSlice
  VAProfileHEVCMain   : VAEntrypointVLD
  VAProfileHEVCMain   : VAEntrypointEncSlice
  VAProfileHEVCMain10 : VAEntrypointVLD
  VAProfileHEVCMain10 : VAEntrypointEncSlice
  VAProfileJPEGBaseline   : VAEntrypointVLD
  VAProfileVP9Profile0: VAEntrypointVLD
  VAProfileVP9Profile2: VAEntrypointVLD
  VAProfileAV1Profile0: VAEntrypointVLD
  VAProfileNone   : VAEntrypointVideoProc
Jul 02 15:05:02 thinkpad-btw kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* 
ring gfx_0.0.0 timeout, signaled seq=4611833, emitted seq=4611836
Jul 02 15:05:02 thinkpad-btw kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* 
Process information: process gnome-shell pid 1731 thread gnome-shel:cs0 pid 1756
Jul 02 15:05:02 thinkpad-btw kernel: amdgpu :c3:00.0: amdgpu: GPU reset 
begin!
Jul 02 15:05:02 thinkpad-btw gnome-shell[1731]: amdgpu: The CS has been 
rejected (-125), but the context isn't robust.
Jul 02 15:05:02 thinkpad-btw gnome-shell[1731]: amdgpu: The process will be 
terminated.
Jul 02 15:05:02 thinkpad-btw kernel: amdgpu_cs_ioctl: 12 callbacks suppressed
Jul 02 15:05:02 thinkpad-btw kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* 
Failed to initialize parser -125!
Jul 02 15:05:03 thinkpad-btw kernel: 
[drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES 
failed to response msg=3
Jul 02 15:05:03 thinkpad-btw kernel: [drm:amdgpu_mes_unmap_legacy_queue 
[amdgpu]] *ERROR* failed to unmap legacy queue
Jul 02 15:05:03 thinkpad-btw kernel: 
[drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES 
failed to response msg=3
Jul 02 15:05:03 thinkpad-btw kernel: [drm:amdgpu_mes_unmap_legacy_queue 
[amdgpu]] *ERROR* failed to unmap legacy queue
Jul 02 15:05:03 thinkpad-btw kernel: 
[drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES 
failed to response msg=3
Jul 02 15:05:03 thinkpad-btw kernel: [drm:amdgpu_mes_unmap_legacy_queue 
[amdgpu]] *ERROR* failed to unmap legacy queue
Jul 02 15:05:03 thinkpad-btw kernel: 
[drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES 
failed to response msg=3
Jul 02 15:05:03 thinkpad-btw kernel: [drm:amdgpu_mes_unmap_legacy_queue 
[amdgpu]] *ERROR* failed to unmap legacy queue
Jul 02 15:05:03 thinkpad-btw kernel: 
[drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES 
failed to response msg=3
Jul 02 15:05:03 thinkpad-btw kernel: [drm:amdgpu_mes_unmap_legacy_queue 
[amdgpu]] *ERROR* failed to unmap legacy queue
Jul 02 15:05:03 thinkpad-btw kernel: 
[drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES 
failed to response msg=3
Jul 02 15:05:03 thinkpad-btw kernel: [drm:amdgpu_mes_unmap_legacy_queue 
[amdgpu]] *ERROR* failed to unmap legacy queue
Jul 02 15:05:04 thinkpad-btw kernel: 
[drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES 
failed to response msg=3
Jul 02 15:05:04 thinkpad-btw kernel: [drm:amdgpu_mes_unmap_legacy_queue 
[amdgpu]] *ERROR* failed to unmap legacy queue
Jul 02 15:05:04 thinkpad-btw kernel: 
[drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES 
failed to response msg=3
Jul 02 15:05:04 thinkpad-btw kernel: [drm:amdgpu_mes_unmap_legacy_queue 
[amdgpu]] *ERROR* failed to unmap legacy queue
Jul 02 15:05:04 thinkpad-btw kernel: 
[drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] 

Re: Acer Aspire 5 A515-45 touchpad suddenly stopped working on debian 12.5

[CToID]

https://wiki.archlinux.org/title/Touchpad_Synaptics#Touchpad_not_recognized_after_shutdown_from_Arch

> Certain touchpads (Elantech in particular) will fail to be recognized 
as a device of any sort after a standard shutdown from Arch Linux.


This seems to fit your problem description.

https://wiki.archlinux.org/title/Touchpad_Synaptics#MATE

> MATE will by default overwrite various options for your touchpad.

Maybe your problem has something to do with MATE?

--
Best,

ID

Re: Cannot execute any container using podman run

[CToID]

On 7/2/24 22:38, Jörg Kastning wrote:


:~$ podman run --rm hello-world
conmon: option parsing failed: Unknown option --full-attach
Error: write child: broken pipe


Maybe try run with `podman --log-level=debug run --rm hello-world` to 
get more information?


--
Best,

ID