[Ubuntu-x-swat] [Bug 1388612]
Hi all. I believe this should be fixed with Mesa master - specifically, this commit: commit c4fd0c9052dd391d6f2e9bb8e6da209dfc7ef35b Author: Kenneth Graunke kenn...@whitecape.org 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 with Mesa master, I'd appreciate any reports of whether this solved the problem for you. It seems to have helped for me. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1388612 Title: [GM965] GPU lockup running OpenGL applications on Dell Vostro 1510 To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1388612/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1299499]
I gave up on waiting and just pushed my original fix. commit 0380ec467d78f40b5c8134158ca48b4c5378b282 Author: Kenneth Graunke kenn...@whitecape.org 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 enabled on GM45 triggered the hw_ctx != NULL assertion in brw_get_graphics_reset_status. We definitely do not want to advertise reset notification support on Gen4-5 systems, since it needs hardware contexts, and we never even request a hardware context on those systems. Cc: 10.1 mesa-sta...@lists.freedesktop.org Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=75723 Signed-off-by: Kenneth Graunke kenn...@whitecape.org Hopefully it'll get picked up for the next 10.1 release... -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1299499 Title: kwin crashes on desktop startup with wobbly windows enabled To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1299499/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1282867]
Closing as fixed per comment #24. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in 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: https://bugs.launchpad.net/linux/+bug/1282867/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1140716]
*** Bug 71890 has been marked as a duplicate of this bug. *** -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1140716 Title: [regression] 3.5.0-26-generic and 3.2.0-39-generic GPU hangs on Sandybridge To manage notifications about this bug go to: https://bugs.launchpad.net/dri/+bug/1140716/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1175533]
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-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1175533 Title: [HSW] intel VGA driver i915 doesn't support new haswell graphics [8086:0a2e] To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1175533/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1061073]
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 version of Mesa results in perhaps ~55-60 FPS. Bad Mesa can be as low as 17 FPS, often mid-30s. I also went ahead and bisected it (the log is attached). e943e5c291c5f4c017f9f5a483f194031fc3 is the first bad commit commit e943e5c291c5f4c017f9f5a483f194031fc3 Author: Chad Versace chad.vers...@linux.intel.com Date: Thu Aug 2 17:13:17 2012 -0700 intel: Advertise multisample DRI2 configs on gen = 6 This turns on window system MSAA. So in other words, it looks like KDE is using multisampling now, whereas it didn't before. Our implementation of that may not be optimal, and may have bugs, but it will always be far slower than single sampling. My next question would be: how can one disable the use of MSAA in KWin or Plasma? I don't see an option for that, but I would be really surprised if there wasn't one... -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1061073 Title: Desktop effects are slow and desktop corruption using mesa 9 To manage notifications about this bug go to: https://bugs.launchpad.net/kdebase-workspace/+bug/1061073/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1061073]
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, and doesn't request any samples, so Mesa gives it a proper non-MSAA config. It's just with GLX, where KWin rolls its own algorithm, that there's a problem. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1061073 Title: Desktop effects are slow and desktop corruption using mesa 9 To manage notifications about this bug go to: https://bugs.launchpad.net/kdebase-workspace/+bug/1061073/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1061073]
(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 backend in KWin uses glXGetFBConfigs(), so the ordering rules in the spec don't apply here. I've thought about rewriting that code to use glXChooseFBConfig(), but I'm reluctant to touch working code without a good reason. This bug might be enough of a reason to do that though. @Rune: Feel free to double check by running glxinfo, but I believe the ordering is correct: multisample configs are always sorted later, as required. Using glXChooseFBConfig() does seem like a good idea...could guard against future problems (though I don't know what), and should simplify the code a fair bit. Also, KWin's EGL backend uses eglChooseConfig() and it never had this problem. That would also make the GLX and EGL backends more similar. Thanks again. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1061073 Title: Desktop effects are slow and desktop corruption using mesa 9 To manage notifications about this bug go to: https://bugs.launchpad.net/kdebase-workspace/+bug/1061073/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1061073]
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-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1061073 Title: Desktop effects are slow and desktop corruption using mesa 9 To manage notifications about this bug go to: https://bugs.launchpad.net/kdebase-workspace/+bug/1061073/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 977281]
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-X, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/977281 Title: [sandybridge-m-gt2] False GPU lockup render.IPEHR: 0x7a02 To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/977281/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 981883]
Working in Mesa master, with Ian's version of the patches. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/981883 Title: MapsGL doesn't render properly on nouveau To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/981883/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 950300]
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-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/950300 Title: [snb-gt2] GPU lockup render.IPEHR: 0x7a02 To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/950300/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 976331]
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 member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/976331 Title: [i965gm] False GPU lockup render.IPEHR: 0x7b009404 To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/976331/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 945441]
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 e...@anholt.net Date: Fri Feb 10 12:54:25 2012 -0800 intel: Fix rendering from textures after RenderTexture(). There's a serious trap for drivers: RenderTexture() does not indicate that the texture is currently bound to the draw buffer, despite FinishRenderTexture() signaling that the texture is just now being unbound from the draw buffer. We were acting as if RenderTexture() *was* the start of rendering and that we could make texturing incoherent with the current contents of the renderbuffer. This caused intel oglconform sRGB Mipmap.1D_textures to fail, because we got a call to TexImage() and thus RenderTexture() on a texture bound to a framebuffer that wasn't the draw buffer, so we skipped validating the new image into the texture object used for rendering. We can't (easily) make RenderTexture() indicate the start of drawing, because both our driver and gallium are using it as the moment to set up the renderbuffer wrapper used for things like MapRenderbuffer(). Instead, postpone the setup of the workaround render target miptree until update_renderbuffer time, so that we no longer need to skip validation of miptrees used as render targets. As a bonus, this should make GL_NV_texture_barrier possible. (This also fixes a regression in the gen4 small-mipmap rendering since 3b38b33c1648b07e75dc4d8340758171e109c598, which switched set_draw_offset from image-mt to irb-mt but didn't move the irb-mt replacement up before set_draw_offset). Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=44961 NOTE: This is a candidate for the 8.0 branch. I tested it on a GM965, and it seems to be working for me. Feel free to reopen if problems persist. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/945441 Title: [i965gme] GPU lockup render.IPEHR: 0x81323232 - GPU hang after executing supertuxkart To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/945441/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 966631]
*** Bug 48748 has been marked as a duplicate of this bug. *** -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/966631 Title: [sandybridge-m-gt2] GPU lockup render.IPEHR: 0x7a03 with Google Maps(WebGL) in Chromium To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/966631/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 977281]
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 debug it further. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/977281 Title: [sandybridge-m-gt2] False GPU lockup render.IPEHR: 0x7a02 To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/977281/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 966631]
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 HiZ and separate stencil (export hiz=false). (The kernel patch does the register write, so the intel_reg_write workaround is just as good.) commit 3a69ddd6f872180b6f61fda87152b37202118fbc Author: Kenneth Graunke kenn...@whitecape.org Date: Fri Apr 27 12:44:41 2012 -0700 drm/i915: Set the Stencil Cache eviction policy to non-LRA mode. Clearing bit 5 of CACHE_MODE_0 is necessary to prevent GPU hangs in OpenGL programs such as Google MapsGL, Google Earth, and gzdoom when using separate stencil buffers. Without it, the GPU tries to use the LRA eviction policy, which isn't supported. This was supposed to be off by default, but seems to be on for many machines. This cannot be done in gen6_init_clock_gating with most of the other workaround bits; the render ring needs to exist. Otherwise, the register write gets dropped on the floor (one printk will show it changed, but a second printk immediately following shows the value reverts to the old one). Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=47535 Cc: sta...@vger.kernel.org Cc: Rob Castle future...@gmail.com Cc: Eric Appleman erapple...@gmail.com Cc: aaron...@gmx.net Cc: Keith Packard kei...@keithp.com Signed-off-by: Kenneth Graunke kenn...@whitecape.org Reviewed-by: Daniel Vetter daniel.vet...@ffwll.ch Acked-by: Daniel Vetter daniel.vet...@ffwll.ch Signed-off-by: Dave Airlie airl...@redhat.com -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/966631 Title: [sandybridge-m-gt2] GPU lockup render.IPEHR: 0x7a03 with Google Maps(WebGL) in Chromium To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/966631/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 966631]
*** Bug 48526 has been marked as a duplicate of this bug. *** -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/966631 Title: [sandybridge-m-gt2] GPU lockup render.IPEHR: 0x7a03 with Google Maps(WebGL) in Chromium To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/966631/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 966631]
*** Bug 48791 has been marked as a duplicate of this bug. *** -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/966631 Title: [sandybridge-m-gt2] GPU lockup render.IPEHR: 0x7a03 with Google Maps(WebGL) in Chromium To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/966631/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 981883]
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 is changing its rendering technique when VS texturing is present (or not), but I suspect that there's something broken in core Mesa related to VS texturing. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/981883 Title: MapsGL doesn't render properly on nouveau To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/981883/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 981883]
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-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/981883 Title: MapsGL doesn't render properly on nouveau To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/981883/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 966631]
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-X, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/966631 Title: [sandybridge-m-gt2] GPU lockup render.IPEHR: 0x7a03 with Google Maps(WebGL) in Chromium To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/966631/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 966631]
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 fix should be. Hopefully we can land on something soon... Reassigning to me. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/966631 Title: [sandybridge-m-gt2] GPU lockup render.IPEHR: 0x7a03 with Google Maps(WebGL) in Chromium To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/966631/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 899159]
Closing as it works for me and no response for a month. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/899159 Title: [snb-gt2] GPU lockup render.IPEHR: 0x7b009004 (Needs 8.0.2) To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/899159/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 899159]
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 Mesa you're using. (You could use a 32-bit build of glxinfo, though.) I'm guessing that perhaps you accidentally got the (old) 32-bit Mesa installed on your system, rather than the newly built git version you thought you were testing. It's really easy to do. Or I could be wrong and there's an actual bug. :) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/899159 Title: [snb-gt2] GPU lockup render.IPEHR: 0x7b009004 (Needs 8.0.2) To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/899159/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 899159]
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-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/899159 Title: [snb-gt2] GPU lockup render.IPEHR: 0x7b009004 To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/899159/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 899159]
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 kenn...@whitecape.org Date: Sat Feb 18 21:29:29 2012 -0800 i965: Only set Last Render Target Select on the last FB write. Fixes GPU hangs in OilRush, Trine, and Amnesia: The Dark Descent, which all use MRT (multiple render targets). NOTE: This is a candidate for release branches. Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=38720 Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=40059 Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=45216 Reviewed-by: Eric Anholt e...@anholt.net Signed-off-by: Kenneth Graunke kenn...@whitecape.org That patch is also on the 8.0 branch as of today. Your apitrace file no longer hangs my system. Could you confirm? Thanks! Sorry this took so long. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/899159 Title: [snb-gt2] GPU lockup render.IPEHR: 0x7b009004 To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/899159/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 829086]
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 glitches in various apps; feel free to open new bug reports and we'll take a look at them. I think that will be clearer and more useful for everyone than keeping this bug report open. Thanks for your patience. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/829086 Title: Artifacts in 3D with Sandy Bridge To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/829086/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 829086]
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-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/829086 Title: Artifacts in 3D with Sandy Bridge To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/829086/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
