Date: Thu, 17 May 2018 09:43:54 +0300 From: Andriy Gapon <avg@FreeBSD.org> To: Johannes Lundberg <johalun0@gmail.com>, freebsd-current <freebsd-current@freebsd.org> Subject: Re: Lag after resume culprit found Message-ID: <acaa419d-891e-96b1-7c1f-3203857c07ec@FreeBSD.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 17/05/2018 02:07, Johannes Lundberg wrote: > https://github.com/freebsd/freebsd/commit/66f063557f257baa9c8aeab9f933171eaa6e1cfa > 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 have any effect on the system state after resume. Does anyone have a theory of what could be wrong? > 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?acaa419d-891e-96b1-7c1f-3203857c07ec>