Hi all. I believe this should be fixed with Mesa master - specifically,
this commit:
commit c4fd0c9052dd391d6f2e9bb8e6da209dfc7ef35b
Author: Kenneth Graunke
Date: Sat Jan 17 23:21:15 2015 -0800
i965: Work around mysterious Gen4 GPU hangs with minimal state
changes.
If you're able to test
I gave up on waiting and just pushed my original fix.
commit 0380ec467d78f40b5c8134158ca48b4c5378b282
Author: Kenneth Graunke
Date: Wed Mar 12 01:43:40 2014 -0700
i965: Don't enable reset notification support on Gen4-5.
arekm reported that using Chrome with GPU acceleration enable
Closing as fixed per comment #24.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1282867
Title:
Frequent hang and render glitches in Xorg, caused by SNA
To manage notifications about this bug go to:
*** Bug 71890 has been marked as a duplicate of this bug. ***
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1140716
Title:
[regression] 3.5.0-26-generic and 3.2.0-39-generic GPU hangs on
Sandybri
Fixed in Mesa 9.2.3 (out today), the upcoming Mesa 10.0 release, or Mesa
master.
This fixes the Sandybridge-specific GPU hang where i915_error_state (aka
/sys/class/drm/card0/error) lists an IPEHR of 0x79050005.
If you experience a GPU hang and your IPEHR is not 0x79050005, that is a
different bu
(In reply to comment #33)
> Created attachment 88969 [details]
> i915_error_state
>
> Still hang after playing hedgewars for nearly an hour, but it doesn't hang
> continuously, just one time. Dmesg shows:
> [ 3929.521951] [drm:i915_hangcheck_elapsed] *ERROR* stuck on render ring
> [ 3929.521963] [
libdrm master, intel-gpu-tools master, and Mesa from either master or
the 9.1 branch now recognize these PCI IDs. I believe that's everything
other than libva.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net
(In reply to comment #25)
> I've pushed a patch to KWin that should fix the problem. The patch is in
> both master and the 4.9 branch, so you should see it in 4.9.3. That release
> will be tagged on Thursday.
Thanks Fredrik! Based on that, I'm closing this as RESOLVED/NOTOURBUG.
> @Rune: The GLX
Ouch. Well...in that case, I'm not sure what to do on the Mesa
side...perhaps a point release of KWin could fix this?
For what it's worth, KWin from git master has the slowdown with the GLX
backend, but appears to work well with the EGL backend. I imagine
that's because it uses eglChooseConfig,
Created attachment 69265
Bisect log (Kayden)
I managed to reproduce this after all.
Steps to reproduce:
1. Enable KWin's "Show FPS" counter plugin.
2. Configure the "Present Windows" effect to one of the screen corners.
3. Mash that repeatedly and watch the FPS counter.
On HD 4000, a good versio
Unfortunately, I can't seem to reproduce this: I also have KDE 4.9.2 and
Mesa 9.0, but it appears to work fine for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1061073
Title:
Desktop effects ar
Presumably fixed in Linux v3.4. If problems persist, feel free to
reopen.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/977281
Title:
[sandybridge-m-gt2] False GPU lockup render.IPEHR: 0x7a02
Working in Mesa master, with Ian's version of the patches.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/981883
Title:
MapsGL doesn't render properly on nouveau
To manage notifications about this
Closing, since the original reporter indicated that it was fixed by the
STC eviction mode patch.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/950300
Title:
[snb-gt2] GPU lockup render.IPEHR: 0x7a00
Google Earth seems to be working fine on my GM965, even with Mesa 8.0.2.
I haven't tried an older kernel or xf86-video-intel, though, so I'm not
certain whether this got fixed at some point or if I'm just failing to
reproduce the issue.
--
You received this bug notification because you are a memb
Hi! I believe this was fixed by the following commit, which is already
part of the Mesa 8.0.3 release:
commit 93e94cbb48a679b7bf67594adb6f858526b37935
Author: Eric Anholt
Date: Fri Feb 10 12:54:25 2012 -0800
intel: Fix rendering from textures after RenderTexture().
There's a seri
*** Bug 48748 has been marked as a duplicate of this bug. ***
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/966631
Title:
[sandybridge-m-gt2] GPU lockup render.IPEHR: 0x7a03 with Google
Maps(
Yeah, the 0x7a02 isn't super helpful...it's PIPE_CONTROL a.k.a.
flush. In other words, the GPU was doing something and it died. :)
It'd be worth checking if the kernel fix for MapsGL/Google
Earth/gzdoom/etc. fixes this. My guess is that it does. If not, I'll
certainly be glad to try and deb
*** Bug 48791 has been marked as a duplicate of this bug. ***
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/966631
Title:
[sandybridge-m-gt2] GPU lockup render.IPEHR: 0x7a03 with Google
Maps(
*** Bug 48526 has been marked as a duplicate of this bug. ***
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/966631
Title:
[sandybridge-m-gt2] GPU lockup render.IPEHR: 0x7a03 with Google
Maps(
Linus merged the patch into the upstream kernel, and Greg picked it up
for 3.3 stable. Hopefully should be landing in a distro near you. :)
Marking fixed. If upgrading kernels is inconvenient, you can also apply
the workaround manually via "sudo intel_reg_write 0x2120 0x1206800", or
by disabling
On the i965 driver, I tracked it down to the commit where I started
advertising vertex shader texture units. I also noticed that the
rendering is broken using classic swrast (LIBGL_ALWAYS_SOFTWARE=1), but
if I hacked swrast to advertise 0 VS texture image units, then it
worked.
Obviously MapsGL i
It turns out that Daniel already implemented a workaround for this in
the kernel...but the register write isn't sticking. Apparently this
register needs to be written later in the initialization process.
I've sent a preliminary (lame) patch to intel-gfx to spark some
discussion on what the right
Mashing this register makes the problem go away for me:
$ sudo intel_reg_write 0x2120 '0x1206800'
Value before: 0x6820
Value after: 0x6800
Anyone care to try it out? I'll put together a kernel patch soon.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
I'm seeing this on i965/Sandy Bridge as well, so maybe it's something in
Core Mesa? Either that or we all have similar bugs :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/981883
Title:
MapsGL do
Closing as it works for me and no response for a month.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/899159
Title:
[snb-gt2] GPU lockup render.IPEHR: 0x7b009004 (Needs 8.0.2)
To manage notificati
Hi Martin,
Your trace works fine on my Sandybridge system. No hangs.
In order to run a 32-bit application, you'll need to use a 32-bit build
of Mesa (libGL.so and i965_dri.so). Note that your system 'glxinfo'
binary is likely 64-bit, so it won't give an accurate indication of what
version of Me
Yeah, the OpenGL man pages come from Khronos, not from Mesa.
Distribution packaging issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/189852
Title:
OpenGL man pages missing
To manage notificatio
This is on the 8.0 branch as 16cc79f975816c0741711560be48fc498d4b4794.
Closing since I believe it's fixed and haven't heard otherwise.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/899159
Title:
[s
Tom,
It turns out that your GPU hang was due to a bug in our MRT support. It
should be fixed on master by:
commit 172bb92db1a3c317867d9cfec6f15c09c37a0f6c
Author: Kenneth Graunke
Date: Sat Feb 18 21:29:29 2012 -0800
i965: Only set Last Render Target Select on the last FB write.
Closing this bug. We believe the primary issue here is fixed in the
Linux 3.2 kernel, and many people seem to agree. I'm guessing most of
the people who had trouble were either trying to use intel_reg_write had
trouble patching the kernel.
It sounds like a few people still have rendering glitche
For what it's worth, the patches are included in the 3.2 kernel which
was just released. So you could use that.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/829086
Title:
Artifacts in 3D with Sand
32 matches
Mail list logo
