[Bug 280028] S3 suspend of Thinkpad x270 stopped working after freebsd-update to 14.1-RELEASE-p1
Date: Sat, 20 Jul 2024 07:32:48 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280028 --- Comment #20 from cos <freebsd.org@fydagy.netizen.se> --- Apologies for being a slow in reporting back. This being my daily driver, it took a few days before being able to reboot into the problematic bootenv. (In reply to Mark Johnston from comment #19) Thanks for looking at my files. They are as described. Maybe I should be more clear in pointing out that the kernel doesn't fully hang. The shutdown gets stuck in some kind of partial shutdown, without (at least some) wifi and usb drivers. As long as I'm not too picky with such functionality, I can still use the system as normal. ;) With X running, the first suspend completes successfully while the second attempt consistently fail, until calling halt. Without X, suspending + resuming x 10 works. Verified again today, with the actual increase from a few cycles up to ten. I also updated to 14.1-p2 on a cloned bootenv, experiencing identical results. Please let me highlight this dmesg difference and state that, supported by that stuff works after killing X, I believe the output to be related: -drmn0: [drm] [ENCODER:102:DDI B/PHY B] is disabled/in DSI mode with an ungated DDI clock, gate it -drmn0: [drm] [ENCODER:116:DDI C/PHY C] is disabled/in DSI mode with an ungated DDI clock, gate it I did some web searches of the above, but did unfortunately not become much wiser. I also made a half-baked attempt starting a git-bisect of `/usr/src`, but couldn't understand which commit 14.1-p1 was built from. Not even after looking in seemingly relevant handbooks and asking on irc. (It ended up only with #280186 being posted instead.) Should one just go with release/14.1.0 as the good tag and the HEAD of releng/14.1 as the known bad commit? (I would have expected 14.1.1 and 14.1.2 tags for 14.1-p1 and 14.1-p2 respectively, but am uncertain if it's the right place as those do not exist.) -- You are receiving this mail because: You are the assignee for the bug.