<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Priority</th>
<td>high
</td>
</tr>
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW "
title="NEW --- - [PNV/GM45 Bisected]glxgears segfault"
href="https://bugs.freedesktop.org/show_bug.cgi?id=65845">65845</a>
</td>
</tr>
<tr>
<th>CC</th>
<td>xunx.fang@intel.com, yangweix.shui@intel.com
</td>
</tr>
<tr>
<th>Assignee</th>
<td>mika.kuoppala@intel.com
</td>
</tr>
<tr>
<th>Summary</th>
<td>[PNV/GM45 Bisected]glxgears segfault
</td>
</tr>
<tr>
<th>QA Contact</th>
<td>intel-gfx-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Severity</th>
<td>major
</td>
</tr>
<tr>
<th>Classification</th>
<td>Unclassified
</td>
</tr>
<tr>
<th>OS</th>
<td>Linux (All)
</td>
</tr>
<tr>
<th>Reporter</th>
<td>huax.lu@intel.com
</td>
</tr>
<tr>
<th>Hardware</th>
<td>All
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Version</th>
<td>unspecified
</td>
</tr>
<tr>
<th>Component</th>
<td>DRM/Intel
</td>
</tr>
<tr>
<th>Product</th>
<td>DRI
</td>
</tr></table>
<p>
<div>
<pre>Created <span class=""><a href="attachment.cgi?id=80931" name="attach_80931" title="dmesg">attachment 80931</a> <a href="attachment.cgi?id=80931&action=edit" title="dmesg">[details]</a></span>
dmesg
System Environment:
--------------------------
Platform: Pineview/GM45
Kernel: (drm-intel-next-queued)cab8b5862acd55019fbeede6940d1a601912d6b8
Bug detailed description:
-------------------------
It segfault on Pineview and GM45 with drm-intel-next-queued kernel.It works
well on drm-intel-fixes kernel.
Bisect shows:a89cdd3cfcd66d932d4ae2617c5e89279515f14d is the first bad commit.
commit a89cdd3cfcd66d932d4ae2617c5e89279515f14d
Author: Mika Kuoppala <<a href="mailto:mika.kuoppala@linux.intel.com">mika.kuoppala@linux.intel.com</a>>
AuthorDate: Wed Jun 12 12:35:34 2013 +0300
Commit: Daniel Vetter <<a href="mailto:daniel.vetter@ffwll.ch">daniel.vetter@ffwll.ch</a>>
CommitDate: Thu Jun 13 17:42:18 2013 +0200
drm/i915: refuse to submit more batchbuffers from guilty context
If context has recently submitted a faulty batchbuffers guilty of
gpu hang and decides to keep submitting more crap, ban it permanently.
Note: This is just a refinment of the existing policy to declare the
gpu wedged when it's hanging too often. We have that in place to
increase the odds of a system surviving gpu hang storms (and so
getting a useful bug report with the error state).
With this patch here we reduce the risk to take down unrelated
applications, since especially modern compositors tend to die when
mesa can't submit batches any more. So for the somewhat common case of
a specific gl workload causing a gpu hang flurry we should now have
less grumpy users since we don't take down their entire deskopt
enviroment any more.
v2: Store guilty ban status bool in gpu_error instead of pointers
that might become danling before hang is declared.
v3: Use return value for banned status instead of stashing state
into gpu_error (Chris Wilson)
Signed-off-by: Mika Kuoppala <<a href="mailto:mika.kuoppala@intel.com">mika.kuoppala@intel.com</a>>
Reviewed-by: Chris Wilson <<a href="mailto:chris@chris-wilson.co.uk">chris@chris-wilson.co.uk</a>>
[danvet: Added note to commit message to explain why we want this,
which addresses a concern Ben raised.]
Signed-off-by: Daniel Vetter <<a href="mailto:daniel.vetter@ffwll.ch">daniel.vetter@ffwll.ch</a>>
output:
Running synchronized to the vertical refresh. The framerate should be
approximately the same as the monitor refresh rate.
Segmentation fault (core dumped)
Reproduce steps:
----------------
1. xinit
2. glxgears</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
</ul>
</body>
</html>