<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 --- - [ALL bisected]I-G-T/testdisplay causes call trace while setting up customized timing"
href="https://bugs.freedesktop.org/show_bug.cgi?id=65442">65442</a>
</td>
</tr>
<tr>
<th>Assignee</th>
<td>intel-gfx-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Summary</th>
<td>[ALL bisected]I-G-T/testdisplay causes call trace while setting up customized timing
</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>cancan.feng@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>System Environment:
--------------------------------------------
Kernel: (drm-intel-next-queued)d7697eea3eec74c561d12887d892c53ac4380c00
Some additional commit info:
Author: Daniel Vetter <<a href="mailto:daniel.vetter@ffwll.ch">daniel.vetter@ffwll.ch</a>>
Date: Sun Jun 2 17:23:01 2013 +0200
drm/i915: optimize vblank waits in set_base_atomic
Bug detail Description:
--------------------------------------------
I-G-T testdisplay causes call trace while setting up customized timing. This
issue happens on HSW, IVB, SNB, ILK.
[ 32.373406] Call Trace:
[ 32.373427] [<ffffffff816de142>] ? dump_stack+0xd/0x17
[ 32.373461] [<ffffffff8102c67d>] ? warn_slowpath_common+0x5f/0x77
[ 32.373498] [<ffffffff8102c72d>] ? warn_slowpath_fmt+0x45/0x4a
[ 32.373539] [<ffffffffa0088edd>] ? intel_modeset_check_state+0x904/0x94b
[i915]
[ 32.373587] [<ffffffffa0088f94>] ? intel_set_mode+0x1d/0x27 [i915]
[ 32.373635] [<ffffffffa0089521>] ? intel_crtc_set_config+0x583/0x73b [i915]
[ 32.373688] [<ffffffffa0013cc1>] ? drm_mode_set_config_internal+0x19/0x40
[drm]
[ 32.373751] [<ffffffffa0015925>] ? drm_mode_setcrtc+0x437/0x4e8 [drm]
[ 32.373812] [<ffffffffa000946c>] ? drm_ioctl+0x290/0x3b5 [drm]
[ 32.373862] [<ffffffffa00154ee>] ? drm_mode_setplane+0x30f/0x30f [drm]
[ 32.373901] [<ffffffff816e1b31>] ? __schedule+0x60a/0x751
[ 32.373935] [<ffffffff8104b125>] ? __wake_up+0x35/0x46
[ 32.373968] [<ffffffff810dc342>] ? vfs_ioctl+0x1e/0x31
[ 32.373999] [<ffffffff810dcb71>] ? do_vfs_ioctl+0x3e9/0x42b
[ 32.374033] [<ffffffff810dcc01>] ? SyS_ioctl+0x4e/0x7d
[ 32.374065] [<ffffffff816e7e12>] ? system_call_fastpath+0x16/0x1b
[ 32.374101] ---[ end trace ee545d65293e034b ]---
I attach the whole dmesg info in the attachment, and this is a regression, here
is the bisect info:
Bisect result:
--------------------------------------------
045ac3b5629d9711531a408e92f9074db6afe7ce is the first bad commit
commit 045ac3b5629d9711531a408e92f9074db6afe7ce
Author: Jesse Barnes <<a href="mailto:jbarnes@virtuousgeek.org">jbarnes@virtuousgeek.org</a>>
Date: Tue May 14 17:08:26 2013 -0700
drm/i915: add encoder get_config function v5
We can use this for fetching encoder specific pipe_config state, like
mode flags, adjusted clock, etc.
Just used for mode flags atm, so we can check the pipe config state at
mode set time.
v2: get_config when checking hw state too
v3: fix DVO and LVDS mode flags (Ville)
get SDVO DTD for flag fetch (Ville)
v4: use input timings (Ville)
correct command used (Ville)
remove gen4 check (Ville)
v5: get DDI flag config too
Signed-off-by: Jesse Barnes <<a href="mailto:jbarnes@virtuousgeek.org">jbarnes@virtuousgeek.org</a>>
Reviewed-by: Ville Syrjälä <<a href="mailto:ville.syrjala@linux.intel.com">ville.syrjala@linux.intel.com</a>> (v4)
Tested-by: Paulo Zanoni <<a href="mailto:przanoni@gmail.com">przanoni@gmail.com</a>> (the new hsw ddi stuff)
Signed-off-by: Daniel Vetter <<a href="mailto:daniel.vetter@ffwll.ch">daniel.vetter@ffwll.ch</a>>
:040000 040000 b2b8a7612a37028fb4ff2f62e372b70e9ce5179a
7b4bf7d42a2d1ce673ea2f405035e4c9c7dfe4a8
M drivers
Reproduce step:
--------------------------------------------
1. booting up machine
2. ./testdisplay -f 38.25,800,832,912,1024,600,603,607,624(or other)
3. dmesg | grep "Call Trace"</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 the assignee for the bug.</li>
</ul>
</body>
</html>