You are not logged in.

#1 2024-08-23 03:53:56

frogmech
Member
Registered: 2024-08-23
Posts: 6

Display frozen, computer still working

I'm getting this error at random on an ASUS Vivobook S 16 with a Ryzen AI 9 365: "kwin_wayland_drm: Pageflip timed out! This is a kernel bug" Sometimes it happens about a minute after booting, sometimes up to ~20 minutes after. The screen freezes, but the computer is still "working" both with the laptop itself and SSH. I tested it by blindly navigating to terminal, creating a folder, and then I was able to see the folder via SSH. Here's the log.

Offline

#2 2024-08-23 05:23:05

jnnj
Member
Registered: 2024-08-22
Posts: 5

Re: Display frozen, computer still working

Hi frogmech,
what is Your kernel (uname -v) and Plasma version? Looking to this thread, seems to be problem of specify version of kernel (and Plasma). Try to get different - newest kernel.

This ArchLinux bbs's thread also can be relevant for You. It is about nvidia drivers downgrade. So You can try to downgrade Your AMD GPU drivers.

Cya J.

Offline

#3 2024-08-23 07:01:55

seth
Member
Registered: 2012-09-03
Posts: 57,369

Re: Display frozen, computer still working

Aug 22 23:02:50 archlinux kernel: ------------[ cut here ]------------
Aug 22 23:02:50 archlinux kernel: WARNING: CPU: 8 PID: 142 at drivers/gpu/drm/amd/amdgpu/../display/dc/dce/dmub_psr.c:124 dmub_psr_get_state+0xb1/0xd0 [amdgpu]
Aug 22 23:02:50 archlinux kernel: Modules linked in: snd_seq_dummy snd_hrtimer snd_seq snd_seq_device ccm hid_sensor_als snd_hda_scodec_cs35l56_spi vfat fat joydev mousedev snd_acp_legacy_mach snd_acp_mach snd_soc_nau8821 snd_acp3x_rn snd_acp70 snd_acp_i2s snd_acp_pdm snd_soc_dmic snd_acp_pcm snd_sof_amd_acp63 snd_sof_amd_vangogh snd_sof_amd_rembrandt snd_sof_amd_renoir snd_sof_amd_acp snd_sof_pci snd_sof_xtensa_dsp snd_sof snd_sof_utils snd_pci_ps snd_amd_sdw_acpi soundwire_amd mt7925e soundwire_generic_allocation mt7925_common soundwire_bus mt792x_lib snd_hda_codec_realtek mt76_connac_lib snd_soc_core mt76 snd_hda_codec_generic snd_hda_scodec_component snd_hda_codec_hdmi snd_compress ac97_bus snd_hda_intel snd_intel_dspcfg mac80211 snd_ctl_led uvcvideo snd_pcm_dmaengine snd_hda_scodec_cs35l56_i2c snd_intel_sdw_acpi snd_rpl_pci_acp6x videobuf2_vmalloc kvm_amd snd_hda_scodec_cs35l56 snd_hda_codec uvc snd_acp_pci snd_hda_cirrus_scodec videobuf2_memops libarc4 snd_acp_legacy_common hid_sensor_prox snd_soc_cs35l56_shared snd_hda_core
Aug 22 23:02:50 archlinux kernel:  videobuf2_v4l2 btusb snd_pci_acp6x hid_sensor_trigger snd_hwdep kvm snd_hda_cs_dsp_ctls btrtl videodev snd_pci_acp5x cfg80211 industrialio_triggered_buffer asus_nb_wmi ucsi_acpi snd_rn_pci_acp3x snd_soc_cs_amp_lib snd_pcm btintel kfifo_buf snd_acp_config cs_dsp videobuf2_common asus_wmi typec_ucsi sp5100_tco hid_sensor_iio_common btbcm snd_timer snd_soc_acpi hid_multitouch btmtk bluetooth industrialio mc rapl typec sparse_keymap wmi_bmof snd pcspkr amd_pmf thunderbolt amdtee snd_pci_acp3x soundcore rfkill k10temp i2c_piix4 roles amd_sfh i2c_hid_acpi platform_profile serial_multi_instantiate amd_pmc i2c_hid mac_hid i2c_dev loop nfnetlink ip_tables x_tables ext4 crc32c_generic crc16 mbcache jbd2 dm_crypt cbc encrypted_keys trusted asn1_encoder tee dm_mod hid_sensor_hub hid_generic usbhid amdgpu crct10dif_pclmul amdxcp crc32_pclmul i2c_algo_bit crc32c_intel drm_ttm_helper polyval_clmulni ttm polyval_generic gf128mul drm_exec ghash_clmulni_intel gpu_sched serio_raw sha512_ssse3 sdhci_pci atkbd
Aug 22 23:02:50 archlinux kernel:  drm_suballoc_helper sha256_ssse3 cqhci drm_buddy sha1_ssse3 libps2 nvme aesni_intel vivaldi_fmap sdhci drm_display_helper crypto_simd nvme_core xhci_pci cryptd mmc_core ccp video cec i8042 xhci_pci_renesas nvme_auth wmi serio
Aug 22 23:02:50 archlinux kernel: CPU: 8 PID: 142 Comm: kworker/u82:0 Not tainted 6.10.6-arch1-1 #1 703d152c24f1971e36f16e505405e456fc9e23f8
Aug 22 23:02:50 archlinux kernel: Hardware name: ASUSTeK COMPUTER INC. ASUS Zenbook S 16 UM5606WA_UM5606WA/UM5606WA, BIOS UM5606WA.304 06/17/2024
Aug 22 23:02:50 archlinux kernel: Workqueue: events_unbound commit_work
Aug 22 23:02:50 archlinux kernel: RIP: 0010:dmub_psr_get_state+0xb1/0xd0 [amdgpu]
Aug 22 23:02:50 archlinux kernel: Code: 28 00 00 00 75 31 48 83 c4 10 5b 5d 41 5c 41 5d 41 5e c3 cc cc cc cc 83 c3 01 41 c7 04 24 ff 00 00 00 81 fb e9 03 00 00 75 8a <0f> 0b eb c8 3d ff 00 00 00 75 c1 eb f3 e8 cd 50 e7 e9 66 66 2e 0f
Aug 22 23:02:50 archlinux kernel: RSP: 0018:ffffb3de40687a98 EFLAGS: 00010246
Aug 22 23:02:50 archlinux kernel: RAX: 0000000000000062 RBX: 00000000000003e9 RCX: 0000000000000000
Aug 22 23:02:50 archlinux kernel: RDX: 0000000000000000 RSI: 00000000000036aa RDI: ffff94e759380000
Aug 22 23:02:50 archlinux kernel: RBP: 0000000000000000 R08: 0000000000000002 R09: ffff94e746678b80
Aug 22 23:02:50 archlinux kernel: R10: 0000000000000007 R11: 0000000000000000 R12: ffffb3de40687adc
Aug 22 23:02:50 archlinux kernel: R13: ffffb3de40687a9c R14: ffff94e751540360 R15: ffffb3de40687bbc
Aug 22 23:02:50 archlinux kernel: FS:  0000000000000000(0000) GS:ffff94ec86400000(0000) knlGS:0000000000000000
Aug 22 23:02:50 archlinux kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Aug 22 23:02:50 archlinux kernel: CR2: 000077c5e59ef000 CR3: 0000000587020000 CR4: 0000000000f50ef0
Aug 22 23:02:50 archlinux kernel: PKRU: 55555554
Aug 22 23:02:50 archlinux kernel: Call Trace:
Aug 22 23:02:50 archlinux kernel:  <TASK>
Aug 22 23:02:50 archlinux kernel:  ? dmub_psr_get_state+0xb1/0xd0 [amdgpu 16e9d602f36697d160fe0ce54615bcf93ecc06cd]
Aug 22 23:02:50 archlinux kernel:  ? __warn.cold+0x8e/0xe8
Aug 22 23:02:50 archlinux kernel:  ? dmub_psr_get_state+0xb1/0xd0 [amdgpu 16e9d602f36697d160fe0ce54615bcf93ecc06cd]
Aug 22 23:02:50 archlinux kernel:  ? report_bug+0xff/0x140
Aug 22 23:02:50 archlinux kernel:  ? handle_bug+0x3c/0x80
Aug 22 23:02:50 archlinux kernel:  ? exc_invalid_op+0x17/0x70
Aug 22 23:02:50 archlinux kernel:  ? asm_exc_invalid_op+0x1a/0x20
Aug 22 23:02:50 archlinux kernel:  ? dmub_psr_get_state+0xb1/0xd0 [amdgpu 16e9d602f36697d160fe0ce54615bcf93ecc06cd]
Aug 22 23:02:50 archlinux kernel:  ? dmub_psr_get_state+0x53/0xd0 [amdgpu 16e9d602f36697d160fe0ce54615bcf93ecc06cd]
Aug 22 23:02:50 archlinux kernel:  dmub_psr_enable+0xc7/0x110 [amdgpu 16e9d602f36697d160fe0ce54615bcf93ecc06cd]
Aug 22 23:02:50 archlinux kernel:  edp_set_psr_allow_active+0x27d/0x3b0 [amdgpu 16e9d602f36697d160fe0ce54615bcf93ecc06cd]
Aug 22 23:02:50 archlinux kernel:  amdgpu_dm_psr_disable+0x59/0x80 [amdgpu 16e9d602f36697d160fe0ce54615bcf93ecc06cd]
Aug 22 23:02:50 archlinux kernel:  amdgpu_dm_atomic_commit_tail+0x3218/0x3db0 [amdgpu 16e9d602f36697d160fe0ce54615bcf93ecc06cd]
Aug 22 23:02:50 archlinux kernel:  ? generic_reg_get+0x21/0x40 [amdgpu 16e9d602f36697d160fe0ce54615bcf93ecc06cd]
Aug 22 23:02:50 archlinux kernel:  ? dma_fence_default_wait+0x8b/0x250
Aug 22 23:02:50 archlinux kernel:  ? wait_for_completion_timeout+0x130/0x180
Aug 22 23:02:50 archlinux kernel:  ? dma_fence_wait_timeout+0x108/0x140
Aug 22 23:02:50 archlinux kernel:  commit_tail+0x91/0x130
Aug 22 23:02:50 archlinux kernel:  process_one_work+0x17b/0x330
Aug 22 23:02:50 archlinux kernel:  worker_thread+0x2e2/0x410
Aug 22 23:02:50 archlinux kernel:  ? __pfx_worker_thread+0x10/0x10
Aug 22 23:02:50 archlinux kernel:  kthread+0xcf/0x100
Aug 22 23:02:50 archlinux kernel:  ? __pfx_kthread+0x10/0x10
Aug 22 23:02:50 archlinux kernel:  ret_from_fork+0x31/0x50
Aug 22 23:02:50 archlinux kernel:  ? __pfx_kthread+0x10/0x10
Aug 22 23:02:50 archlinux kernel:  ret_from_fork_asm+0x1a/0x30
Aug 22 23:02:50 archlinux kernel:  </TASK>
Aug 22 23:02:50 archlinux kernel: ---[ end trace 0000000000000000 ]---

