<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Priority</th>
<td>medium
</td>
</tr>
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW "
title="NEW --- - [IVB/HSW]Subcases negative-reloc-lut and negative-reloc fail"
href="https://bugs.freedesktop.org/show_bug.cgi?id=78876">78876</a>
</td>
</tr>
<tr>
<th>CC</th>
<td>intel-gfx-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Assignee</th>
<td>intel-gfx-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Summary</th>
<td>[IVB/HSW]Subcases negative-reloc-lut and negative-reloc fail
</td>
</tr>
<tr>
<th>QA Contact</th>
<td>intel-gfx-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Severity</th>
<td>normal
</td>
</tr>
<tr>
<th>Classification</th>
<td>Unclassified
</td>
</tr>
<tr>
<th>OS</th>
<td>All
</td>
</tr>
<tr>
<th>Reporter</th>
<td>jinxianx.guo@intel.com
</td>
</tr>
<tr>
<th>Hardware</th>
<td>Other
</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=99293" name="attach_99293" title="dmesg">attachment 99293</a> <a href="attachment.cgi?id=99293&action=edit" title="dmesg">[details]</a></span>
dmesg
==System Environment==
--------------------------
Regression: No.
It's new case
Non-working platforms: IVB HSW
==kernel==
--------------------------
-nightly: f79ba79cf037eea9ee757ad37730b00f43d5ef80 (fails)
-queued: d3b448d9917a3d6531e499d88bfb13ea5e31e4ad (fails)
Author: Chris Wilson <<a href="mailto:chris@chris-wilson.co.uk">chris@chris-wilson.co.uk</a>>
Date: Fri May 16 18:59:00 2014 +0100
drm/i915: Only unpin the default ctx object if it exists
Since commit 691e6415c891b8b2b082a120b896b443531c4d45
Author: Chris Wilson <<a href="mailto:chris@chris-wilson.co.uk">chris@chris-wilson.co.uk</a>>
Date: Wed Apr 9 09:07:36 2014 +0100
drm/i915: Always use kref tracking for all contexts.
we have contexts everywhere, and so we must be careful to distinguish
fake contexts, which do not have an associated bo, and real ones, which
do. In particular, we now need to be careful not to dereference NULL
pointers.
This is one such example, as the commit highlighted above failed to move
the unpinning of the default ctx object into the real-context-only
branch.
Reported-by: Daniel Vetter <<a href="mailto:daniel.vetter@ffwll.ch">daniel.vetter@ffwll.ch</a>>
Bugzilla: <a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED FIXED - [regression] module reload Oopses all over the place"
href="show_bug.cgi?id=78792">https://bugs.freedesktop.org/show_bug.cgi?id=78792</a>
Signed-off-by: Chris Wilson <<a href="mailto:chris@chris-wilson.co.uk">chris@chris-wilson.co.uk</a>>
Cc: Daniel Vetter <<a href="mailto:daniel.vetter@ffwll.ch">daniel.vetter@ffwll.ch</a>>
Cc: Ben Widawsky <<a href="mailto:benjamin.widawsky@intel.com">benjamin.widawsky@intel.com</a>>
Cc: Mika Kuoppala <<a href="mailto:mika.kuoppala@intel.com">mika.kuoppala@intel.com</a>>
Cc: Jani Nikula <<a href="mailto:jani.nikula@intel.com">jani.nikula@intel.com</a>>
Signed-off-by: Daniel Vetter <<a href="mailto:daniel.vetter@ffwll.ch">daniel.vetter@ffwll.ch</a>>
-fixes: e95a2f7509f5219177d6821a0a8754f93892ca56 (fails)
Author: Ville Syrjälä <<a href="mailto:ville.syrjala@linux.intel.com">ville.syrjala@linux.intel.com</a>>
Date: Thu May 8 15:09:19 2014 +0300
drm/i915: Increase WM memory latency values on SNB
On SNB the BIOS provided WM memory latency values seem insufficient to
handle high resolution displays.
In this particular case the display mode was a 2560x1440@60Hz, which
makes the pixel clock 241.5 MHz. It was empirically found that a memory
latency value if 1.2 usec is enough to avoid underruns, whereas the BIOS
provided value of 0.7 usec was clearly too low. Incidentally 1.2 usec
is what the typical BIOS provided values are on IVB systems.
Increase the WM memory latency values to at least 1.2 usec on SNB.
Hopefully this won't have a significant effect on power consumption.
v2: Increase the latency values regardless of the pixel clock
Cc: Robert N <<a href="mailto:crshman@gmail.com">crshman@gmail.com</a>>
Bugzilla: <a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED FIXED - [snb dp hotplug] Pipe B, PCH transcoder B FIFO underrun"
href="show_bug.cgi?id=70254">https://bugs.freedesktop.org/show_bug.cgi?id=70254</a>
Tested-by: Robert Navarro <<a href="mailto:crshman@gmail.com">crshman@gmail.com</a>>
Tested-by: Vitaly Minko <<a href="mailto:vitaly.minko@gmail.com">vitaly.minko@gmail.com</a>>
Cc: <a href="mailto:stable@vger.kernel.org">stable@vger.kernel.org</a>
Signed-off-by: Ville Syrjälä <<a href="mailto:ville.syrjala@linux.intel.com">ville.syrjala@linux.intel.com</a>>
Signed-off-by: Jani Nikula <<a href="mailto:jani.nikula@intel.com">jani.nikula@intel.com</a>>
==Bug detailed description==
-----------------------------
Subcases negative-reloc-lut and negative-reloc fail
Output:
./gem_bad_reloc --run-subtest negative-reloc-lut
IGT-Version: 1.6-g252d115 (x86_64) (Linux:
3.15.0-rc3_drm-intel-fixes_e95a2f_20140519_debug+ x86_64)
Found offset 13033472 for 4k batch
Test assertion failure function negative_reloc, file gem_bad_reloc.c:99:
Last errno: 0, Success
Failed assertion: buf[2 + i] < gtt_max
Subtest negative-reloc-lut: FAIL
==Reproduce steps==
----------------------------
1. ./gem_bad_reloc --run-subtest negative-reloc-lut</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
<li>You are on the CC list for the bug.</li>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>