<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 - MinnowMAX jumbled display with i915 via micro-HDMI"
href="https://bugs.freedesktop.org/show_bug.cgi?id=100700">100700</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>MinnowMAX jumbled display with i915 via micro-HDMI
</td>
</tr>
<tr>
<th>Product</th>
<td>DRI
</td>
</tr>
<tr>
<th>Version</th>
<td>DRI git
</td>
</tr>
<tr>
<th>Hardware</th>
<td>IA64 (Itanium)
</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>jennifer.ito@windriver.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></table>
<p>
<div>
<pre>Created <span class=""><a href="attachment.cgi?id=130874" name="attach_130874" title="Files used to build testcase in WRL8 environment.">attachment 130874</a> <a href="attachment.cgi?id=130874&action=edit" title="Files used to build testcase in WRL8 environment.">[details]</a></span>
Files used to build testcase in WRL8 environment.
This was originally found with a Wind River Linux 8 system. I have attached a
build.tar.gz file that was used to build the testcase. If the ability to build
a WRL8 system exists for whoever is assigned to this bug, please feel free to
contact me for information on how to build. While the testcase should be able
to be run on other versions of Linux, it may be difficult to build due to
dependencies.
In order to prepare for this bugzilla report, the latest drm-tip was used.
Once you have the board booted, perform the following steps to see the problem.
1. setting environment on target.
a. login target and run "export DISPLAY=:0"
b. ps -ef | grep X
root 257 228 0 09:07 ? 00:00:00 xinit /etc/X11/xinit/xinitrc -- /usr/bin/X :0
-auth /.serverauth.228
root 258 257 0 09:07 tty2 00:00:00 /usr/bin/X :0 -auth /.serverauth.228
root 355 297 0 09:36 ttyS0 00:00:00 grep X
c. copy /.serverauth.228 to /root/.Xauthority
2. running xwininfo (such as xwininfo -root -tree).
3. observing testcase to see if distorted screen occur when second widget
shows. This should show the behavior in the attached screenshot
(JumbledGraphics.png).
I have attached minnowboard.tar.gz which includes some log files collected on
the target.
root@localhost:~# uname -r
4.11.0-rc4
root@localhost:~# uname -m
x86_64
root@localhost:~# cat /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 55
model name : Intel(R) Atom(TM) CPU E3826 @ 1.46GHz
stepping : 9
cpu MHz : 535.095
cache size : 512 KB
physical id : 0
siblings : 2
core id : 0
cpu cores : 2
apicid : 0
initial apicid : 0
fpu : yes
fpu_exception : yes
cpuid level : 11
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36
clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syt
bugs :
bogomips : 2932.60
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:
processor : 1
vendor_id : GenuineIntel
cpu family : 6
model : 55
model name : Intel(R) Atom(TM) CPU E3826 @ 1.46GHz
stepping : 9
cpu MHz : 535.990
cache size : 512 KB
physical id : 0
siblings : 2
core id : 2
cpu cores : 2
apicid : 4
initial apicid : 4
fpu : yes
fpu_exception : yes
cpuid level : 11
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36
clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syt
bugs :
bogomips : 2943.00
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are on the CC list for the bug.</li>
<li>You are the assignee for the bug.</li>
<li>You are the QA Contact for the bug.</li>
</ul>
</body>
</html>