Created attachment 172647 [details] The same logs as found in "additional information" for download *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY System freezes completely when using normally for web browsing, watching videos, gaming, etc. STEPS TO REPRODUCE 1. Upgrade from fedora 39 to 40 using the guide. 2. Use the pc as normal, seems to trigger most often in graphically intenser environments such as video games or media playback OBSERVED RESULT The system freezes completely. You can't even enter the terminal environments(tty2) or shut down the pc with the case power button. The last +-second of audio hangs and repeats. EXPECTED RESULT The system correctly loads the video, game, etc. SOFTWARE/OS VERSIONS Operating System: Fedora Linux 40 KDE Plasma Version: 6.1.4 KDE Frameworks Version: 6.5.0 Qt Version: 6.7.2 Kernel Version: 6.10.3-200.fc40.x86_64 (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 5800X 8-Core Processor Memory: 47.0 GiB of RAM Graphics Processor: AMD Radeon RX Vega ADDITIONAL INFORMATION Journalctl logs: Please see attachment, too large to paste here.
hmm, in that log the system shuts down many hours after the OpenGL warning, I'm not sure it's related. When the system is in this frozen state, can you still access it through ssh from another device?
(In reply to Zamundaaa from comment #1) > hmm, in that log the system shuts down many hours after the OpenGL warning, > I'm not sure it's related. > > When the system is in this frozen state, can you still access it through ssh > from another device? No clue, but I would guess not seeing as even something like the case power button doesn't function anymore. I can't really test it since I don't have another device to ssh into my pc from
(In reply to Zamundaaa from comment #1) > hmm, in that log the system shuts down many hours after the OpenGL warning, > I'm not sure it's related. > > When the system is in this frozen state, can you still access it through ssh > from another device? I just experienced another crash, I'll upload the crash log to the attachments.
Created attachment 172715 [details] New crash logs, right after crash
🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME. For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging. Thank you for helping us make KDE software even better for everyone!
I have been experience this issues as well on Arch. ``` Operating System: Arch Linux KDE Plasma Version: 6.1.4 KDE Frameworks Version: 6.5.0 Qt Version: 6.7.2 Kernel Version: 6.10.6-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 5800X 8-Core Processor Memory: 62.7 GiB of RAM Graphics Processor: AMD Radeon RX 6750 XT Manufacturer: ASUS ``` I get many many journal entries like this: `kwin_wayland[1234]: kwin_scene_opengl: Invalid framebuffer status: "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"` I don't see any other relevant information. It has been quite intrusive, requiring hard reset to get my pc to respond again. Audio hitches, repeating the last second or so and system becomes completely unresponsive. I am currently also unable to wake my pc from sleep, it will also freeze the moment it goes to sleep. It indeed happens most often during games and watching media.
Please check if you can ssh in while the system is frozen. If you can, does running "kwin_wayland --replace" restore the system to a working state?
(In reply to Zamundaaa from comment #7) > Please check if you can ssh in while the system is frozen. If you can, does > running "kwin_wayland --replace" restore the system to a working state? I can SSH in, "kwin_wayland --replace" does not seem to do anything however, stays frozen. I am also not able to switch tty for that matter. So strange that ssh still works fine. Don't see much of relevancy in journalctl.
Created attachment 173285 [details] Crash log popup right after reboot This crash log may be unrelated but I got a plasma crash handler popup after rebooting my pc.
hmm, it could be that KWin's hanging then. Could you check if that's true with > sudo gdb $(pidof kwin_wayland) and then type in "bt" for the backtrace, and attach that here? If it's just frozen, > killall kwin_wayland -9 should restore the system to a working state. The output of > sudo dmesg might also help figure out what's going on.
Created attachment 173473 [details] dmesg after freeze gdb bt says there is no stack. Killall kind of brings me back to a tty but does not restore my session, switching to tty2 gives me a black screen with working cursor. `sudo reboot` completely froze my system, had to manually hard reset, couldnt switch tty's, connect with ssh and it was stuck with a frozen spinner to reboot. I've attached my dmesg. This is happening semi-regularly during games/media, I'd guess every 2 days or so and also every time my pc falls asleep. My current way to reproduce this issue is to simply let the system go to sleep, so I can reliably reproduce this issue by simply clicking sleep. Has the same properties of repeating audio etc.
I am going to change the status to REPORTED if that's okay. Two people are suffering from the same issue and in my case it is reproducible.
I am also experiencing this issue. I run two Fedora Kinoite machines (one for work and the other for home). Both have experienced these crashes. At work its generally when I'm multitasking with a video playing. At home, it happens when I run modern games, videos, and even on a few old retro games (Total Annihilation Kingdoms from the 90s via wine-ge). The logs show this "kwin_scene_opengl: Invalid framebuffer status: "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"" Both machines are up to date Fedora Kinoite 40, I don't have the work machines exact specs. I know it's running a Haswell processor with an RX480 GPU. The home machines specs are below: Operating System: Fedora Kinoite Linux 40 KDE Plasma Version: 6.1.5 KDE Frameworks Version: 6.6.0 Qt Version: 6.7.2 Kernel Version: 6.10.12-200.fc40.x86_64 (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 3700X 8-Core Processor Memory: 31.2 GiB of RAM Graphics Processor: AMD Radeon RX 7600 Manufacturer: ASUS
I'm having a similar issue, except it is not a "full system freeze", only small continuous freezes (UI and mouse lags a bit) and kwin_wayland peaks at 15 - 20% CPU usage. In the logs I see something like this: Oct 09 12:26:17 lucdesktop kwin_wayland[5496]: kwin_scene_opengl: 0x506: GL_INVALID_FRAMEBUFFER_OPERATION error generated. Operation is not valid because a bound framebuffer is not framebuffer complete. Oct 09 12:26:17 lucdesktop kwin_wayland[5496]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated. Framebuffer name must be generated before being bound. Oct 09 12:26:17 lucdesktop kwin_wayland[5496]: kwin_scene_opengl: Invalid framebuffer status: "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT" Oct 09 12:26:17 lucdesktop kwin_wayland[5496]: kwin_scene_opengl: 0x501: GL_INVALID_VALUE error generated. <levels>, <width> and <height> must be 1 or greater. Oct 09 12:26:17 lucdesktop kwin_wayland[5496]: kf.windowsystem: static bool KX11Extras::mapViewport() may only be used on X11 Operating System: Arch Linux KDE Plasma Version: 6.1.5 KDE Frameworks Version: 6.6.0 Qt Version: 6.7.3 Kernel Version: 6.11.2-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 24 × AMD Ryzen 9 5900X 12-Core Processor Memory: 31.3 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1080/PCIe/SSE2 Packages: * linux 6.11.2.arch1-1 * nvidia-dkms 560.35.03-5 * wayland 1.23.1-1 * kwin 6.1.5-2 * plasma-desktop 6.1.5-1
(In reply to Luc from comment #15) > I'm having a similar issue, except it is not a "full system freeze", only > small continuous freezes (UI and mouse lags a bit) and kwin_wayland peaks at > 15 - 20% CPU usage. Just in case someone experience similar issues, in my case I can confirm now the lagging and high CPU usage was caused by DDC/CI communication issues with my second display.
Today my system got frozen so many times that I could not count. I had the regular application open, Firefox, Chrome and PHPStorm. Whenever I ran step debugging with Xdebug and the execution moved in PHPStorm, the screen got frozen and I had to force shutdown the machine, there was no move from there. Captured the following logs. Case 1 ``` 14:02:21 kwin_wayland: kwin_scene_opengl: Invalid framebuffer status: "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT" 14:02:21 kwin_wayland: kwin_scene_opengl: Invalid framebuffer status: "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT" 14:02:21 kwin_wayland: kwin_scene_opengl: Invalid framebuffer status: "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT" 14:02:21 kwin_wayland: kwin_scene_opengl: Invalid framebuffer status: "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT" 14:02:21 kwin_wayland: kwin_scene_opengl: Invalid framebuffer status: "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT" 14:02:21 kwin_wayland: kwin_scene_opengl: Invalid framebuffer status: "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT" 14:02:21 kwin_wayland: kwin_scene_opengl: Invalid framebuffer status: "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT" 14:02:19 kwin_wayland: kwin_scene_opengl: Invalid framebuffer status: "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT" 14:02:10 kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! 14:02:09 kernel: [drm:gfx_v11_0_cp_gfx_enable.isra.0 [amdgpu]] *ERROR* failed to halt cp gfx 14:02:08 kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process Xwayland pid 2907 thread Xwayland:cs0 pid 2970 ``` Case 2: ``` 14:54:30 kwin_wayland: kwin_wayland_drm: Pageflip timed out! This is a kernel bug 14:53:20 kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! 14:53:19 kernel: [drm:gfx_v11_0_cp_gfx_enable.isra.0 [amdgpu]] *ERROR* failed to halt cp gfx 14:53:18 kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process Xwayland pid 3207 thread Xwayland:cs0 pid 3273 14:13:16 resolvconf: Failed to set DNS configuration: Unit dbus-org.freedesktop.network1.service not found. 14:13:15 bluetoothd: sap-server: Operation not permitted (1) 14:13:15 kernel: amd-pmf AMDI0102:00: ta invoke cmd init failed err: 60005 ```
(In reply to mxr576 from comment #17) > Today my system got frozen so many times that I could not count. I had the > regular application open, Firefox, Chrome and PHPStorm. Whenever I ran step > debugging with Xdebug and the execution moved in PHPStorm, the screen got > frozen and I had to force shutdown the machine, there was no move from there. > Captured the following logs. > > Case 1 > > ``` > 14:02:21 kwin_wayland: kwin_scene_opengl: Invalid framebuffer status: > "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT" > 14:02:21 kwin_wayland: kwin_scene_opengl: Invalid framebuffer status: > "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT" > 14:02:21 kwin_wayland: kwin_scene_opengl: Invalid framebuffer status: > "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT" > 14:02:21 kwin_wayland: kwin_scene_opengl: Invalid framebuffer status: > "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT" > 14:02:21 kwin_wayland: kwin_scene_opengl: Invalid framebuffer status: > "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT" > 14:02:21 kwin_wayland: kwin_scene_opengl: Invalid framebuffer status: > "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT" > 14:02:21 kwin_wayland: kwin_scene_opengl: Invalid framebuffer status: > "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT" > 14:02:19 kwin_wayland: kwin_scene_opengl: Invalid framebuffer status: > "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT" > 14:02:10 kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize > parser -125! > 14:02:09 kernel: [drm:gfx_v11_0_cp_gfx_enable.isra.0 [amdgpu]] *ERROR* > failed to halt cp gfx > 14:02:08 kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process > information: process Xwayland pid 2907 thread Xwayland:cs0 pid 2970 > ``` > > Case 2: > > ``` > 14:54:30 kwin_wayland: kwin_wayland_drm: Pageflip timed out! This is a > kernel bug > 14:53:20 kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize > parser -125! > 14:53:19 kernel: [drm:gfx_v11_0_cp_gfx_enable.isra.0 [amdgpu]] *ERROR* > failed to halt cp gfx > 14:53:18 kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process > information: process Xwayland pid 3207 thread Xwayland:cs0 pid 3273 > 14:13:16 resolvconf: Failed to set DNS configuration: Unit > dbus-org.freedesktop.network1.service not found. > 14:13:15 bluetoothd: sap-server: Operation not permitted (1) > 14:13:15 kernel: amd-pmf AMDI0102:00: ta invoke cmd init failed err: 60005 > > ``` Operating System: KDE neon 12 KDE Plasma Version: 6.2.2 KDE Frameworks Version: 6.7.0 Qt Version: 6.8.0 Kernel Version: 6.8.0-48-generic (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 7840U w/ Radeon 780M Graphics Memory: 60,6 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: HP Product Name: HP EliteBook 865 16 inch G10 Notebook PC
I just wanted to add my laptop and three more at work. I am running CachyOS and I think the other three are EndeavourOS. Besides flooding the logs none of us can REISUB or ssh into our machines. All we can do is hold the power button to shutdown. No problems under X11. This error message floods our logs: Nov 06 21:04:46 NCC1701X kwin_wayland[1113]: kwin_scene_opengl: Invalid framebuffer status: "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT" System: Kernel: 6.11.6-2-cachyos arch: x86_64 bits: 64 compiler: clang v: 18.1.8 clocksource: tsc Desktop: KDE Plasma v: 6.2.3 tk: Qt v: N/A wm: kwin_wayland vt: 2 dm: SDDM Distro: CachyOS base: Arch Linux Machine: Type: Laptop System: Dell product: Inspiron 16 7610 v: N/A serial: <superuser required> Chassis: type: 10 serial: <superuser required> Mobo: Dell model: 1J0MWF v: A00 serial: <superuser required> part-nu: 0A83 uuid: <superuser required> UEFI: Dell v: 1.26.0 date: 08/06/2024 Battery: ID-1: BAT0 charge: 81.4 Wh (100.0%) condition: 81.4/84.3 Wh (96.6%) volts: 12.0 min: 11.4 model: BYD DELL M59JH16 type: Li-poly serial: <filter> status: full CPU: Info: 8-core model: 11th Gen Intel Core i7-11800H bits: 64 type: MT MCP smt: enabled arch: Tiger Lake rev: 1 cache: L1: 640 KiB L2: 10 MiB L3: 24 MiB Speed (MHz): avg: 800 min/max: 800/4600 cores: 1: 800 2: 800 3: 800 4: 800 5: 800 6: 800 7: 800 8: 800 9: 800 10: 800 11: 800 12: 800 13: 800 14: 800 15: 800 16: 800 bogomips: 73728 Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx Graphics: Device-1: Intel TigerLake-H GT1 [UHD Graphics] vendor: Dell driver: i915 v: kernel arch: Gen-12.1 ports: active: eDP-1 empty: DP-1, DP-2, DP-3, DP-4, HDMI-A-1 bus-ID: 00:02.0 chip-ID: 8086:9a60 class-ID: 0300 Device-2: NVIDIA GA107M [GeForce RTX 3050 Mobile] vendor: Dell driver: nvidia v: 565.57.01 arch: Ampere pcie: speed: 16 GT/s lanes: 8 bus-ID: 01:00.0 chip-ID: 10de:25a2 class-ID: 0302 Device-3: Microdia Integrated_Webcam_HD driver: uvcvideo type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 bus-ID: 3-5:2 chip-ID: 0c45:6a10 class-ID: 0e02 Display: wayland server: X.org v: 1.21.1.14 with: Xwayland v: 24.1.4 compositor: kwin_wayland driver: X: loaded: modesetting,nvidia alternate: fbdev,intel,nouveau,nv,vesa dri: iris gpu: i915,nvidia display-ID: 0 Monitor-1: eDP-1 res: 1755x1097 size: N/A modes: N/A API: EGL v: 1.5 hw: drv: intel iris drv: nvidia platforms: device: 0 drv: nvidia device: 2 drv: iris device: 3 drv: swrast gbm: drv: nvidia surfaceless: drv: nvidia wayland: drv: iris x11: drv: iris inactive: device-1 API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: intel mesa v: 24.2.6-cachyos1.3 glx-v: 1.4 direct-render: yes renderer: Mesa Intel UHD Graphics (TGL GT1) device-ID: 8086:9a60 display-ID: :0.0 API: Vulkan v: 1.3.295 layers: 1 surfaces: xcb,xlib,wayland device: 0 type: discrete-gpu driver: nvidia device-ID: 10de:25a2 device: 1 type: integrated-gpu driver: mesa intel device-ID: 8086:9a60 Audio: Device-1: Intel Tiger Lake-H HD Audio vendor: Dell driver: sof-audio-pci-intel-tgl bus-ID: 00:1f.3 chip-ID: 8086:43c8 class-ID: 0401 API: ALSA v: k6.11.6-2-cachyos status: kernel-api Server-1: JACK v: 1.9.22 status: off Server-2: PipeWire v: 1.2.6 status: active with: 1: pipewire-pulse status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin Network: Device-1: Intel Tiger Lake PCH CNVi WiFi driver: iwlwifi v: kernel bus-ID: 00:14.3 chip-ID: 8086:43f0 class-ID: 0280 IF: wlan0 state: up mac: <filter> IF-ID-1: virbr0 state: down mac: <filter> Bluetooth: Device-1: Intel AX201 Bluetooth driver: btusb v: 0.8 type: USB rev: 2.0 speed: 12 Mb/s lanes: 1 bus-ID: 3-14:4 chip-ID: 8087:0026 class-ID: e001 Report: btmgmt ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 5.2 lmp-v: 11 class-ID: 6c010c Drives: Local Storage: total: 4.19 TiB used: 443.3 GiB (10.3%) ID-1: /dev/nvme0n1 vendor: Sabrent model: N/A size: 3.73 TiB speed: 31.6 Gb/s lanes: 4 tech: SSD serial: <filter> fw-rev: RKT343.2 temp: 26.9 C scheme: GPT ID-2: /dev/nvme1n1 vendor: A-Data model: IM2P33F3A NVMe 512GB size: 476.94 GiB speed: 31.6 Gb/s lanes: 4 tech: SSD serial: <filter> fw-rev: 92310271 temp: 30.9 C scheme: GPT Partition: ID-1: / size: 3.73 TiB used: 443.3 GiB (11.6%) fs: btrfs dev: /dev/dm-0 mapped: luks-2f3ddd75-cead-49b3-a4b4-3a73529c2587 ID-2: /boot/efi size: 299.4 MiB used: 744 KiB (0.2%) fs: vfat dev: /dev/nvme0n1p1 ID-3: /home size: 3.73 TiB used: 443.3 GiB (11.6%) fs: btrfs dev: /dev/dm-0 mapped: luks-2f3ddd75-cead-49b3-a4b4-3a73529c2587 ID-4: /var/log size: 3.73 TiB used: 443.3 GiB (11.6%) fs: btrfs dev: /dev/dm-0 mapped: luks-2f3ddd75-cead-49b3-a4b4-3a73529c2587 ID-5: /var/tmp size: 3.73 TiB used: 443.3 GiB (11.6%) fs: btrfs dev: /dev/dm-0 mapped: luks-2f3ddd75-cead-49b3-a4b4-3a73529c2587 Swap: ID-1: swap-1 type: zram size: 62.55 GiB used: 768 KiB (0.0%) priority: 100 dev: /dev/zram0 Sensors: System Temperatures: cpu: 48.0 C mobo: 43.0 C Fan Speeds (rpm): cpu: 0 fan-2: 0 Info: Memory: total: 64 GiB note: est. available: 62.55 GiB used: 8.5 GiB (13.6%) Processes: 359 Power: uptime: 5h 33m states: freeze,mem,disk suspend: s2idle wakeups: 0 hibernate: platform Init: systemd v: 256 default: graphical Packages: pm: pacman pkgs: 1722 Compilers: clang: 18.1.8 gcc: 14.2.1 Shell: sysinfo default: Bash v: 5.2.37 running-in: gnome-terminal inxi: 3.3.36 Wed Nov 6 22:08:13 2024 +-----------------------------------------------------------------------------------------+ | NVIDIA-SMI 565.57.01 Driver Version: 565.57.01 CUDA Version: 12.7 | |-----------------------------------------+------------------------+----------------------+ | GPU Name Persistence-M | Bus-Id Disp.A | Volatile Uncorr. ECC | | Fan Temp Perf Pwr:Usage/Cap | Memory-Usage | GPU-Util Compute M. | | | | MIG M. | |=========================================+========================+======================| | 0 NVIDIA GeForce RTX 3050 ... Off | 00000000:01:00.0 Off | N/A | | N/A 47C P0 15W / 60W | 1MiB / 4096MiB | 0% Default | | | | N/A | +-----------------------------------------+------------------------+----------------------+ +-----------------------------------------------------------------------------------------+ | Processes: | | GPU GI CI PID Type Process name GPU Memory | | ID ID Usage | |=========================================================================================| | No running processes found | +-----------------------------------------------------------------------------------------+
I start to believe that these crashes that I see are related to the monitor setup as well, when I unplug the Dell display, they stop. Nowadays the system keeps working with a degraded UI experice, so restart is needed anyway. 14:15:37 kernel: ---[ end trace 0000000000000000 ]--- 14:15:37 kernel: </TASK> 14:15:37 kernel: Call Trace: 14:15:37 kernel: PKRU: 55555554 14:15:37 kernel: CR2: 00003c7f008fa008 CR3: 000000011f834000 CR4: 0000000000f50ef0 14:15:37 kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 14:15:37 kernel: FS: 0000000000000000(0000) GS:ffff98f1dfe80000(0000) knlGS:0000000000000000 14:15:37 kernel: R13: ffffac2cc16cfa74 R14: ffff98e318a20440 R15: ffff98e321800000 14:15:37 kernel: R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000 14:15:37 kernel: RBP: ffffac2cc16cfa60 R08: 0000000000000000 R09: 0000000000000000 14:15:37 kernel: RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000 14:15:37 kernel: RAX: 0000000000000062 RBX: 00000000000003e9 RCX: 0000000000000000 14:15:37 kernel: RSP: 0018:ffffac2cc16cfa30 EFLAGS: 00010246 14:15:37 kernel: Code: 5d 31 c0 31 d2 31 c9 31 f6 31 ff 45 31 c0 e9 65 80 c7 c1 83 c3 01 41 c7 45 00 ff 00 00 00 81 fb e9 03 00 00 0f 85 79 ff ff ff <0f> 0b eb b8 3d ff 00 00 00 75 b1 eb f3 e8 a1 17 9a c1 90 90 90 90 14:15:37 kernel: RIP: 0010:dmub_psr_get_state+0xbd/0xd0 [amdgpu] 14:15:37 kernel: Workqueue: events_unbound commit_work 14:15:37 kernel: Hardware name: HP HP EliteBook 865 16 inch G10 Notebook PC/8B6E, BIOS V82 Ver. 01.06.02 08/23/2024 14:15:37 kernel: CPU: 5 PID: 508 Comm: kworker/u32:9 Tainted: G O 6.8.0-48-generic #48-Ubuntu 14:15:37 kernel: cdc_ether usbnet mii amdgpu(O) amddrm_ttm_helper(O) amdttm(O) amddrm_buddy(O) amdxcp(O) drm_exec drm_suballoc_helper amd_sched(O) crct10dif_pclmul amdkcl(O) crc32_pclmul hid_multitouch drm_display_helper polyval_clmulni hid_generic cec polyval_generic nvme ghash_clmulni_intel ucsi_acpi rc_core i2c_hid_acpi sha256_ssse3 nvme_core xhci_pci typec_ucsi video amd_sfh i2c_hid sha1_ssse3 thunderbolt i2c_algo_bit xhci_pci_renesas nvme_auth typec wmi hid aesni_intel crypto_simd cryptd 14:15:37 kernel: Modules linked in: xt_nat veth ccm nft_chain_nat xt_MASQUERADE nf_nat bridge stp llc nf_conntrack_netlink xfrm_user xfrm_algo rfcomm snd_seq_dummy snd_hrtimer vboxnetadp(O) vboxnetflt(O) vboxdrv(O) overlay snd_ctl_led ledtrig_audio cmac algif_hash algif_skcipher af_alg ip6t_REJECT qrtr nf_reject_ipv6 xt_hl ip6t_rt ipt_REJECT bnep nf_reject_ipv4 xt_LOG nf_log_syslog nft_limit xt_limit xt_addrtype xt_tcpudp xt_conntrack nf_conntrack intel_rapl_msr nf_defrag_ipv6 intel_rapl_common nf_defrag_ipv4 nft_compat nf_tables edac_mce_amd binfmt_misc libcrc32c kvm_amd nls_iso8859_1 kvm irqbypass 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_hda_codec_realtek snd_sof snd_hda_codec_generic snd_hda_codec_hdmi snd_sof_utils snd_hda_scodec_cs35l41_spi snd_soc_core snd_compress ac97_bus snd_hda_intel snd_pcm_dmaengine snd_intel_dspcfg snd_intel_sdw_acpi snd_pci_ps rtw89_8852ce snd_hda_codec snd_rpl_pci_acp6x btusb uvcvideo rtw89_8852c 14:15:37 kernel: WARNING: CPU: 5 PID: 508 at /tmp/amd.KNjRGRxt/amd/amdgpu/../display/dc/dce/dmub_psr.c:124 dmub_psr_get_state+0xbd/0xd0 [amdgpu] 14:15:37 kernel: ------------[ cut here ]------------ 14:14:53 kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 14:13:30 kernel: lockdown_is_locked_down: 5 callbacks suppressed 14:12:43 kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! 14:12:43 kernel: amdgpu 0000:c3:00.0: amdgpu: GPU reset(2) succeeded! 14:12:42 kernel: [drm] DMUB hardware initialized: version=0x08003D00 14:12:42 kernel: amdgpu 0000:c3:00.0: amdgpu: SMU is resumed successfully! 14:12:42 kernel: [drm] PCIE GART of 512M enabled (table at 0x000000807FD00000). 14:12:42 kernel: amdgpu 0000:c3:00.0: amdgpu: GPU reset succeeded, trying to resume 14:12:42 kernel: [drm:gfx_v11_0_cp_gfx_enable.isra.0 [amdgpu]] *ERROR* failed to halt cp gfx 14:12:42 kernel: [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue 14:12:42 kernel: amdgpu 0000:c3:00.0: amdgpu: MES failed to respond to msg=REMOVE_QUEUE 14:12:37 kernel: amdgpu 0000:c3:00.0: amdgpu: GPU reset begin! 14:12:37 kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process Xwayland pid 2926 thread Xwayland:cs0 pid 2991 14:12:37 kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process Xwayland pid 2926 thread Xwayland:cs0 pid 2991 14:12:37 kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0 timeout, signaled seq=207447, emitted seq=207449 https://i.imgur.com/ue9FvDA.png
Created attachment 176309 [details] `journalctl -b` ouput after freeze, plus info after unfreezing I think I've also been experiencing this same issue. As mxr576 mentions above, this does seem to also be related to monitor setup changes. In my case, I'm connecting my Wacom graphics tablet to my desktop to draw with, but occasionally I'll run into bug 493027 after periods of inactivity. While the workaround that was merged avoids the segfault for that issue, I still have to reconnect my tablet in order to restore proper input functionality for it. This was working fine on a Garuda Linux install, but recently I migrated my system to a new Arch Linux setup instead. Since then, reconnecting my tablet to try and restore input instead causes this full graphics freeze. Interestingly, it appears that the system is able to recover and unfreeze after an some amount of time if the graphics tablet is disconnected again (sometimes it does so quickly, sometimes it takes a minute or so). However, I just now found that if I first connect the tablet for input only (USB), and then after for display (HDMI), then this can avoid the freeze and allow it to reconnect normally again, however this still causes other apps such as Dolphin file explorer, kwallet, Telegram, and so on to crash. Obviously this is not so helpful of a workaround for most users, but it feels worth noting. Additionally, I have had this issue occur on Arch regardless of using `linux` or `linux-zen` kernels, and `nvidia` or `nvidia-dkms` respectively. Still trying to troubleshoot things to see if there's any more information that can be gained, as I'm especially curious why I haven't seen this happen under my Garuda install, but does under Arch (unless there was some update to kwin within the last week or so that potentially introduced the bug that I just wasn't aware of due to migrating). I moved my system over just a couple days ago, but still have the previous one setup on a separate SSD, so I could try testing things further and see if that produces anything noteworthy in the journal for comparison. Also possibly related: bug 486460 However in my case HDR is disabled, and I'm not encountering any black screens. In the meantime, I've added my journal of the issue occurring on Arch to the attachments as well. Journal summary: - The wall of "GL_FRAMEBUFFER" errors occurs from line 6088 to 17024, at which point the system recovered from the freeze. - Then again in troubleshooting once more, another wall of errors from 17875 to 28773, where it recovers again. - After that point, I then attempt the workaround of connecting the tablet as input first, then display, which causes the multiple application crashes that are caught by the system. - The end state is graphics remaining unfrozen and system functioning normally (as far as I can tell). I can also provide coredumps from the affected applications if that would help at all, though I feel those are mainly side effects of the actual issue. --- Operating System: Arch Linux KDE Plasma Version: 6.2.4 KDE Frameworks Version: 6.8.0 Qt Version: 6.8.0 Kernel Version: 6.12.1-zen1-1-zen (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 2600X Six-Core Processor Memory: 15.5 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1070 Ti/PCIe/SSE2
Could anyone confirm if setting your computer to sleep causes a freeze? I currently have worked around the issue by disabling anything that would cause my PC to go into sleep mode. This issue now also doesn't seem to occur anymore. However, if I manually set my PC to sleep it will immediately freeze. This might be a completely unrelated issue however. Since monitors have been brought up, I do have a monitor with HDR (disabled) and gsync. I'll check later tonight if unplugging this monitor makes any difference.
(In reply to Peter Leconte from comment #22) > Could anyone confirm if setting your computer to sleep causes a freeze? > I currently have worked around the issue by disabling anything that would > cause my PC to go into sleep mode. > This issue now also doesn't seem to occur anymore. > However, if I manually set my PC to sleep it will immediately freeze. This > might be a completely unrelated issue however. Testing sleep mode on my end, I haven't been able to reproduce the freeze with it. In my case, when the system is put to sleep manually with a single monitor, it does so without issue, and resumes normally without freezing. When the second monitor (graphics tablet) is connected, putting to PC to sleep appears to work fine, but then on resume the second monitor does not receive input signal and is not detected by the system. I suspect this is more to with with how the tablet is connected though, as I have to use the Wacom Link adaptor for it that splits and converts the combined output signal from a USB-C port into HDMI and microUSB instead. Unfortunately I dont have any means of connecting it directly from USB-C to USB-C as none of our machines support such connections, though that is probably irrelevant given how niche such a setup would be in regards to troubleshooting this bug. I have also tried only connecting it with HDMI to have it treated as just a second display without input, however this results in the same freezing unless input is connected separately first, interestingly enough. Again, not as useful for those affected with standard monitors. As for sleep settings, I have setup the following setup manually: - Using `nvidia-dkms` - Enabled `nvidia-suspend.service`, `nvidia-hibernate.service`, and `nvidia-resume.service` explicitly via `systemctl` - Created `/etc/modprobe.d/nvidia-suspend-fix.conf` with settings - `options nvidia NVreg_PreserveVideoMemoryAllocations=1` Previously I avoided sleep mode entirely because it would often lead to issues with my Nvidia card, however after looking up things on the ArchWiki, it appears setting that kernel module option to preserve video memory now allows it to work normally (at least, ignoring the problem with the tablet display not resuming, but again I suspect that to be a more unique issue with how its physically connected). Notably though we're both on different GPUs, as your previous comment mentions running on AMD in the specs. Would be interested in knowing if the freeze is caused by sleep mode specifically on one or another, though in either case I feel like that is probably a different issue that's just resulting int he same graphics failure. If you wait a while while the screen is frozen (1-2 minutes), and then try to move the mouse around, does the screen unfreeze for you at all? I'm able to consistently recover from the freeze in my cases now by simply waiting, though as mentioned the amount of time to wait is inconsistent. Finally, a few other things I've tried, but to no avail: - Changing to 200% scaling instead of previously 175% fractional scaling in system settings - Downgrading to `kwin 6.2.3` Given 6.2.3 did not make any difference though and that package release was roughly 3 weeks back, I don't imagine downgrading further will make a difference, especially given others have been having this issue for much longer. Will perhaps see about getting a journal from my Garuda install later today though to see if anything is different in how its handling the extra monitor being reconnected, or if suddenly the issue is reproducible there.
Created attachment 176332 [details] kwin 6.2.2, recover from freeze on reconnecting secondary monitor Okay, after some more testing, downgrading to `kwin 6.2.2` does lead to better results, at least in my case. Attached the journal output, but at a glance I dont see any noticeably different messages from what was seen in the output produced on versions 6.2.3 and 6.2.4, however the main difference was that the system was able to recover quickly and unfreeze. After downgrading, I'm able to disconnect and reconnect my graphics tablet display at will, and the system does not freeze indefinitely as observed on the more recent kwin versions. The freeze does still happen briefly, and the journal is still flooded with the "GL_FRAMEBUFFER" errors, however by comparison this only lasts a few seconds, and then the displays reset and graphics unfreeze, allowing for the system to be used normally again. This still results in many applications crashing (kded6, kwallet, kde power management system, etc.), so still not a complete workaround exactly. Would be interested if this is a temporary workaround in some cases though, for those of us that have been experiencing the issue on Plasma 6.2. As the issue does still date back to 6.1 versions though, I wouldn't be surprised if this is just a lucky coincidence with my setup. Additionally I tested my Garuda setup as well but that also resulted in the same graphics freezes, and it was not able to recover after just waiting. The journal was effectively identical to the ones on Arch w/ kwin >=6.2.3. Did not also test with downgrading kwin on Garuda, however the results for running it with kwin 6.2.2 are already known to be identical to the test done on Arch just now. I dont know if there's much more I can contribute at this time, but for anyone else that looks into this further, please let me know if there's any other ways I can assist!
I can 100% replicate it if I plug 3 monitors in all 3 of my DP, if I have 2 DP and 1 HDMI is fine, but as soon as the 3rd DP is also connected it freezes and the log is indeed showing "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT". Note: This does not happen under X11. Operating System: CachyOS Linux KDE Plasma Version: 6.2.4 KDE Frameworks Version: 6.9.0 Qt Version: 6.8.1 Kernel Version: 6.12.5-1-cachyos-bmq (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 5800X3D 8-Core Processor Memory: 31,2 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 3090/PCIe/SSE2
I also experience this issue on KDE neon on an HP Elitebook (4k display) and a Dell monitor (also 4k) connected on HDMI. Operating System: KDE neon 6.2 KDE Plasma Version: 6.3.0 KDE Frameworks Version: 6.10.0 Qt Version: 6.8.2 Kernel Version: 6.11.0-17-generic (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 7840U w/ Radeon 780M Graphics Memory: 60.6 GiB of RAM Graphics Processor: AMD Radeon 780M
Was reminded to respond to this from the other comment just now. This is no longer an issue on my machine as of KDE Plasma 6.3 and kwin 6.3. In my case where this error would get thrown before and things would freeze, my tablet now connects normally and without any significant delay in input or graphics errors like this. If others are still experiencing the problem though, then I was probably observing something different, so I likely won't be able to contribute much more information to the issue now. Can still check my journalctl if the errors still are occurring, even if things aren't freezing, but I think it was just related to a different issue that the fixes/improvements to drawing tablets resolved in 6.3 Hopefully this can be tracked down soon though and fixed for other multi monitor setups! Again, can test things and provide what info I'm able to as requested.
I am also having this issue, complete freeze, can't switch to terminal, etc. Have to hard shut off. It is seemingly random, as sometimes I can work for hours before a crash, other times it happens 30 minutes after boot. I can't find any pattern in activity when the crash occurs. The last time I was doing the same thing I did all day, which was work over an RDP connection. The logs don't appear to give any clues except for this message mentioned previously: kwin_wayland[2272]: kwin_scene_opengl: Invalid framebuffer status: "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT" I am running 4 monitors, and few others mentioned using multiple monitors too, so there may be something to that. -------- From Info Center -------- Operating System: Fedora Linux 41 Kinoite KDE Plasma Version: 6.3.2 KDE Frameworks Version: 6.11.0 Qt Version: 6.8.2 Kernel Version: 6.13.5-200.fc41.x86_64 (64-bit) Graphics Platform: Wayland Processors: 24 × AMD Ryzen 9 9900X 12-Core Processor Memory: 62.4 GiB of RAM Graphics Processor 1: AMD Radeon Pro WX 7100 Graphics Graphics Processor 2: NV172 Manufacturer: Gigabyte Technology Co., Ltd. Product Name: X870 AORUS ELITE WIFI7 ICE System Version: -CF-WCP -------- ------------------------- -------- Monitors 1x Dell S2421HGF 2x Dell P2414H 1x Dell P2312 The S2421 I am running at 144hz. It does have features such as "AMD FreeSync Premium" All four monitors are connected via display port to the WX 7100 graphics card. I do have a NVIDIA 3080 RTX in-slot but it is unused (for pass-through / QEMU, but I am not running any VMs lately, and not during any of the freezes). I recently went to 3 monitors after reading through this thread, suspecting that it may be related to an adapter I was using for one of them, but I just had the freeze again. May try ditching the 144hz, or that monitor all together to see if that changes anything. Anyway, I hope this helps. I will continue to investigate and report back if I find a fix.
I still regularly get freezes :) I am not entirely certain it happens with multiple monitors as I've used a singular one as well (although freesync). I noticed it tends to happen when alt-tabbing with full screen games.