I'm on a Framework laptop uses 6.1-lts drm-kmod, and suspend/resume has been working but I compiled and installed main-n269104-41956c13f950 yesterday and suspend/resume is freezing. What I experience is it drops down to a console view and just sits there and is unresponsive. I have to force restart the laptop. What information can I provide to help?
If it was working before it's unlikely to be drm fault then. First thing to try will be to recompile drm-kmod to be sure that it's synced with your kernel. Then bisect the kernel.
Created attachment 249733 [details] Set-S3-suspend-type Test this patch
(In reply to Vladimir Kondratyev from comment #2) The patch looks good but I don't think that's the problem OP is having as 6.1 worked before for them.
Thank you for the incredibly fast response time. I also tried to see if I had a boot environment for the working version but, alas, I do not. I deleted it before testing suspend. I will test this patch and report back.
There was a report of some audio stack patches causing a regression with suspend-to-S3. They are reverted in main now, so it might be worth trying to update.
I will do that as well, thank you.
Can confirm latest HEAD did not resolve the issue. I'm trying the patch now.
Just to confirm I'm doing everything right, I have been using 6.1-lts for some time. I am pulling down the latest 15.0-CURRENT branch FreeBSD: make buildkernel buildworld make installkernel reboot make installworld etcupdate -F reboot drm-kmod: make make install modify rc.config to load i915kms reboot Everything starts fine works. Try to enter S3 and I get pulled into console view and it just sits there. drm-kmod commit: 36ad244cd1446fd974189be7a7ab1a92989b8eeb
The patch did not resolve the issue.
(In reply to mmatalka from comment #10) > The patch did not resolve the issue. It fixes S3 suspend on amdgpu rather than on i915kms
Ah that makes sense. Sorry, I was unclear about what hardware I'm running.
Good news: the latest HEAD I compiled today, main-n269229-cce11997a052:, is working with suspend and resume (so far). Yay!
(In reply to mmatalka from comment #13) This issue should be presumed resolved then?
Indeed
It's not "Overcome By Events", the bug was on drm but it wasn't drm.