[Bug 88700] Portal 2 FPS goes below 5 in several places

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Thu Mar 5 03:07:49 PST 2015


https://bugs.freedesktop.org/show_bug.cgi?id=88700

Samuel Iglesias <siglesias at igalia.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |siglesias at igalia.com

--- Comment #7 from Samuel Iglesias <siglesias at igalia.com> ---
Created attachment 114024
  --> https://bugs.freedesktop.org/attachment.cgi?id=114024&action=edit
/sys/class/drm/card0/error

OK, then I reproduced it successfully on my SNB laptop. In my case, GPU hang
happens after five minutes of "Portal 2" gameplay (executed through Steam).

I attach /sys/class/drm/card0/error file.

System info:

glxinfo:

OpenGL vendor string: Intel Open Source Technology Center
OpenGL renderer string: Mesa DRI Intel(R) Sandybridge Mobile 
OpenGL core profile version string: 3.3 (Core Profile) Mesa 10.6.0-devel
(git-073a5d2)
OpenGL core profile shading language version string: 3.30

$ uname -a
Linux fourier 3.14-2-amd64 #1 SMP Debian 3.14.15-2 (2014-08-09) x86_64
GNU/Linux

/var/log/messages output. Google Chrome was also running. Because of the GPU
hang, Chrome lost its GL context and its CPU consumption went to 100%. I would
say that this is duplicate of bug 89279 but I am not sure as bug 89279 report
doesn't explain what Steam was doing.

[...]
Mar  4 13:59:58 fourier kernel: [22628.700115] [drm] stuck on render ring
Mar  4 13:59:58 fourier kernel: [22628.700119] [drm] stuck on blitter ring
Mar  4 13:59:58 fourier kernel: [22628.700120] [drm] GPU crash dump saved to
/sys/class/drm/card0/error
Mar  4 13:59:58 fourier kernel: [22628.700121] [drm] GPU hangs can indicate a
bug anywhere in the entire gfx stack, including userspace.
Mar  4 13:59:58 fourier kernel: [22628.700122] [drm] Please file a _new_ bug
report on bugs.freedesktop.org against DRI -> DRM/Intel
Mar  4 13:59:58 fourier kernel: [22628.700122] [drm] drm/i915 developers can
then reassign to the right component if it's not a kernel issue.
Mar  4 13:59:58 fourier kernel: [22628.700123] [drm] The gpu crash dump is
required to analyze gpu hangs, so please always attach it.
Mar  4 13:59:58 fourier google-chrome.desktop[7447]:
[7524:7524:0304/125958:ERROR:gles2_cmd_decoder.cc(10030)] Onscreen context lost
via ARB/EXT_robustness. Reset status = GL_INNOCENT_CONTEXT_RESET_KHR
Mar  4 13:59:58 fourier google-chrome.desktop[7447]:
[7524:7524:0304/125958:ERROR:gles2_cmd_decoder.cc(3200)]   GLES2DecoderImpl:
Context lost during MakeCurrent.
Mar  4 13:59:58 fourier google-chrome.desktop[7447]:
[7524:7524:0304/125958:ERROR:gles2_cmd_decoder.cc(3200)]   GLES2DecoderImpl:
Context lost during MakeCurrent.
Mar  4 13:59:58 fourier google-chrome.desktop[7447]:
[7524:7524:0304/125958:ERROR:gles2_cmd_decoder.cc(3200)]   GLES2DecoderImpl:
Context lost during MakeCurrent.
Mar  4 13:59:58 fourier google-chrome.desktop[7447]:
[7524:7524:0304/125958:ERROR:gles2_cmd_decoder.cc(3200)]   GLES2DecoderImpl:
Context lost during MakeCurrent.
Mar  4 13:59:58 fourier google-chrome.desktop[7447]:
[7524:7524:0304/125958:ERROR:gles2_cmd_decoder.cc(10030)] Onscreen context lost
via ARB/EXT_robustness. Reset status = GL_INNOCENT_CONTEXT_RESET_KHR
Mar  4 13:59:58 fourier google-chrome.desktop[7447]:
[7524:7524:0304/125958:ERROR:gles2_cmd_decoder.cc(3200)]   GLES2DecoderImpl:
Context lost during MakeCurrent.
[...]

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/intel-3d-bugs/attachments/20150305/250feaf1/attachment-0001.html>


More information about the intel-3d-bugs mailing list