Date: Mon, 03 May 2021 22:08:31 +0000 From: bugzilla-noreply@freebsd.org To: x11@FreeBSD.org Subject: [Bug 253801] graphics/drm-fbsd13-kmod panic when resuming from sleep Message-ID: <bug-253801-7141-XkszZJS6fU@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-253801-7141@https.bugs.freebsd.org/bugzilla/> References: <bug-253801-7141@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=3D253801 --- Comment #14 from Patricio Villar <patovm04@gmail.com> --- UPDATE: I think I finally made some progress to workaround this problem: I used to have a little devd script that locked my screen when resuming from sleep. It never did any harm on FreeBSD 11/12 so I didn't think it could be problematic now, but it turns out it may have been the culprit... After all, something definitely changed on 13.0. What I did was modify the moment when this script was executed: instead of becoming active at resume, it is now triggered when closing the lid (which means, before suspend). I don't want to assume this is the ultimate solution or something, especial= ly since so many assumptions have been made to this point, but so far it REALLY seems to have fixed this issue for me. I've had about 20+ successful and uninterrupted (this is, without shutting = down or rebooting in the middle) suspend/resume cycles without any issue. And I'= ve really tried to make it difficult to succeed by having multiple programs running at the same time and stuff like that. I don't know if some of you too have some kind of custom scripts that get executed at resume time, but if that's the case, I encourage you to switch = them to run while going to sleep instead, or even drop them altogether, and see = if it makes a change for you. --=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-253801-7141-XkszZJS6fU>