but that'S well into the problem, it seems and after

Aug 22 23:00:48 archlinux kwin_wayland[1088]: kwin_scene_opengl: 0x2: GL_INVALID_OPERATION in glDrawBuffers(unsupported buffer GL_BACK_LEFT)
Aug 22 23:00:48 archlinux kwin_wayland[1088]: kwin_scene_opengl: 0x2: GL_INVALID_OPERATION in glDrawBuffers(unsupported buffer GL_BACK_LEFT)
Aug 22 23:00:48 archlinux kwin_wayland[1088]: kwin_scene_opengl: 0x2: GL_INVALID_OPERATION in glDrawBuffers(unsupported buffer GL_BACK_LEFT)
Aug 22 23:00:48 archlinux kwin_wayland[1088]: kwin_scene_opengl: 0x2: GL_INVALID_OPERATION in glDrawBuffers(unsupported buffer GL_BACK_LEFT)
Aug 22 23:00:48 archlinux kwin_wayland[1088]: kwin_scene_opengl: 0x2: GL_INVALID_OPERATION in glDrawBuffers(unsupported buffer GL_BACK_LEFT)
Aug 22 23:00:48 archlinux kwin_wayland[1088]: kwin_scene_opengl: 0x2: GL_INVALID_OPERATION in glDrawBuffers(unsupported buffer GL_BACK_LEFT)

