Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 14 May 2018 07:34:56 -0700
From:      Pete Wright <pete@nomadlogic.org>
To:        Niclas Zeising <zeising+freebsd@daemonic.se>, Theron <theron.tarigo@gmail.com>, Andriy Gapon <avg@FreeBSD.org>, FreeBSD Current <freebsd-current@freebsd.org>
Subject:   Re: suspend/resume regression
Message-ID:  <46e8a643-a6b0-b291-093b-7cf21c41c8fd@nomadlogic.org>
In-Reply-To: <92bc7e50-2252-5e6a-cf2c-165ef5f6f2d3@daemonic.se>
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> <92bc7e50-2252-5e6a-cf2c-165ef5f6f2d3@daemonic.se>

next in thread | previous in thread | raw e-mail | index | archive | help


On 05/14/2018 01:18, Niclas Zeising wrote:
> On 05/13/18 21:44, Pete Wright wrote:
>>
>>
>> On 05/13/2018 10:27, Pete Wright wrote:
>>>
>>>
>>> On 05/13/2018 08:58, Theron wrote:
>>>>> Hi!
>>>>> I'm also seeing issues, not as severe as Pete, but after I resume 
>>>>> (which works, with drm-next and DMC firmware), the system becomes 
>>>>> sluggish.  It feels like I/O takes more time, and graphics are 
>>>>> sluggish (very sientific, I know, but for instance git operations 
>>>>> are much slower after a resume).  I know there's been an update to 
>>>>> acpica between my system updates, when this started to happen, but 
>>>>> I haven't had time to revert that update and test again.  I will 
>>>>> try to do that and report back.
>>>>> Regards
>>>> Hi Niclas,
>>>> I used drm-next on Skylake with issues which sound similar. 
>>>> Resuming from suspend, or simply switching the laptop display 
>>>> output off and on from xrandr, resulted in graphics sluggishness 
>>>> (drop to 30fps in glxgears) and graphical corruption in Xorg apps, 
>>>> which persisted even after restarting these apps. Switching to 
>>>> drm-stable made the problems go away; I haven't had time to figure 
>>>> out what -next is doing differently to cause them.
>>>>
>>>> Pete's issue sounds more severe, and unrelated as it happens 
>>>> without drm loaded.  My kernel is two weeks out of date (r333093), 
>>>> so I need to check whether the more recent changes affect my system 
>>>> as well.
>>>>
>>> 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?
>>
>
> Hi!
> It's a bit worrisome that your regression occurs both on CURRENT and 
> STABLE.  There was an update to both drm-next-kmod and drm-stable-kmod 
> last week, but both are very minor.  One question, did you install 
> from pkg or compile from ports?

i create a package directly from the github mirror of the ports tree 
(i.e. make package; pkg install...).

-pete

-- 
Pete Wright
pete@nomadlogic.org
@nomadlogicLA




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?46e8a643-a6b0-b291-093b-7cf21c41c8fd>