public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Andi Kleen <andi@firstfloor.org>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: chrome crashing the gpu on sandy bridge
Date: Mon, 7 Jul 2014 21:53:48 +0200	[thread overview]
Message-ID: <20140707195348.GI5821@phenom.ffwll.local> (raw)
In-Reply-To: <20140629042703.GG5714@two.firstfloor.org>

On Sun, Jun 29, 2014 at 06:27:03AM +0200, Andi Kleen wrote:
> 
> Hi,
> 
> The current version of chrome reproducibly hangs the GPU on my 
> sandy bridge system when using google maps. The GUI freezes
> and I have to kill chrome from a console to recover.
> 
> Known problem? Crash dump is attached.

Death after a mesa batch, but cursory look at it doesn't ring immediate
bells. Retesting with latest mesa still recommended, recently we've fixed
a pile of snb+ gpu hangs all over in there.
-Daniel
> 
> Kernel 3.15.1 (opensuse version)
> 
> google-chrome-stable-35.0.1916.153-1.x86_64
> 
> OpenGL vendor string: Intel Open Source Technology Center
> OpenGL renderer string: Mesa DRI Intel(R) Sandybridge Desktop 
> OpenGL core profile version string: 3.1 (Core Profile) Mesa 9.2.3
> OpenGL core profile shading language version string: 1.40
> 
> 
> 522626.356259] [drm] stuck on render ring
> [522626.357015] [drm] GPU HANG: ecode 0:0x85fffff9, reason: Ring hung,
> action: reset
> [522626.357015] [drm] GPU hangs can indicate a bug anywhere in the
> entire gfx stack, including userspace.
> [522626.357016] [drm] Please file a _new_ bug report on
> bugs.freedesktop.org against DRI -> DRM/Intel
> [522626.357016] [drm] drm/i915 developers can then reassign to the right
> component if it's not a kernel issue.
> [522626.357016] [drm] The gpu crash dump is required to analyze gpu
> hangs, so please always attach it.
> [522626.357016] [drm] GPU crash dump saved to /sys/class/drm/card0/error
> [522628.356424] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off
> [522638.368877] Watchdog[1565]: segfault at 0 ip 00007f6992e78b4e sp
> 00007f6981fe7670 error 6 in chrome[7f698ee87000+4f39000]
> [522712.515146] Watchdog[1776]: segfault at 0 ip 00007f2963b4bb4e sp
> 00007f2952cba670 error 6 in chrome[7f295fb5a000+4f39000]
> [522724.558268] Watchdog[1930]: segfault at 0 ip 00007f43334a9b4e sp
> 00007f4322618670 error 6 in chrome[7f432f4b8000+4f39000]
> [522728.389633] [drm] stuck on render ring
> [522728.390330] [drm] GPU HANG: ecode 0:0x85fffff9, reason: Ring hung,
> action: reset
> [522730.389771] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off
> 
> 
> 
> -- 
> ak@linux.intel.com -- Speaking for myself only.


> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/intel-gfx


-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch

      reply	other threads:[~2014-07-07 19:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-29  4:27 chrome crashing the gpu on sandy bridge Andi Kleen
2014-07-07 19:53 ` Daniel Vetter [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20140707195348.GI5821@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=andi@firstfloor.org \
    --cc=intel-gfx@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox