[Bug 93782] [i9xx TV][BISECT] vblank wait timeout on crtc

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Sun Sep 25 19:17:18 UTC 2016


https://bugs.freedesktop.org/show_bug.cgi?id=93782

--- Comment #20 from Till Schäfer <till2.schaefer at uni-dortmund.de> ---
I am also seeing this dmesg warning when switching tty. However, it does not
only be related to the kernel. I have used the 4.4.6 kernel with xorg server
1.17.4, mesa 11.0.6 and intel driver 2.99.917 without any issues (I am not 100%
sure that this does not happened before, but i look quite regular at the dmesg
and do not remember to see a stack trace popping up. 

Now after updating to xorg server 1.18.4 with mesa 12.0.1 and intel driver
2.99.917_p20160621-r1 (snapshot for gentoo) the vblank timeout occurs. 

Furthermore, i have notices some display freezes (programs seem to react, but
the display is not updated). I do not know if this is related. 

I have then also tested kernels 4.4.21 and 4.7.5, both show the vblank warning. 

Hardware: I am also using the Dell D630 Laptop with Intel 965GM graphics.



[   55.375183] ------------[ cut here ]------------
[   55.375205] WARNING: CPU: 1 PID: 3609 at drivers/gpu/drm/drm_irq.c:1318
drm_wait_one_vblank+0x131/0x180
[   55.375209] vblank wait timed out on crtc 0
[   55.375212] Modules linked in: iwl4965 iwlegacy
[   55.375227] CPU: 1 PID: 3609 Comm: X Tainted: G        W       4.7.5-gentoo
#1
[   55.375231] Hardware name: Dell Inc. Latitude D630                  
/0KU184, BIOS A17 01/04/2010
[   55.375236]  0000000000000000 ffffffff8144a38d ffff8800d6013910
0000000000000000
[   55.375244]  ffffffff810daeaf 0000000000000000 ffff8800d6013960
0000000000000000
[   55.375252]  0000000000000014 ffff8800da17b608 0000000000000001
ffffffff810daf1a
[   55.375260] Call Trace:
[   55.375272]  [<ffffffff8144a38d>] ? dump_stack+0x46/0x59
[   55.375280]  [<ffffffff810daeaf>] ? __warn+0xbf/0xe0
[   55.375286]  [<ffffffff810daf1a>] ? warn_slowpath_fmt+0x4a/0x50
[   55.375293]  [<ffffffff81985c72>] ? _raw_spin_lock_irqsave+0x12/0x40
[   55.375299]  [<ffffffff81523af1>] ? drm_wait_one_vblank+0x131/0x180
[   55.375307]  [<ffffffff81115770>] ? wait_woken+0x80/0x80
[   55.375316]  [<ffffffff815b8ce5>] ? intel_pre_plane_update+0x145/0x170
[   55.375322]  [<ffffffff815b94f6>] ? intel_atomic_commit+0x336/0x12d0
[   55.375330]  [<ffffffff8153a715>] ? drm_atomic_check_only+0x145/0x640
[   55.375335]  [<ffffffff81985a8f>] ? _raw_spin_unlock_irqrestore+0xf/0x30
[   55.375342]  [<ffffffff815bf8c1>] ? intel_release_load_detect_pipe+0x21/0x80
[   55.375350]  [<ffffffff815fa236>] ? intel_tv_detect+0x326/0x570
[   55.375360]  [<ffffffff81510234>] ?
drm_helper_probe_single_connector_modes+0x2c4/0x4d0
[   55.375368]  [<ffffffff8152e629>] ? drm_mode_getconnector+0x319/0x360
[   55.375374]  [<ffffffff810fd2c9>] ? preempt_count_add+0x99/0xa0
[   55.375381]  [<ffffffff81521de1>] ? drm_ioctl+0x121/0x490
[   55.375387]  [<ffffffff8152e310>] ? drm_mode_getcrtc+0x120/0x120
[   55.375395]  [<ffffffff812208c6>] ? do_vfs_ioctl+0x86/0x5b0
[   55.375402]  [<ffffffff812146bf>] ? SyS_newfstat+0x1f/0x30
[   55.375409]  [<ffffffff8122aa4b>] ? __fget+0x6b/0xb0
[   55.375414]  [<ffffffff81220e26>] ? SyS_ioctl+0x36/0x70
[   55.375420]  [<ffffffff81001a5c>] ? syscall_trace_enter_phase2+0x12c/0x210
[   55.375425]  [<ffffffff81001cdd>] ? do_syscall_64+0x4d/0x100
[   55.375431]  [<ffffffff819860fc>] ? entry_SYSCALL64_slow_path+0x25/0x25
[   55.375436] ---[ end trace da2e91405d3d4515 ]---

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20160925/849c599a/attachment-0001.html>


More information about the intel-gfx-bugs mailing list