On Sat, Jan 09, 2016 at 04:07:05PM -0800, Marc MERLIN wrote:
> On Fri, Jan 08, 2016 at 09:42:24AM -0800, Marc MERLIN wrote:
> > On Sun, Jan 03, 2016 at 08:04:27AM -0800, Marc MERLIN wrote:
> > > My hunch at this point is that google-chrome-beta is taxing the GPU and
> > > causing the driver to misbehave. I'm now back to
> > > 2:2.99.917+git20151217-1~exp1 and 4.3.3 and will run google-chrome-beta
> > > --disable-gpu, but this kills other stuff I need and won't be working
> > > anymore as a result :(
> >
> > google-chrome-beta --disable-gpu did not help.
> >
> > 4.3.3 and xserver-xorg-video-intel 2:2.99.917+git20151217-1~exp1 gave a
> > full deadlock
> >
> > Downgrading to 3.19.8 also gave the full deadlock.
> >
> > I've now just downgraded xserver-xorg-video-intel to 2:2.99.917-1 and
> > will see how that goes.
>
> And I got a full deadlock with that combination too :(
>
> Sigh. What broke? The driver was never great, but it wasn't nearly as
> bad as it's been in the last months (i.e. a crash/deadlock every other
> day on average). This is quite unbearable.
Well, I had my system board replaced just in case, and this seems to
have addressed my hangs.
So that's good news, it seems that the driver doesn't have a big
regression on my chip afterall.
Marc
--
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems ....
.... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/ | PGP 1024R/763BE901
_______________________________________________
Intel-gfx mailing list
Intel-gfx@xxxxxxxxxxxxxxxxxxxxx
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
