<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED FIXED - [BDW/BYT Bisected semaphores] igt/gem_gtt_hog fails, gem_reset_stats and more"
href="https://bugs.freedesktop.org/show_bug.cgi?id=81209#c28">Comment # 28</a>
on <a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED FIXED - [BDW/BYT Bisected semaphores] igt/gem_gtt_hog fails, gem_reset_stats and more"
href="https://bugs.freedesktop.org/show_bug.cgi?id=81209">bug 81209</a>
from <span class="vcard"><a class="email" href="mailto:yann.argotti@intel.com" title="yann <yann.argotti@intel.com>"> <span class="fn">yann</span></a>
</span></b>
<pre>(In reply to Chris Wilson from <a href="show_bug.cgi?id=81209#c27">comment #27</a>)
<span class="quote">> commit 9607ae79710afb453173b90d5bf564788a6e09b1
> Author: Chris Wilson <<a href="mailto:chris@chris-wilson.co.uk">chris@chris-wilson.co.uk</a>>
> Date: Thu Nov 24 09:47:52 2016 +0000
>
> drm/i915/debugfs: Increment return value of gt.next_seqno
>
> The i915_next_seqno read value is to be the next seqno used by the
> kernel. However, in the conversion to atomics ops for gt.next_seqno, in
> commit 28176ef4cfa5 ("drm/i915: Reserve space in the global seqno during
> request allocation"), this was changed from a post-increment to a
> pre-increment. This increment was missed from the value reported by
> debugfs, so in effect it was reporting the current seqno (last
> assigned), not the next seqno.</span >
Elio, please re-test and confirm that the issue you posted here is fixed then.
Moreover, don't forget to create new bug when defect cause is different.</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>