Date: Fri, 12 Jul 2024 17:33:24 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 280028] S3 suspend of Thinkpad x270 stopped working after freebsd-update to 14.1-RELEASE-p1 Message-ID: <bug-280028-227-zpZNtXhCzP@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-280028-227@https.bugs.freebsd.org/bugzilla/> References: <bug-280028-227@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D280028 Mark Johnston <markj@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|New |Open CC| |markj@FreeBSD.org --- Comment #19 from Mark Johnston <markj@FreeBSD.org> --- (In reply to cos from comment #16) So, this procstat trace is from the system after it hanged? I don't see any obvious culprits there. (In reply to cos from comment #18) Is this workaround completely reliable? Have you been able to suspend/resu= me, say, 10 times in a row after disabling XDM? The xdm process in the procstat output I linked above isn't doing anything abnormal, so that's a bit odd. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-280028-227-zpZNtXhCzP>