Same backtrace here, didn't realise this may be caused by DPMS update.

00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09) (prog-if 00 [VGA controller])
        Subsystem: ASRock Incorporation Device 0122
        Flags: bus master, fast devsel, latency 0, IRQ 16
        Memory at fe000000 (64-bit, non-prefetchable) [size=4M]
        Memory at c0000000 (64-bit, prefetchable) [size=256M]
        I/O ports at f000 [size=64]
        Expansion ROM at <unassigned> [disabled]
        Capabilities: [90] MSI: Enable- Count=1/1 Maskable- 64bit-
        Capabilities: [d0] Power Management version 2
        Capabilities: [a4] PCI Advanced Features
        Kernel driver in use: i915

A week ago, I switched to using only one external monitor (on the VGA port). Since then, I have not suffered from this bug. So it could be this only occurs when using a monitor connected via MiniDP->HDMI->DVI. Or only when two monitors are connected, of course.

I'll try connecting a single monitor via MiniDP->HDMI->DVI and using this setup for a week.

The monitor here is connected directly via DVI->DVI. The board offers HDMI, but that's not used.
I think this is a regression in 10.3.0. I got these freezes directly after booting with the upgraded mesa. I then downgraded to 10.2.8 (on 1. October) and since then never experienced this issue again.

Hi

What are the exact steps to reproduce, and how often do you get the bug when you do these steps? All that is needed is to wait until the machine enters DPMS state?

Can you please boot passing drm.debug=0xe as a Kernel argument (you can do that in grub), reproduce the bug, then attach the output of dmesg here?

I find it weird that you have a VGA port on an ULT machine. Can you please post the output of the "xrandr" command?

Just a notice: we are aware that some converters (e.g., DP->HDMI, HDMI->DVI, etc.) sometimes may cause problems. Not all converters cause this behavior, so if you could try to test other converters (or a DP monitor), it would be nice to know .

Thanks,
Paulo

This happened again yesterday, with mesa-10.2.8 - so no regression, at least not in mesa.
It happened while viewing a video in fullscreen, which also was the first time I saw this happen. But this also happened during regular use without any multimedia application running. It even happened after a fresh reboot, no window open and absolutely no activity.
This particular machine is running most recent kde desktop.

But I had this also on my Laptop, a Lenovo ThinkPad L520, no external monitor plugged in. I am running awesome WM with compton. It happened while watching a Video, also fullscreen, in flash + firefox (if that matters). I manually turned off dpms and screensaver using xset.

The only solution to get the monitor repainted again is to switch to another TTY (CTRL+ALT+Fx). It will take ~2 minutes until I see the terminal login. I then can switch back to my Xsession, everything seems to work fine, then.

I did not yet find a regular pattern to trigger this bug, it seems to happen quite randomly.

I encounter the same error on another desktop machine, using the same monitor connected via a DP->DVI adapter. Backtrace:

kernel: ------------[ cut here ]------------
kernel: WARNING: CPU: 0 PID: 24018 at drivers/gpu/drm/i915/intel_display.c:3313 intel_crtc_wait_for_pending_flips+0xe0/0x133()
kernel: Modules linked in: cfg80211 vboxnetadp(O) vboxnetflt(O) vboxdrv(O) cpufreq_ondemand snd_hda_codec_realtek snd_hda_codec_hdmi snd_hda_codec_generic snd_hda_intel snd_hda_controller snd_hda_codec e1000e snd_hwdep x86_pkg_temp_thermal snd_pcm coretemp sr_mod psmouse microcode cdrom snd_timer i2c_i801 ptp snd pps_core fan thermal battery processor
kernel: CPU: 0 PID: 24018 Comm: X Tainted: G           O  3.16.0+ #164
kernel: Hardware name: LENOVO 10AHS0NG00/SHARKBAY, BIOS FBKT75AUS 04/01/2014
kernel:  0000000000000000 ffff8801d736fc30 ffffffff81553866 0000000000000000
kernel:  ffff8801d736fc68 ffffffff81039595 ffffffff8138eb1c 0000000000000000
kernel:  ffff8802153f2000 ffff880215387d50 ffff8802150f2800 ffff8801d736fc78
kernel: Call Trace:
kernel:  [<ffffffff81553866>] dump_stack+0x4e/0x7a
kernel:  [<ffffffff81039595>] warn_slowpath_common+0x7a/0x93
kernel:  [<ffffffff8138eb1c>] ? intel_crtc_wait_for_pending_flips+0xe0/0x133
kernel:  [<ffffffff8103964d>] warn_slowpath_null+0x15/0x17
kernel:  [<ffffffff8138eb1c>] intel_crtc_wait_for_pending_flips+0xe0/0x133
kernel:  [<ffffffff8105f2c5>] ? finish_wait+0x60/0x60
kernel:  [<ffffffff813914c0>] intel_crtc_disable_planes+0x2b/0x148
kernel:  [<ffffffff81392114>] haswell_crtc_disable+0x3c/0x237
kernel:  [<ffffffff81392906>] intel_crtc_update_dpms+0x5c/0x6d
kernel:  [<ffffffff81395b76>] intel_connector_dpms+0x43/0x4e
kernel:  [<ffffffff81346739>] drm_mode_obj_set_property_ioctl+0x20f/0x2a9
kernel:  [<ffffffff813467fe>] drm_mode_connector_property_set_ioctl+0x2b/0x2d
kernel:  [<ffffffff813393d3>] drm_ioctl+0x381/0x3f9
kernel:  [<ffffffff813467d3>] ? drm_mode_obj_set_property_ioctl+0x2a9/0x2a9
kernel:  [<ffffffff81113987>] do_vfs_ioctl+0x351/0x415
kernel:  [<ffffffff8111b763>] ? __fget+0x6a/0x74
kernel:  [<ffffffff81113a83>] SyS_ioctl+0x38/0x5f
kernel:  [<ffffffff81559892>] system_call_fastpath+0x16/0x1b
kernel: ---[ end trace 36351689a27913b3 ]---

lspci -v:
00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller (rev 06) (prog-if 00 [VGA controller])
        Subsystem: Lenovo Device 309f
        Flags: bus master, fast devsel, latency 0, IRQ 40
        Memory at f7800000 (64-bit, non-prefetchable) [size=4M]
        Memory at e0000000 (64-bit, prefetchable) [size=256M]
        I/O ports at f000 [size=64]
        Expansion ROM at <unassigned> [disabled]
        Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
        Capabilities: [d0] Power Management version 2
        Capabilities: [a4] PCI Advanced Features
        Kernel driver in use: i915

kernel: 3.16.0

I have not tried the debug parameter, but will enable it at the next opportunity.

Timeout, closing. Please reopen (and attach dmesg with drm.debug=14) if the problem persists with latest kernels.