| Summary: | Setting refresh rate to 240 Hz from 60 Hz appears to break turning monitor on after inactivity timeout | ||
|---|---|---|---|
| Product: | [Plasma] kwin | Reporter: | Paul <paul.e.hill2> |
| Component: | general | Assignee: | KWin default assignee <kwin-bugs-null> |
| Status: | NEEDSINFO WAITINGFORINFO | ||
| Severity: | normal | CC: | aleixpol, plasma-bugs, ppirazzi4, xaver.hugl |
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Fedora RPMs | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: |
drm_info while issue is present.
dmesg drm debug log 30 Sep 2025 |
||
|
Description
Paul
2025-09-21 23:28:33 UTC
Please attach the output of drm_info while the screen doesn't turn on. You can get it through ssh Created attachment 185152 [details] drm_info while issue is present. In case it helps, here's a diff against the output after the screen is back on: $ diff drm_info_2025-09-22_non-working.txt drm_info_2025-09-22_working.txt 82c82 < │ │ ├───"EDID" (immutable): blob = 155 --- > │ │ ├───"EDID" (immutable): blob = 152 87c87 < │ │ ├───"CRTC_ID" (atomic): object CRTC = 0 --- > │ │ ├───"CRTC_ID" (atomic): object CRTC = 62 89c89 < │ │ ├───"HDR_OUTPUT_METADATA": blob = 153 --- > │ │ ├───"HDR_OUTPUT_METADATA": blob = 146 171a172 > │ │ │ ├───Mode: 5120×1440@239.76 phsync nvsync 174,175c175,177 < │ │ ├───"ACTIVE" (atomic): range [0, 1] = 0 < │ │ ├───"MODE_ID" (atomic): blob = 0 --- > │ │ ├───"ACTIVE" (atomic): range [0, 1] = 1 > │ │ ├───"MODE_ID" (atomic): blob = 151 > │ │ │ └───5120×1440@239.76 phsync nvsync 246c248,254 < │ │ ├───FB ID: 0 --- > │ │ ├───FB ID: 149 > │ │ │ ├───Object ID: 149 > │ │ │ ├───Size: 5120×1440 > │ │ │ ├───Format: ABGR2101010 (0x30334241) > │ │ │ ├───Modifier: NVIDIA_BLOCK_LINEAR_2D(h=4, k=6, g=2, s=1, c=0) (0x0300000000606014) > │ │ │ └───Planes: > │ │ │ └───Plane 0: offset = 0, pitch = 20480 bytes 272c280,286 < │ ├───"FB_ID" (atomic): object framebuffer = 0 --- > │ ├───"FB_ID" (atomic): object framebuffer = 149 > │ │ ├───Object ID: 149 > │ │ ├───Size: 5120×1440 > │ │ ├───Format: ABGR2101010 (0x30334241) > │ │ ├───Modifier: NVIDIA_BLOCK_LINEAR_2D(h=4, k=6, g=2, s=1, c=0) (0x0300000000606014) > │ │ └───Planes: > │ │ └───Plane 0: offset = 0, pitch = 20480 bytes 274c288 < │ ├───"CRTC_ID" (atomic): object CRTC = 0 --- > │ ├───"CRTC_ID" (atomic): object CRTC = 62 472,473c486,487 < │ ├───"CRTC_X" (atomic): srange [INT32_MIN, INT32_MAX] = 571 < │ ├───"CRTC_Y" (atomic): srange [INT32_MIN, INT32_MAX] = 856 --- > │ ├───"CRTC_X" (atomic): srange [INT32_MIN, INT32_MAX] = 1993 > │ ├───"CRTC_Y" (atomic): srange [INT32_MIN, INT32_MAX] = 627 Okay, I think we'll need a drm debug log of KWin trying to turn the display on. https://invent.kde.org/plasma/kwin/-/wikis/Debugging/Debugging-DRM-issues explains how to do that; ideally you should enable the logging through ssh and then trigger KWin to enable the display by moving the mouse or pressing some key, and then stop the logging again. Created attachment 185405 [details]
dmesg drm debug log 30 Sep 2025
(In reply to Zamundaaa from comment #3) > Okay, I think we'll need a drm debug log of KWin trying to turn the display > on. > https://invent.kde.org/plasma/kwin/-/wikis/Debugging/Debugging-DRM-issues > explains how to do that; ideally you should enable the logging through ssh > and then trigger KWin to enable the display by moving the mouse or pressing > some key, and then stop the logging again. Sorry for the delay! Please find the log in the attachment. Thank you for your help in troubleshooting this! |