Please post the entire journal of the affected boot, not random excerpts.
If it'S PSR, you can disable that: https://wiki.archlinux.org/title/AMDGPU … parameters
=> https://raw.githubusercontent.com/torva … d_shared.h and see the DC_DEBUG_MASK

Offline

#4 2024-08-23 14:38:50

frogmech
Member
Registered: 2024-08-23
Posts: 6

Re: Display frozen, computer still working

My kernel version is 6.10.6 and my KDE Plasma version is 6.1.4. Here is the full log of a different boot with the same issue: https://pastebin.com/7HVL8gCm Also if I run the "plasmashell" command, I get this:

qt.qpa.xcb: could not connect to display 
qt.qpa.plugin: From 6.5.0, xcb-cursor0 or libxcb-cursor0 is needed to load the Qt xcb platform plugin.
qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.

Available platform plugins are: minimalegl, linuxfb, eglfs, vkkhrdisplay, wayland, wayland-egl, minimal, xcb, vnc, offscreen.

Aborted (core dumped)

Offline

#5 2024-08-23 15:00:10

seth
Member
Registered: 2012-09-03
Posts: 57,369

Re: Display frozen, computer still working

Aug 23 09:50:33 archlinux kwin_wayland[1261]: kwin_wayland_drm: Pageflip timed out! This is a kernel bug
Aug 23 09:50:38 archlinux kwin_wayland[1261]: kwin_wayland_drm: Pageflip timed out! This is a kernel bug
Aug 23 09:50:38 archlinux kernel: amdgpu 0000:c4:00.0: [drm] *ERROR* [CRTC:79:crtc-0] flip_done timed out
Aug 23 09:50:38 archlinux kernel: [drm:amdgpu_dm_atomic_check [amdgpu]] *ERROR* [CRTC:79:crtc-0] hw_done or flip_done timed out
Aug 23 09:50:43 archlinux kwin_wayland[1261]: kwin_wayland_drm: Pageflip timed out! This is a kernel bug
Aug 23 09:50:48 archlinux kwin_wayland[1261]: kwin_wayland_drm: Pageflip timed out! This is a kernel bug

