On 16/09/2020 10:05, Warner Losh wrote: > > > On Wed, Sep 16, 2020 at 12:31 AM Andriy Gapon <avg_at_freebsd.org > <mailto:avg_at_freebsd.org>> wrote: > > On 15/09/2020 23:13, Eirik Øverby wrote: > > On 9/15/20 9:50 PM, Andriy Gapon wrote: > >> On 15/09/2020 22:36, Eirik Øverby wrote: > >>> Now, since I updated from r365358 to r365688, I have not once been able > to wake from sleep. > >> > >> Is that the only thing that changed? > >> Any port / package upgrades? > > > > There have been updates to packages, yes - but it didn't even occur to me > that these could impact the resume process at such an early stage. Not sure > which that would be; obviously the drm module has been rebuilt each time I > upgraded, but I don't have any other kernel modules installed from packages. > > Yes, I specifically had drm modules in mind. > > > I too can report this for my Lenovo Yoga running code as of September 13, but > with manu's latest drm... It used to work fine, but my last build on the system > was from May. Most likely a new panic in that code path, but I've not chased > down further... One thing to check is to set debug.acpi.suspend_bounce=1 before suspending. This will run suspend (and then resume) methods of all drivers just like for a normal suspend, but will skip the actual ACPI suspend. -- Andriy GaponReceived on Wed Sep 16 2020 - 06:30:18 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:41:25 UTC