Created attachment 152855 [details] Error messages as seen in the journald journal SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Run KDE Plasma with Wayland 2. Suspend the machine 3. Wake machine up by pressing power button OBSERVED RESULT The screens stay black and the journal gets filled with uncountable error messages from KWin, picture attached EXPECTED RESULT KDE Plasma starts normally SOFTWARE/OS VERSIONS KDE Plasma Version: 5.26.0 KDE Frameworks Version: 5.99.0 Qt Version: 5.15.6 ADDITIONAL INFORMATION
Is this a regression compared to Plasma 5.25? Or were you seeing it there too?
(In reply to Nate Graham from comment #1) > Is this a regression compared to Plasma 5.25? Or were you seeing it there > too? It is a regression, suspend wake-up worked fine in Plasma 5.25
This bug doesn't happen on my work laptop, I figure my main laptop's Plasma installation is just bugged out for some reason. This bug can be closed, I'll reopen it if the bug occurs again. It might be caused by the AMD GPU in my main PC (my laptop uses an intel iGPU), but I'm unsure about that.
I confirm that the bug also happens in my machine. It seems to be something related to xwayland - if I kill it through htop, the screen appears. Running xorg, it works just fine. Operating System: EndeavourOS KDE Plasma Version: 5.26.1 KDE Frameworks Version: 5.99.0 Qt Version: 5.15.6 Kernel Version: 6.0.2-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 36 × Intel® Xeon® CPU E5-2696 v3 @ 2.30GHz Memory: 31.2 GiB of RAM Graphics Processor: AMD Radeon RX 550 / 550 Series Manufacturer: HUANANZHI
(In reply to Pedro Barreto from comment #4) > I confirm that the bug also happens in my machine. It seems to be something > related to xwayland - if I kill it through htop, the screen appears. > > Running xorg, it works just fine. > > Operating System: EndeavourOS > KDE Plasma Version: 5.26.1 > KDE Frameworks Version: 5.99.0 > Qt Version: 5.15.6 > Kernel Version: 6.0.2-arch1-1 (64-bit) > Graphics Platform: Wayland > Processors: 36 × Intel® Xeon® CPU E5-2696 v3 @ 2.30GHz > Memory: 31.2 GiB of RAM > Graphics Processor: AMD Radeon RX 550 / 550 Series > Manufacturer: HUANANZHI Then it's an AMD issue (I guess), as this doesn't affect my intel GPU machine at all. You can also reactivate KWin by just switching from the open session to a TTY like tty4 and then switch back to tty1 (or was it tty2?)
No. If I change for a console tty, the screen appears, but if I go back to wayland's tty, the monitor turns off.
(In reply to Pedro Barreto from comment #6) > No. If I change for a console tty, the screen appears, but if I go back to > wayland's tty, the monitor turns off. That's weird, that workaround works for me. Let's hope it gets fixed soon.
Here's my system information: Operating System: Arch Linux KDE Plasma Version: 5.26.0 KDE Frameworks Version: 5.99.0 Qt Version: 5.15.6 Kernel Version: 6.0.1-arch2-1 (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 5600X 6-Core Processor Memory: 31.3 GiB of RAM Graphics Processor: AMD Radeon RX 6600 XT Manufacturer: Micro-Star International Co., Ltd. Product Name: MS-7C56 System Version: 1.0
Can you upload the output of "sudo dmesg" when this happens?
(In reply to Zamundaaa from comment #9) > Can you upload the output of "sudo dmesg" when this happens? I am sorry. That's not happenning when I use RX 550. Only I use my other GPU, RX 6600: See my dmesg: [ 23.608159] ACPI: PM: Preparing to enter system sleep state S3 [ 23.608846] ACPI: PM: Saving platform NVS memory [ 23.609089] Disabling non-boot CPUs ... [ 23.612927] smpboot: CPU 1 is now offline [ 23.620052] smpboot: CPU 2 is now offline [ 23.626287] smpboot: CPU 3 is now offline [ 23.632385] smpboot: CPU 4 is now offline [ 23.636084] smpboot: CPU 5 is now offline [ 23.642071] smpboot: CPU 6 is now offline [ 23.647632] smpboot: CPU 7 is now offline [ 23.652963] smpboot: CPU 8 is now offline [ 23.657963] smpboot: CPU 9 is now offline [ 23.662951] smpboot: CPU 10 is now offline [ 23.667754] smpboot: CPU 11 is now offline [ 23.672674] smpboot: CPU 12 is now offline [ 23.677340] smpboot: CPU 13 is now offline [ 23.681895] smpboot: CPU 14 is now offline [ 23.686147] smpboot: CPU 15 is now offline [ 23.690468] smpboot: CPU 16 is now offline [ 23.693846] smpboot: CPU 17 is now offline [ 23.701119] smpboot: CPU 18 is now offline [ 23.703405] smpboot: CPU 19 is now offline [ 23.705357] smpboot: CPU 20 is now offline [ 23.707510] smpboot: CPU 21 is now offline [ 23.710086] smpboot: CPU 22 is now offline [ 23.712262] smpboot: CPU 23 is now offline [ 23.714252] smpboot: CPU 24 is now offline [ 23.716249] smpboot: CPU 25 is now offline [ 23.718173] smpboot: CPU 26 is now offline [ 23.720092] smpboot: CPU 27 is now offline [ 23.721927] smpboot: CPU 28 is now offline [ 23.723730] smpboot: CPU 29 is now offline [ 23.725541] smpboot: CPU 30 is now offline [ 23.727295] smpboot: CPU 31 is now offline [ 23.729121] smpboot: CPU 32 is now offline [ 23.730867] smpboot: CPU 33 is now offline [ 23.732635] smpboot: CPU 34 is now offline [ 23.734314] smpboot: CPU 35 is now offline [ 23.743948] ACPI: PM: Low-level resume complete [ 23.743968] ACPI: PM: Restoring platform NVS memory [ 23.744544] Enabling non-boot CPUs ... [ 23.745975] x86: Booting SMP configuration: [ 23.745976] smpboot: Booting Node 0 Processor 1 APIC 0x2 [ 23.753105] CPU1 is up [ 23.753157] smpboot: Booting Node 0 Processor 2 APIC 0x4 [ 23.759615] CPU2 is up [ 23.759838] smpboot: Booting Node 0 Processor 3 APIC 0x6 [ 23.766436] CPU3 is up [ 23.766487] smpboot: Booting Node 0 Processor 4 APIC 0x8 [ 23.772926] CPU4 is up [ 23.772972] smpboot: Booting Node 0 Processor 5 APIC 0x10 [ 23.779879] CPU5 is up [ 23.779928] smpboot: Booting Node 0 Processor 6 APIC 0x12 [ 23.786588] CPU6 is up [ 23.786632] smpboot: Booting Node 0 Processor 7 APIC 0x14 [ 23.793323] CPU7 is up [ 23.793373] smpboot: Booting Node 0 Processor 8 APIC 0x16 [ 23.799714] CPU8 is up [ 23.799757] smpboot: Booting Node 0 Processor 9 APIC 0x20 [ 23.806100] CPU9 is up [ 23.806142] smpboot: Booting Node 0 Processor 10 APIC 0x22 [ 23.812650] CPU10 is up [ 23.812695] smpboot: Booting Node 0 Processor 11 APIC 0x24 [ 23.819244] CPU11 is up [ 23.819286] smpboot: Booting Node 0 Processor 12 APIC 0x26 [ 23.826102] CPU12 is up [ 23.826156] smpboot: Booting Node 0 Processor 13 APIC 0x28 [ 23.832800] CPU13 is up [ 23.832847] smpboot: Booting Node 0 Processor 14 APIC 0x30 [ 23.839301] CPU14 is up [ 23.839342] smpboot: Booting Node 0 Processor 15 APIC 0x32 [ 23.846198] CPU15 is up [ 23.846241] smpboot: Booting Node 0 Processor 16 APIC 0x34 [ 23.853074] CPU16 is up [ 23.853116] smpboot: Booting Node 0 Processor 17 APIC 0x36 [ 23.860026] CPU17 is up [ 23.860076] smpboot: Booting Node 0 Processor 18 APIC 0x1 [ 23.863372] CPU18 is up [ 23.863426] smpboot: Booting Node 0 Processor 19 APIC 0x3 [ 23.866584] CPU19 is up [ 23.866628] smpboot: Booting Node 0 Processor 20 APIC 0x5 [ 23.869721] CPU20 is up [ 23.869763] smpboot: Booting Node 0 Processor 21 APIC 0x7 [ 23.872990] CPU21 is up [ 23.873036] smpboot: Booting Node 0 Processor 22 APIC 0x9 [ 23.876441] CPU22 is up [ 23.876492] smpboot: Booting Node 0 Processor 23 APIC 0x11 [ 23.879986] CPU23 is up [ 23.880027] smpboot: Booting Node 0 Processor 24 APIC 0x13 [ 23.883581] CPU24 is up [ 23.883622] smpboot: Booting Node 0 Processor 25 APIC 0x15 [ 23.887206] CPU25 is up [ 23.887255] smpboot: Booting Node 0 Processor 26 APIC 0x17 [ 23.891057] CPU26 is up [ 23.891107] smpboot: Booting Node 0 Processor 27 APIC 0x21 [ 23.894830] CPU27 is up [ 23.894874] smpboot: Booting Node 0 Processor 28 APIC 0x23 [ 23.898672] CPU28 is up [ 23.898714] smpboot: Booting Node 0 Processor 29 APIC 0x25 [ 23.902736] CPU29 is up [ 23.902783] smpboot: Booting Node 0 Processor 30 APIC 0x27 [ 23.907071] CPU30 is up [ 23.907119] smpboot: Booting Node 0 Processor 31 APIC 0x29 [ 23.911382] CPU31 is up [ 23.911422] smpboot: Booting Node 0 Processor 32 APIC 0x31 [ 23.915580] CPU32 is up [ 23.915620] smpboot: Booting Node 0 Processor 33 APIC 0x33 [ 23.920007] CPU33 is up [ 23.920049] smpboot: Booting Node 0 Processor 34 APIC 0x35 [ 23.924748] CPU34 is up [ 23.924800] smpboot: Booting Node 0 Processor 35 APIC 0x37 [ 23.929386] CPU35 is up [ 23.943700] ACPI: PM: Waking up from system sleep state S3 [ 23.945976] pcieport 0000:00:1c.0: Enabling MPC IRBNCE [ 23.945977] pcieport 0000:00:1c.2: Enabling MPC IRBNCE [ 23.945982] pcieport 0000:00:1c.1: Enabling MPC IRBNCE [ 23.945983] pcieport 0000:00:1c.0: Intel PCH root port ACS workaround enabled [ 23.945986] pcieport 0000:00:1c.4: Enabling MPC IRBNCE [ 23.945988] pcieport 0000:00:1c.2: Intel PCH root port ACS workaround enabled [ 23.945991] pcieport 0000:00:1c.1: Intel PCH root port ACS workaround enabled [ 23.945998] pcieport 0000:00:1c.4: Intel PCH root port ACS workaround enabled [ 23.947335] pci 0000:00:05.0: disabled boot interrupts on device [8086:2f28] [ 23.947400] pcieport 0000:00:1c.0: pciehp: Slot(0-1): Card present [ 23.947550] usb usb1: root hub lost power or was reset [ 23.947550] [drm] PCIE GART of 512M enabled (table at 0x00000081FEB00000). [ 23.947591] [drm] PSP is resuming... [ 23.947596] xhci_hcd 0000:00:14.0: xHC error in resume, USBSTS 0x411, Reinit [ 23.947600] usb usb3: root hub lost power or was reset [ 23.947602] usb usb4: root hub lost power or was reset [ 23.947639] usb usb2: root hub lost power or was reset [ 23.947689] xhci_hcd 0000:08:00.0: xHC error in resume, USBSTS 0x411, Reinit [ 23.947692] usb usb5: root hub lost power or was reset [ 23.947694] usb usb6: root hub lost power or was reset [ 23.948286] serial 00:05: activated [ 23.956998] nvme nvme0: 15/0/0 default/read/poll queues [ 23.974091] nvme nvme1: 8/0/0 default/read/poll queues [ 23.978971] nvme nvme1: Ignoring bogus Namespace Identifiers [ 24.031766] [drm] reserve 0xa00000 from 0x8001000000 for PSP TMR [ 24.128543] amdgpu 0000:05:00.0: amdgpu: RAS: optional ras ta ucode is not available [ 24.146593] amdgpu 0000:05:00.0: amdgpu: SECUREDISPLAY: securedisplay ta ucode is not available [ 24.146597] amdgpu 0000:05:00.0: amdgpu: SMU is resuming... [ 24.146600] amdgpu 0000:05:00.0: amdgpu: smu driver if version = 0x0000000f, smu fw if version = 0x00000013, smu fw program = 0, version = 0x003b2900 (59.41.0) [ 24.146604] amdgpu 0000:05:00.0: amdgpu: SMU driver if version not matched [ 24.146647] amdgpu 0000:05:00.0: amdgpu: use vbios provided pptable [ 24.197902] amdgpu 0000:05:00.0: amdgpu: SMU is resumed successfully! [ 24.199324] [drm] DMUB hardware initialized: version=0x02020013 [ 24.234622] usb 2-1: reset high-speed USB device number 2 using ehci-pci [ 24.234635] usb 1-1: reset high-speed USB device number 2 using ehci-pci [ 24.263397] amdgpu: Move buffer fallback to memcpy unavailable [ 24.263401] amdgpu 0000:05:00.0: amdgpu: 00000000af86c199 pin failed [ 24.263406] [drm:dm_plane_helper_prepare_fb [amdgpu]] *ERROR* Failed to pin framebuffer with error -19 [ 24.265059] [drm] kiq ring mec 2 pipe 1 q 0 [ 24.269205] [drm] VCN decode and encode initialized successfully(under DPG Mode). [ 24.269564] [drm] JPEG decode initialized successfully. [ 24.269580] amdgpu 0000:05:00.0: amdgpu: ring gfx_0.0.0 uses VM inv eng 0 on hub 0 [ 24.269583] amdgpu 0000:05:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0 [ 24.269584] amdgpu 0000:05:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0 [ 24.269586] amdgpu 0000:05:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 5 on hub 0 [ 24.269587] amdgpu 0000:05:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 6 on hub 0 [ 24.269588] amdgpu 0000:05:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 7 on hub 0 [ 24.269589] amdgpu 0000:05:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 8 on hub 0 [ 24.269590] amdgpu 0000:05:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 9 on hub 0 [ 24.269591] amdgpu 0000:05:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 10 on hub 0 [ 24.269593] amdgpu 0000:05:00.0: amdgpu: ring kiq_2.1.0 uses VM inv eng 11 on hub 0 [ 24.269594] amdgpu 0000:05:00.0: amdgpu: ring sdma0 uses VM inv eng 12 on hub 0 [ 24.269595] amdgpu 0000:05:00.0: amdgpu: ring sdma1 uses VM inv eng 13 on hub 0 [ 24.269597] amdgpu 0000:05:00.0: amdgpu: ring vcn_dec_0 uses VM inv eng 0 on hub 1 [ 24.269598] amdgpu 0000:05:00.0: amdgpu: ring vcn_enc_0.0 uses VM inv eng 1 on hub 1 [ 24.269599] amdgpu 0000:05:00.0: amdgpu: ring vcn_enc_0.1 uses VM inv eng 4 on hub 1 [ 24.269600] amdgpu 0000:05:00.0: amdgpu: ring jpeg_dec uses VM inv eng 5 on hub 1
It seems to be AMDGPU bug for RX 6600 6600m 6600 XT cards: https://gitlab.freedesktop.org/drm/amd/-/issues/2164
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!