<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW "
title="NEW - [BYT] flickering is seen after running benchmark synmark [regression]"
href="https://bugs.freedesktop.org/show_bug.cgi?id=98036">98036</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>[BYT] flickering is seen after running benchmark synmark [regression]
</td>
</tr>
<tr>
<th>Product</th>
<td>DRI
</td>
</tr>
<tr>
<th>Version</th>
<td>XOrg git
</td>
</tr>
<tr>
<th>Hardware</th>
<td>x86-64 (AMD64)
</td>
</tr>
<tr>
<th>OS</th>
<td>Linux (All)
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Severity</th>
<td>normal
</td>
</tr>
<tr>
<th>Priority</th>
<td>medium
</td>
</tr>
<tr>
<th>Component</th>
<td>DRM/Intel
</td>
</tr>
<tr>
<th>Assignee</th>
<td>intel-gfx-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>luis.botello.ortega@intel.com
</td>
</tr>
<tr>
<th>QA Contact</th>
<td>intel-gfx-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>CC</th>
<td>intel-gfx-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>i915 platform</th>
<td>BYT
</td>
</tr>
<tr>
<th>i915 features</th>
<td>display/HDMI
</td>
</tr></table>
<p>
<div>
<pre>Created <span class=""><a href="attachment.cgi?id=126983" name="attach_126983" title="dmesg">attachment 126983</a> <a href="attachment.cgi?id=126983&action=edit" title="dmesg">[details]</a></span>
dmesg
Description:
========================================================
After running synmark flickering is seen on BYT.
Software Configuration:
========================================================
Kernel version : 4.8.0-rc2bisect-jira-2efb813+
Linux distribution : Ubuntu 16.04 LTS
Architecture : 64-bit
Mesa version : 12.0.0 (git-8b06176
xf86-video-intel version : Not found
Xorg-Xserver version : 1.18.99.2
DRM version : 2.4.70
VAAPI version : Intel i965 driver for Intel(R) Bay Trail -
1.7.3.pre1 (1.7.0-136-g36fbd81)
Cairo version : 1.15.2
Intel GPU Tools version : Tag [intel-gpu-tools-1.16-22-g200237a] /
Commit [200237a]
Kernel driver in use : i915
Hardware acceleration : Enabled
Bios revision : 1.30
Bios release date : 03/24/2014
KSC revision : 1.10
Hardware Config:
==========================================================
Platform : BYT-M (Toshiba)
Motherboard model : Satellite C55t-A
Motherboard type : Portable PC Notebook
Motherboard manufacturer : TOSHIBA
CPU family : Atom
CPU information : Intel(R) Celeron(R) CPU N2820 @ 2.13GHz
GPU Card : Intel Corporation Atom Processor
Z36xxx/Z37xxx Series Graphics & Display (rev 0c) (prog-if 00 [VGA controller])
Memory ram : 4 GB
Maximum memory ram allowed : 8 GB
Display resolution : 1920x1200
CPU thread : 2
CPU core : 2
Socket : None
Signature : Type 0, Family 6, Model 55, Stepping 3
Hard drive capacity : 465GiB (500GB)
Regression:
===============================================
2efb813d5388e18255c54afac77bd91acd586908 is the first bad commit
commit 2efb813d5388e18255c54afac77bd91acd586908
Author: Chris Wilson <<a href="mailto:chris@chris-wilson.co.uk">chris@chris-wilson.co.uk</a>>
Date: Thu Aug 18 17:17:06 2016 +0100
drm/i915: Fallback to using unmappable memory for scanout
The existing ABI says that scanouts are pinned into the mappable region
so that legacy clients (e.g. old Xorg or plymouthd) can write directly
into the scanout through a GTT mapping. However if the surface does not
fit into the mappable region, we are better off just trying to fit it
anywhere and hoping for the best. (Any userspace that is capable of
using ginormous scanouts is also likely not to rely on pure GTT
updates.) With the partial vma fault support, we are no longer
restricted to only using scanouts that we can pin (though it is still
preferred for performance reasons and for powersaving features like
FBC).
v2: Skip fence pinning when not mappable.
v3: Add a comment to explain the possible ramifications of not being
able to use fences for unmappable scanouts.
v4: Rebase to skip over some local patches
v5: Rebase to defer until after we have unmappable GTT fault support
Signed-off-by: Chris Wilson <<a href="mailto:chris@chris-wilson.co.uk">chris@chris-wilson.co.uk</a>>
Cc: Deepak S <<a href="mailto:deepak.s@linux.intel.com">deepak.s@linux.intel.com</a>>
Cc: Damien Lespiau <<a href="mailto:damien.lespiau@intel.com">damien.lespiau@intel.com</a>>
Cc: Daniel Vetter <<a href="mailto:daniel.vetter@ffwll.ch">daniel.vetter@ffwll.ch</a>>
Cc: Jani Nikula <<a href="mailto:jani.nikula@linux.intel.com">jani.nikula@linux.intel.com</a>>
Reviewed-by: Joonas Lahtinen <<a href="mailto:joonas.lahtinen@linux.intel.com">joonas.lahtinen@linux.intel.com</a>>
Link:
<a href="http://patchwork.freedesktop.org/patch/msgid/20160818161718.27187-27-chris@chris-wilson.co.uk">http://patchwork.freedesktop.org/patch/msgid/20160818161718.27187-27-chris@chris-wilson.co.uk</a>
:040000 040000 96d2cab693321fa8be700eb9f9db8f220819fa36
5d834a722b30204e059044af28d0230a784f40f9 M drivers
Steps to reproduce:
==========================================================
-- Download SYnmark Benchamrk
<a href="http://benchsrv.fi.intel.com/archive/benchmarks/SynMark2-7.0.tar.gz">http://benchsrv.fi.intel.com/archive/benchmarks/SynMark2-7.0.tar.gz</a>
-- Open a terminal
-- run synmark
Attachments:
=============================================
dmesg
Xorg.log</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>