There's no kernel crash in that journal, ignoring the popular https://gitlab.freedesktop.org/drm/amd/-/issues/2950 and going by the PSR error, try to disable that:

amdgpu.dcdebugmask=0x12

https://wiki.archlinux.org/title/Kernel_parameters

Offline

#6 2024-08-23 16:34:46

frogmech
Member
Registered: 2024-08-23
Posts: 6

Re: Display frozen, computer still working

Downgrading to kernel version 6.9.9 seems to have fixed the issue.

Offline

#7 2024-08-23 19:35:24

seth
Member
Registered: 2012-09-03
Posts: 57,369

Re: Display frozen, computer still working

Ok, but you cannot keep running an old kernel forever.
I'd suggest to install the LTS kernel as (hopefully) working solution and see to find the cause of this - starting by disabling the PSR before oging for a bisection (6.10.0 is already affected?)

Offline

#8 2024-08-23 21:15:15

frogmech
Member
Registered: 2024-08-23
Posts: 6

Re: Display frozen, computer still working

Ok I disabled PSR and updated my kernel back to 6.10.6 and I think it's fixed, I'll have to use the laptop a little longer to be sure though. Is there any downside to disabling PSR? From what I've read it seems like it may reduce battery life?

Offline

#9 2024-08-23 22:11:15

seth
Member
Registered: 2012-09-03
Posts: 57,369

Re: Display frozen, computer still working

The panel self refresh is a power saving feature that prevents the gpu from having to refresh the panel when there's no actual update (static framebuffer)
You could check powertop w/ the feature en- and disabled on the 6.9 kernel to see whether it has major impact (it might not have been enabled for your system on 6.9, got enabled for 6.10 but is unfortunately not working…)

Offline

#10 2024-08-24 07:49:40

an4oud
Member
Registered: 2016-12-17
Posts: 32

Re: Display frozen, computer still working

I have the same issue after upgrade my laptop asus vivobook M6500XV with amd radeon 780m igpu to 6.10.6 kernel version

Offline

#11 2024-08-24 08:22:36

seth
Member
Registered: 2012-09-03
Posts: 57,369

Re: Display frozen, computer still working

