See example here: https://goo.gl/photos/WZWuue9838c9utqp6
This is only present in 1-monitor case; 2-monitor case causes bug 97037 instead
dual video hardware, bumblebee (usually keep nvidia card disabled)
# lspci -nnn -vvv -s00:02.0
00:02.0 VGA compatible controller : Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller])
Subsystem: CLEVO/KAPOK Computer Device [1558:5281]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Interrupt: pin A routed to IRQ 35
Region 0: Memory at f7400000 (64-bit, non-prefetchable) [size=4M]
Region 2: Memory at d0000000 (64-bit, prefetchable) [size=256M]
Region 4: I/O ports at f000 [size=64]
[virtual] Expansion ROM at 000c0000 [disabled] [size=128K]
Capabilities:  MSI: Enable+ Count=1/1 Maskable- 64bit-
Address: fee00018 Data: 0000
Capabilities: [d0] Power Management version 2
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [a4] PCI Advanced Features
AFCap: TP+ FLR+
Kernel driver in use: i915
Kernel modules: i915
This issue looks visually very similar to https://bugs.freedesktop.org/show_bug.cgi?id=95414 .. which in my case could be circumvented by disabling TearFree. Perhaps it is not the exact same issue, but might be worth trying to disable TearFree if you have it enabled?
Yes, disabling TearFree seems to fix it for me, as well as avoiding OOM condition that also happens while playing fullscreen.
Will this be fixed in the near future?
Alas, I am only a user, not developer, so I can't answer when or if it will be fixed. However, your report(s) do not include Xorg.log or other information about your setup so I can only guess that you are using DRI2. With DRI3 (+TearFree, if you wish) this issue does not present itself, but I should warn that DRI3 has/may have other problems.
Sorry for the late reply, I'm not subscribed to this bug #.
The visual glitches here are not originating from the ddx; the pattern here is consistent with GL rendering. Nevertheless, the same kernel fix is definitely required.