Hi Klaus, On Mon, Jun 09, 2025 at 12:26:37AM +0200, Klaus Singvogel wrote: > > Hi, > > Salvatore Bonaccorso wrote: > > Control: tags -1 + moreinfo > > > > Hi, > > > > On Sun, Jun 08, 2025 at 01:55:23PM +0200, Klaus Singvogel wrote: > > > Package: src:linux > > > Version: 6.1.140-1 > > > Severity: serious > > > Justification: Policy 11.8.1 > > > > > > Dear Maintainer, > > > > > > *** Reporter, please consider answering these questions, where > > > appropriate *** > > > > > > * What led up to the situation? > > > Resume from suspend-to-disk keeps screen dark. The system is > > > running, and is accessable via network, but no X11. > > > * What exactly did you do (or not do) that was effective (or > > > ineffective)? > > > acpitool -S; reboot, input of disk encryption password > > > * What was the outcome of this action? > > > Two dark monitors, which report no HDMI and (the other) no > > > DisplayPort signal > > > * What outcome did you expect instead? > > > My window system was expected, with a X11 windows and mouse. > > > > > > * Additional, maybe helpful information: > > > I've a AMD Ryzen 7 5700G system, where the on-chip GPU is used as > > > the only graphic card, and where no additional graphic card is installed. > > > I saw this in 3 of 3 times, after upgrading to > > > linux-image-6.1.0-37-amd64 kernel. Running the old, saved > > > linux-image-6.1.0-34-amd64 kernel package (kernel 6.1.135-1) - selection > > > via grub - , the situation doesn't occur and the resumes are solid now. > > > Note that I didn't upgrade or install any other packages in between, only > > > using a different Linux kernel from Debian, and now the situation doesn't > > > occur anymore. > > > > Thanks for your report. > > > > Can you please report here a full boot long once triggering the issue > > with the 6.1.140-1 please from boot, to suspend and then resume. > > Find it attached.
This is very helpful thanks. While the OOT is not directly related, can you confirm that you get the same problem if you do not load the OOT wl module? If yes, the next step would be to report it upstream at https://gitlab.freedesktop.org/drm/amd with the full boot log attached ot the report there (there are similar, but not identical reports filled there, but closed). Regards, Salvatore