6.10.5 was still fine? (should make bisection easy and suggest it's not a feature change)

Offline

#12 2024-08-24 08:48:23

an4oud
Member
Registered: 2016-12-17
Posts: 32

Re: Display frozen, computer still working

I am not sure that 6.10.5 was fine, but for the last week with 6.10.5 kernel there are no any amdgpu errors.
But with 6.10.6 kernel I have got the error twice in one day

Last edited by an4oud (2024-08-24 08:50:44)

Offline

#13 2024-08-24 08:54:09

an4oud
Member
Registered: 2016-12-17
Posts: 32

Re: Display frozen, computer still working

...
Aug 23 13:58:47 cosx kernel: amdgpu 0000:64:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:40 vmid:2 pasid:32793)
Aug 23 13:58:47 cosx kernel: amdgpu 0000:64:00.0: amdgpu:  in process firefox pid 3729 thread firefox:cs0 pid 3830)
Aug 23 13:58:47 cosx kernel: amdgpu 0000:64:00.0: amdgpu:   in page starting at address 0x0000800100ec0000 from client 10
Aug 23 13:58:47 cosx kernel: amdgpu 0000:64:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00241051
Aug 23 13:58:47 cosx kernel: amdgpu 0000:64:00.0: amdgpu:          Faulty UTCL2 client ID: TCP (0x8)
Aug 23 13:58:47 cosx kernel: amdgpu 0000:64:00.0: amdgpu:          MORE_FAULTS: 0x1
Aug 23 13:58:47 cosx kernel: amdgpu 0000:64:00.0: amdgpu:          WALKER_ERROR: 0x0
Aug 23 13:58:47 cosx kernel: amdgpu 0000:64:00.0: amdgpu:          PERMISSION_FAULTS: 0x5
Aug 23 13:58:47 cosx kernel: amdgpu 0000:64:00.0: amdgpu:          MAPPING_ERROR: 0x0
Aug 23 13:58:47 cosx kernel: amdgpu 0000:64:00.0: amdgpu:          RW: 0x1
Aug 23 13:58:47 cosx kernel: amdgpu 0000:64:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:40 vmid:2 pasid:32793)
Aug 23 13:58:47 cosx kernel: amdgpu 0000:64:00.0: amdgpu:  in process firefox pid 3729 thread firefox:cs0 pid 3830)
Aug 23 13:58:47 cosx kernel: amdgpu 0000:64:00.0: amdgpu:   in page starting at address 0x0000800100ec2000 from client 10
Aug 23 13:58:47 cosx kernel: amdgpu 0000:64:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00000000
Aug 23 13:58:47 cosx kernel: amdgpu 0000:64:00.0: amdgpu:          Faulty UTCL2 client ID: CB/DB (0x0)
Aug 23 13:58:47 cosx kernel: amdgpu 0000:64:00.0: amdgpu:          MORE_FAULTS: 0x0
Aug 23 13:58:47 cosx kernel: amdgpu 0000:64:00.0: amdgpu:          WALKER_ERROR: 0x0
Aug 23 13:58:47 cosx kernel: amdgpu 0000:64:00.0: amdgpu:          PERMISSION_FAULTS: 0x0
Aug 23 13:58:47 cosx kernel: amdgpu 0000:64:00.0: amdgpu:          MAPPING_ERROR: 0x0
Aug 23 13:58:47 cosx kernel: amdgpu 0000:64:00.0: amdgpu:          RW: 0x0
Aug 23 13:58:47 cosx kernel: amdgpu 0000:64:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:40 vmid:2 pasid:32793)
Aug 23 13:58:47 cosx kernel: amdgpu 0000:64:00.0: amdgpu:  in process firefox pid 3729 thread firefox:cs0 pid 3830)
Aug 23 13:58:47 cosx kernel: amdgpu 0000:64:00.0: amdgpu:   in page starting at address 0x0000800100ec1000 from client 10
Aug 23 13:58:47 cosx kernel: amdgpu 0000:64:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00000000
Aug 23 13:58:47 cosx kernel: amdgpu 0000:64:00.0: amdgpu:          Faulty UTCL2 client ID: CB/DB (0x0)
Aug 23 13:58:47 cosx kernel: amdgpu 0000:64:00.0: amdgpu:          MORE_FAULTS: 0x0
Aug 23 13:58:47 cosx kernel: amdgpu 0000:64:00.0: amdgpu:          WALKER_ERROR: 0x0
Aug 23 13:58:47 cosx kernel: amdgpu 0000:64:00.0: amdgpu:          PERMISSION_FAULTS: 0x0
Aug 23 13:58:47 cosx kernel: amdgpu 0000:64:00.0: amdgpu:          MAPPING_ERROR: 0x0
Aug 23 13:58:47 cosx kernel: amdgpu 0000:64:00.0: amdgpu:          RW: 0x0
Aug 23 13:58:52 cosx kwin_wayland[1809]: kwin_wayland_drm: Pageflip timed out! This is a kernel bug
Aug 23 13:58:57 cosx kwin_wayland[1809]: kwin_wayland_drm: Pageflip timed out! This is a kernel bug
Aug 23 13:58:57 cosx kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0 timeout, but soft recovered
...
Aug 24 10:19:47 cosx kwin_wayland[1809]: kwin_wayland_drm: Pageflip timed out! This is a kernel bug
Aug 24 10:19:52 cosx kwin_wayland[1809]: kwin_wayland_drm: Pageflip timed out! This is a kernel bug
Aug 24 10:19:53 cosx kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0 timeout, signaled seq=3719902, emitted seq=3719905
Aug 24 10:19:53 cosx kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process Xwayland pid 1896 thread Xwayland:cs0 pid 1897
Aug 24 10:19:55 cosx kernel: amdgpu 0000:64:00.0: amdgpu: MES failed to respond to msg=REMOVE_QUEUE
Aug 24 10:19:55 cosx kernel: [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue
Aug 24 10:19:55 cosx kernel: [drm:gfx_v11_0_hw_fini [amdgpu]] *ERROR* failed to halt cp gfx
Aug 24 10:19:56 cosx systemd-coredump[340550]: [?] Process 2919 (chrome) of user 1000 terminated abnormally without generating a coredump.
Aug 24 10:19:56 cosx systemd-coredump[340549]: [?] Process 1988 (plasmashell) of user 1000 terminated abnormally without generating a coredump
...

Offline

#14 2024-08-24 08:58:22

an4oud
Member
Registered: 2016-12-17
Posts: 32

Re: Display frozen, computer still working

kernel 6.10 is very bad for amdgpu.
Previously on 6.10 there was another problem with video playback on amdgpu
https://lore.kernel.org/linux-kernel/44 … .edu.cn/T/
https://gitlab.freedesktop.org/drm/amd/-/issues/3497

Offline

#15 2024-08-24 15:16:34

seth
Member
Registered: 2012-09-03
Posts: 57,369

Re: Display frozen, computer still working

Does disabling PSR prevent the issue for you as well?
https://bbs.archlinux.org/viewtopic.php … 7#p2191607

Offline

#16 2024-09-03 20:42:06

evea
Member
Registered: 2024-09-03
Posts: 1

Re: Display frozen, computer still working

seth wrote:

Does disabling PSR prevent the issue for you as well?
https://bbs.archlinux.org/viewtopic.php … 7#p2191607

I upgraded to 6.10.7 (which I don't think changed anything related to this bug).  But since adding "amdgpu.dcdebugmask=0x12" I did not have any crashes.

Last edited by evea (2024-09-03 20:42:18)

Offline

#17 2024-09-03 21:53:56

seth
Member
Registered: 2012-09-03
Posts: 57,369

Re: Display frozen, computer still working

Disable PanelSelfRefresh

Offline

#18 2024-09-09 19:19:44

archaeologist
Member
Registered: 2024-09-09
Posts: 25

Re: Display frozen, computer still working

I have the same issue I'm using a ASUS Vivobook S 15 M5506WA and I have the same CPU (AMD Ryzen AI 9 365 w/ Radeon 880M (20) @ 4.31 GHz)

Offline

#19 2024-09-09 19:39:58

seth
Member
Registered: 2012-09-03
Posts: 57,369

Re: Display frozen, computer still working

Ftr, #17 was in response to what disabling PSR does (because I keep tabs up too long)

@archaeologist, if you're facing the same issue, test the same mitigation?

Offline

#20 2024-09-09 20:28:42

archaeologist
Member
Registered: 2024-09-09
Posts: 25

Re: Display frozen, computer still working

Forgot to say but yes I did add "amdgpu.dcdebugmask=0x12" in systemd boot I pressed e and added it to the end then pressed enter and I still face the issue.

Its happened just now since from when I made the last post again also.

Last edited by archaeologist (2024-09-09 20:30:10)

Offline

#21 2024-09-09 21:05:44

archaeologist
Member
Registered: 2024-09-09
Posts: 25

Re: Display frozen, computer still working

21:57 crashed again I'm unsure how to check the logs because I've only been using linux for less than a month

Offline

#22 2024-09-09 21:19:16

seth
Member
Registered: 2012-09-03
Posts: 57,369

Re: Display frozen, computer still working

See the other thread you hijacked, start by avoiding the power button.
Neither of the threads you attached to suggests a kernel halt/panic so there's no need for that - unless you're facing a completely different issue.

Offline

#23 2024-09-12 21:23:59

frogmech
Member
Registered: 2024-08-23
Posts: 6

Re: Display frozen, computer still working

@archaeologist Check out these: https://github.com/BNieuwenhuizen/zenbook-s16 and https://wiki.archlinux.org/title/ASUS_Zenbook_UM5606

They're for a different laptop than yours but I think a lot of the advice will still be applicable to your laptop.

Offline

Board footer

Powered by FluxBB