From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Brian J. Murrell" Subject: Re: i915 when using vaapi, screen only refreshes on mouse movement Date: Thu, 05 Mar 2015 09:04:54 -0500 Message-ID: <1425564294.14015.14.camel@interlinx.bc.ca> References: <1425300262.8476.29.camel@interlinx.bc.ca> <20150302133749.GB28813@nuc-i3427.alporthouse.com> <1425305230.25721.4.camel@interlinx.bc.ca> <20150302142707.GC28813@nuc-i3427.alporthouse.com> <1425388984.5905.38.camel@interlinx.bc.ca> <20150303134927.GD28813@nuc-i3427.alporthouse.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0876494134==" Return-path: Received: from plane.gmane.org (plane.gmane.org [80.91.229.3]) by gabe.freedesktop.org (Postfix) with ESMTP id 632726E300 for ; Thu, 5 Mar 2015 06:05:03 -0800 (PST) Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1YTWOc-0003G7-14 for intel-gfx@lists.freedesktop.org; Thu, 05 Mar 2015 15:05:02 +0100 Received: from d67-193-232-12.home3.cgocable.net ([67.193.232.12]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 05 Mar 2015 15:05:02 +0100 Received: from brian by d67-193-232-12.home3.cgocable.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 05 Mar 2015 15:05:02 +0100 In-Reply-To: <20150303134927.GD28813@nuc-i3427.alporthouse.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: intel-gfx-bounces@lists.freedesktop.org Sender: "Intel-gfx" To: intel-gfx@lists.freedesktop.org List-Id: intel-gfx@lists.freedesktop.org --===============0876494134== Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-K7nfjEuSJFGNFG3K4+oi" --=-K7nfjEuSJFGNFG3K4+oi Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Tue, 2015-03-03 at 13:49 +0000, Chris Wilson wrote: >=20 > It's an OR. The bug I am thinking about has a w/a in the ddx and a real > fix in the kernel. Either one should do, and I think will resolve your > issue. Yeah, upgrading to that newer Intel driver did seem to do the trick. I wonder if it's making https://code.google.com/p/chromium/issues/detail?id=3D463243 worse though since that problem seems to have gotten worse with the new driver. It didn't even really occur to me that that problem was related to my GPU driver but I've since put the same version of Chrome on my laptop with an nVidia Quadro and I have not see the same problem there (yet). Cheers, b. --=-K7nfjEuSJFGNFG3K4+oi Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAABAgAGBQJU+GKGAAoJENrB0DQWy8igKPgH/3Y7IV/RNcnTfUtzKRbl+ur5 IetCUNlHBz3IW192rjyqK8pvi/MHeOc0Gw8RWiOhBE9fWPUgk4feIqnF3/LJDRVj RjvykxN4r187lJRSCijZCy8u/CDN4YcdySNei03UOwAU5/LAZRoitqLq5s4FKmWg hlECCK3BldqckP2dYLI+m8u51TxpncH1/brdmlFomGb/n3Pv/Dvr+FOWpHzFv20X tGVe0Ld6T9dN2hB+nawYSqHmPODoNrq++K+kSnA7KQ2Pu6pNb9qhpRLAhISo2/jb kY5i4QWGkZZa7FlOPTZFLra5awEUZW+zbsz66pnlA9hJYN6j4qwUH1AvuwQQlG4= =tR3/ -----END PGP SIGNATURE----- --=-K7nfjEuSJFGNFG3K4+oi-- --===============0876494134== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KSW50ZWwtZ2Z4 IG1haWxpbmcgbGlzdApJbnRlbC1nZnhAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHA6Ly9saXN0 cy5mcmVlZGVza3RvcC5vcmcvbWFpbG1hbi9saXN0aW5mby9pbnRlbC1nZngK --===============0876494134==--