Created attachment 1844508 [details]
Requested kernel logs
1. Please describe the problem: Monitors no longer remain in sleep state after a screen lock, instead "waking up" and displaying a black screen.
2. What is the Version-Release number of the kernel: 5.15.5-200.fc35.x86_64
3. Did it work previously in Fedora? If so, what kernel version did the issue
*first* appear? Old kernels are available for download at
https://koji.fedoraproject.org/koji/packageinfo?packageID=8 : 5.14.17 and 5.14.18 do not have the issue. 5.15.4 does.
I have performed a bisect, first "bad" commit to master is 55285e21f04517939480966164a33898c34b2af2, the same change made it into the 5.15 branch as e3b39825ed0813f787cb3ebdc5ecaa5131623647.
4. Can you reproduce this issue? If so, please provide the steps to reproduce
the issue below: Yes:
1. Boot system (Fedora Workstation 35 in this case)
2. Log in
3. Lock screen (after a few seconds, monitors will enter power save "sleep" state)
4. Wait (usually no more than 30 seconds, sometimes up to a few minuites)
5. Observer monitor leaving "sleep" state (backlight comes back on), but nothing is displayed
5. Does this problem occur with the latest Rawhide kernel? To install the
Rawhide kernel, run ``sudo dnf install fedora-repos-rawhide`` followed by
``sudo dnf update --enablerepo=rawhide kernel``: Have not tested, I will if requested.
6. Are you running any modules that not shipped with directly Fedora's kernel?: No.
7. Please attach the kernel logs. You can get the complete kernel log
for a boot with ``journalctl --no-hostname -k > dmesg.txt``. If the
issue occurred on a previous boot, use the journalctl ``-b`` flag.
The initial discovery of this bug happened elsewhere. The system in question is a desktop using the amdgpu GPU driver, two monitors connected via DP->HDMI adapters.
 - https://bugzilla.redhat.com/show_bug.cgi?id=1894624#c17
I have reproduced with latest master (a51e3ac43ddbad891c2b1a4f3aa52371d6939570) and reported the bug upstream: https://bugzilla.kernel.org/show_bug.cgi?id=215203
*** Bug 1894624 has been marked as a duplicate of this bug. ***
This message is a reminder that Fedora Linux 35 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 35 on 2022-12-13.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '35'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version'
to a later Fedora Linux version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora Linux 35 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.
Fedora Linux 35 entered end-of-life (EOL) status on 2022-12-13.
Fedora Linux 35 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.
If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.
If you are unable to reopen this bug, please file a new report against an
Thank you for reporting this bug and we are sorry it could not be fixed.