<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 --- - [Baytrail-M Regression Bisected] testdisplay cause "Call Trace""
href="https://bugs.freedesktop.org/show_bug.cgi?id=69808">69808</a>
</td>
</tr>
<tr>
<th>CC</th>
<td>intel-gfx-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Assignee</th>
<td>jbarnes@virtuousgeek.org
</td>
</tr>
<tr>
<th>Summary</th>
<td>[Baytrail-M Regression Bisected] testdisplay cause "Call Trace"
</td>
</tr>
<tr>
<th>QA Contact</th>
<td>intel-gfx-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Severity</th>
<td>major
</td>
</tr>
<tr>
<th>Classification</th>
<td>Unclassified
</td>
</tr>
<tr>
<th>OS</th>
<td>All
</td>
</tr>
<tr>
<th>Reporter</th>
<td>yangweix.shui@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=86557" name="attach_86557" title="dmesg: testdisplay cause call trace">attachment 86557</a> <a href="attachment.cgi?id=86557&action=edit" title="dmesg: testdisplay cause call trace">[details]</a></span>
dmesg: testdisplay cause call trace
Description:
-------------------------
After running testdisplay cases(include -a,-d,-p,-t,-f), there's call trace
come up in console. No matter we use which kind pipe(VGA or eDP), each of them
exists. It's a regression and been bisected.
Bisect result:
-------------------------
f1f644dc66cbaf5a4c7dcde683361536b41885b9 is the first bad commit
commit f1f644dc66cbaf5a4c7dcde683361536b41885b9
Author: Jesse Barnes <<a href="mailto:jbarnes@virtuousgeek.org">jbarnes@virtuousgeek.org</a>>
Date: Thu Jun 27 00:39:25 2013 +0300
drm/i915: get mode clock when reading the pipe config v9
We need this for comparing modes between configuration changes.
The tricky part is to allow us to reuse the new get_clock stuff to
recover the lvds clock on gen2/3 when neither the vbt has an lvds mode
nor the panel a (useful) EDID.
v2: try harder to calulate non-simple pixel clocks (Daniel)
call get_clock after getting the encoder config, needed for pixel
multiply
(Jesse)
v3: drop get_clock now that the pixel_multiply has been moved into
get_pipe_config
v4: re-add get_clock; we need to get the pixel multiplier in the
encoder, so need to calculate the clock value after the encoder's
get_config is called
v5: drop hsw clock_get, still needs to be written
Reproduce Steps:
------------------------
1. boot up machine
2. run testdisplay
3. checkout dmesg</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>
</ul>
</body>
</html>