Date: Thu, 17 May 2018 22:42:38 +0300 From: Andriy Gapon <avg@FreeBSD.org> To: Pete Wright <pete@nomadlogic.org>, FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: suspend/resume regression Message-ID: <34cfc5d0-041b-4822-6e8a-5949b4cc183a@FreeBSD.org> In-Reply-To: <fb0e50cf-1ed1-a146-9611-f4697d5abab8@nomadlogic.org> References: <1e608109-fcdd-d794-b03a-2e417300b95a@nomadlogic.org> <fb0e50cf-1ed1-a146-9611-f4697d5abab8@nomadlogic.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 17/05/2018 21:14, Pete Wright wrote: > > > On 05/12/2018 19:25, Pete Wright wrote: >> hi there - i have an amd64 laptop that's been running CURRENT for a while >> using both drm-next and drm-stable for graphics. during the past week or so >> i've run into issues with suspend resume...well technically resume has stopped >> working. i've tested a couple configurations and none have allowed my system >> to resume successfully: >> >> - drm-next installed with DMC firmware loaded >> - drm-next installed without DMC firmware loaded (worked previously) >> - drm-stable with DMC >> - drm-stable without DMC >> - no drm modules loaded. >> >> I've also tested these configs with the following sysctl set to 0 and 1: >> hw.acpi.reset_video >> >> at this point i'd like to help find what the regression i'm running into is, >> so any pointers on how i can help? the system seems to boot and i'm pretty >> sure i can ssh into it most times, just not sure what info i should grab to >> help. nothing of interest in messages or dmesg buffer either. >> > > Closing the loop on this thread. Git commit > 4e99d4e797ba9cea01897b6909b061db841f855a fixes this issue on my end. For more > info there is a thread on this list named "Lag after resume culprit found" that > has details. Thank you for confirming that it was the same issue and that (or, rather, because) it's fixed now. -- Andriy Gapon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?34cfc5d0-041b-4822-6e8a-5949b4cc183a>