Date: Tue, 15 May 2018 07:48:23 -0700 From: Pete Wright <pete@nomadlogic.org> To: Theron <theron.tarigo@gmail.com>, Niclas Zeising <zeising+freebsd@daemonic.se>, Andriy Gapon <avg@FreeBSD.org>, FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: suspend/resume regression Message-ID: <35d0f223-681a-205a-0f57-4ec360761726@nomadlogic.org> In-Reply-To: <a98cef80-00d4-fbb5-dcf0-6791370ec0d1@gmail.com> References: <1e608109-fcdd-d794-b03a-2e417300b95a@nomadlogic.org> <f9396ec8-c4c4-03cf-f0db-89bc6c41e82f@FreeBSD.org> <fd2a5f46-5c2f-ffa0-e923-16dc8756494c@daemonic.se> <3488a8a4-8cad-d6a8-0852-3bbbdd971c7f@gmail.com> <26f5ec31-3994-eac9-0c43-6d2458c35ad0@nomadlogic.org> <9f7fcdaa-99ea-98f4-8ef3-c8da6060542e@nomadlogic.org> <a98cef80-00d4-fbb5-dcf0-6791370ec0d1@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 05/14/2018 20:35, Theron wrote: > On 05/13/18 15:44, Pete Wright wrote: >>> so i've done a bit more debugging on my end. i've even installed >>> the 11.2-BETA branch last night since 11-STABLE worked without >>> issues about a month or so ago. >>> >>> i've set "debug.acpi.resume_beep=1" and when resuming after entering >>> an S3 sleep state the bell rings and does not stop until i do a hard >>> reset (both with i915kms loaded and unloaded). >>> >>> kinda at a loss as to how this could break both CURRENT and >>> basically 11-STABLE. i'm going to make a ubuntu live image and test >>> that, my laptop is a System76 laptop that shipped with ubuntu >>> originally. if that is broken as well then i guess this could be a >>> hardware issue. >>> >> ubuntu live image suspends/resumes without issue so this certainly >> seems to be a freebsd issue unfortunately. i guess next step is to >> attempt to find a working CURRENT snapshot that does suspend/resume >> without issue then start looking at commits? >> >> -pete >> > Returning to the original issue: complete failure to resume, rather > than slowness: I am affected as well. CURRENT r333093 worked, but > r333582 fails in a manner consistent with what Pete has described, > with or without drm loaded. There have been a few commit messages > mentioning ACPI in that window of history, which I will use to help me > bisect when I have time. > do you think it may be due to r333150 "Merge ACPICA 20180427." not sure if that's been merged into 11-STABLE, but it seems to touch a lot of bits that could effect suspend/resume. -p -- Pete Wright pete@nomadlogic.org @nomadlogicLA
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?35d0f223-681a-205a-0f57-4ec360761726>