<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 - vblank wait timed out on crtc 0 after screen lock on Dell Latitude e6220"
href="https://bugs.freedesktop.org/show_bug.cgi?id=100992">100992</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>vblank wait timed out on crtc 0 after screen lock on Dell Latitude e6220
</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>thomas@junovagen.se
</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>After a screen lock, the screen hangs, with the following stack dump in dmesg:
[46276.425098] WARNING: CPU: 0 PID: 4082 at
/build/linux-FyIZxz/linux-4.4.0/drivers/gpu/d
[46276.425103] vblank wait timed out on crtc 0
[46276.425107] Modules linked in: rfcomm arc4 md4 nls_utf8 cifs fscache bnep
dell_wmi spa_smm_hwmon wl(POE) snd_hda_codec_hdmi irqbypass crct10dif_pclmul
crc32_pclmul ghash_clmulr cryptd snd_hda_intel uvcvideo cdc_ncm snd_hda_codec
usbnet videobuf2_vmalloc mii videoboydev media btrtl btbcm snd_seq_midi btintel
snd_seq_midi_event bluetooth snd_rawmidi inp
[46276.425219] dell_smo8800 mac_hid parport_pc ppdev lp parport autofs4
hid_generic usbhpci libahci sdhci ptp pps_core wmi fjes video
[46276.425266] CPU: 0 PID: 4082 Comm: Xorg Tainted: P W OE
4.4.0-77-generic #98
[46276.425270] Hardware name: Dell Inc. Latitude E6220/0R97MN, BIOS A12
06/28/2013
[46276.425274] 0000000000000286 0000000070ffd816 ffff8800c385bb08
ffffffff813f8493
[46276.425282] ffff8800c385bb50 ffffffffc009db38 ffff8800c385bb40
ffffffff81081302
[46276.425288] ffff8800356c4000 0000000000000000 0000000000000000
000000000002cc9d
[46276.425295] Call Trace:
[46276.425307] [<ffffffff813f8493>] dump_stack+0x63/0x90
[46276.425318] [<ffffffff81081302>] warn_slowpath_common+0x82/0xc0
[46276.425325] [<ffffffff8108139c>] warn_slowpath_fmt+0x5c/0x80
[46276.425337] [<ffffffff810c3da5>] ? finish_wait+0x55/0x70
[46276.425375] [<ffffffffc006d2b5>] drm_wait_one_vblank+0x1b5/0x1c0 [drm]
[46276.425386] [<ffffffff810c4240>] ? wake_atomic_t_function+0x60/0x60
[46276.425471] [<ffffffffc0235e3a>] intel_atomic_commit+0x43a/0x6f0 [i915]
[46276.425519] [<ffffffffc0087037>] drm_atomic_commit+0x37/0x60 [drm]
[46276.425545] [<ffffffffc018fdc6>] drm_atomic_helper_set_config+0x76/0xb0
[drm_kms_help
[46276.425581] [<ffffffffc0075e12>] drm_mode_set_config_internal+0x62/0x100
[drm]
[46276.425614] [<ffffffffc007a46c>] drm_mode_setcrtc+0x3cc/0x4f0 [drm]
[46276.425642] [<ffffffffc006b722>] drm_ioctl+0x152/0x540 [drm]
[46276.425672] [<ffffffffc007a0a0>] ? drm_mode_setplane+0x1b0/0x1b0 [drm]
[46276.425681] [<ffffffff81222c6f>] do_vfs_ioctl+0x29f/0x490
[46276.425689] [<ffffffff8108e5a1>] ? __set_task_blocked+0x41/0xa0
[46276.425696] [<ffffffff81090f36>] ? __set_current_blocked+0x36/0x60
[46276.425702] [<ffffffff81222ed9>] SyS_ioctl+0x79/0x90
[46276.425712] [<ffffffff8183b972>] entry_SYSCALL_64_fastpath+0x16/0x71
[46276.425717] ---[ end trace 6929fd69fa421ae3 ]---
I've seen multiple bug reports with similar effect, but the workaround has been
"video=SVIDEO-1:d" as boot parameters, but this does not affect my case. Also,
the other reports, such as <a class="bz_bug_link
bz_status_REOPENED "
title="REOPENED - [i9xx TV][BISECT] vblank wait timeout on crtc"
href="show_bug.cgi?id=93782">bug 93782</a>, includes 'intel_tv_detect' which mine
does not.
I originally filed this
here:<a href="https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1689651">https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1689651</a>, where I've
filed many logs.
But will try to build drm-tip and make sure it still is there (although bug
93782 seems to indicate that it is), and report back here.</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>
<li>You are on the CC list for the bug.</li>
</ul>
</body>
</html>