On Thu, May 17, 2018 at 8:46 AM, Johannes Lundberg <johal...@gmail.com>
> On Thu, May 17, 2018 at 7:43 AM, Andriy Gapon <a...@freebsd.org> wrote:
>> On 17/05/2018 02:07, Johannes Lundberg wrote:
>> > https://github.com/freebsd/freebsd/commit/66f063557f257baa9c
>> > x86 cpususpend_handler: call wbinvd after setting suspend state bits
>> That's very interesting and surprising.
>> That commit changes something that happens before suspend, it should not
>> any effect on the system state after resume.
>> Does anyone have a theory of what could be wrong?
> Nope but moving
> CPU_CLR_ATOMIC(cpu, &suspended_cpus);
> back to the end of that scope fixes it.
I did some further testing.
is what "breaks" resume.
Is this Intel only or this it happen on AMD as well (which this patch was
>> > How to test (i915kms)
>> > Start X with glxgears
>> > Confirm running stable at 60 fps
>> > suspend/resume (S3)
>> > glxgears is now fluctuating between 10-40 fps.
>> Andriy Gapon
email@example.com mailing list
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"