<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 --- - xf86-video-intel-2.99 SNA mode gives broken rendering"
href="https://bugs.freedesktop.org/show_bug.cgi?id=72346">72346</a>
</td>
</tr>
<tr>
<th>Assignee</th>
<td>chris@chris-wilson.co.uk
</td>
</tr>
<tr>
<th>Summary</th>
<td>xf86-video-intel-2.99 SNA mode gives broken rendering
</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>tiwai@suse.de
</td>
</tr>
<tr>
<th>Hardware</th>
<td>Other
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Version</th>
<td>git
</td>
</tr>
<tr>
<th>Component</th>
<td>Driver/intel
</td>
</tr>
<tr>
<th>Product</th>
<td>xorg
</td>
</tr></table>
<p>
<div>
<pre>Reported by Jan Engelhardt on openSUSE bugzilla:
<a href="https://bugzilla.novell.com/show_bug.cgi?id=853066">https://bugzilla.novell.com/show_bug.cgi?id=853066</a>
Here is the quote:
Rendering of certain bitmappery is broken: <a href="http://inai.de/mah04467a.mp4">http://inai.de/mah04467a.mp4</a>
So far, I have only been able to observe this with vncviewer.
xorgserver xf86intel mode result
1.13 2.20 default(uxa?) ok
1.13 2.99 default(sna) crap
1.13 2.99 uxa ok
1.14 2.20 default(uxa?) ok
1.14 2.99 default(sna) crap
1.14 2.99 uxa ok
Using either the 2.20 driver, or switching to UXA in 2.99 resolves the issue.
It seems to be independent of the Xorg server version.
I read that SNA stands for SandyBridge New A..something. However, I do have a
Pineview Atom with GMA 3150, so defaulting to SandyBridgey-specific rendering
would seem hazardous.
(in <a href="show_bug.cgi?id=72346#c12">comment #12</a>)
In the video, I used the Window Rollup feature of the local window manager
(xfce) to roll the VNC window up, and then down again, so as to cause a repaint
of the local X window, nothing more. Moving windows inside the VNC is also one
way to cause remote repaints and subsequently local repaints, which is also
shown.
A potential cure seems to be to reinitialize the rendering pipes, for example
by turning off at least one (either LVDS1 or VGA1) and then going back to the
desired setup:
xrandr --output LVDS1 --off
xrandr --auto
***
The problem still happens with git 2.99.906-78-g6c37ab3ddc59. It's PineView
x86-64.
Interestingly, we couldn't reproduce the issue here with another machine with
the same chip.</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>