Date: Thu, 17 May 2018 11:12:48 -0700 From: Pete Wright <pete@nomadlogic.org> To: Johannes Lundberg <johalun0@gmail.com> Cc: x11-list freebsd <freebsd-x11@freebsd.org> Subject: Re: Lag after resume culprit found Message-ID: <49b7e10c-998a-e73d-8475-063d50414395@nomadlogic.org> In-Reply-To: <CAECmPwtULDe9GGK0PhnUa7_n=zxripJj9nh5m0RTF9XqKhXKYQ@mail.gmail.com> References: <CAECmPwtULDe9GGK0PhnUa7_n=zxripJj9nh5m0RTF9XqKhXKYQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 05/16/2018 16:07, Johannes Lundberg wrote: > https://github.com/freebsd/freebsd/commit/66f063557f257baa9c8aeab9f933171eaa6e1cfa > x86 cpususpend_handler: call wbinvd after setting suspend state bits > > 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. > > > Way past bedtime now so I stop here for today. i can confirm that the commit avg@ put in to HEAD today to revert this solved my suspend/resume issues on my Kabylake system running drm-next. Thanks for tracking this down Johannes, and the quick attention from Andriy to fix this! cheers, -pete -- Pete Wright pete@nomadlogic.org @nomadlogicLA
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?49b7e10c-998a-e73d-8475-063d50414395>