Created attachment 134458 [details]
bisect log (drm)
(I've only Intel hardware available but since git bisect shows the culprit in drm and not drm/i915, I've filed it against DRM/other, feel free to reassign)
Since 4.11, I've noticed major flickering on some displays I have (reproducible 100%). By flickering I mean the screen is mostly black and every few seconds I can see a flash with the screen content and it goes black again.
It only occurs with the preferred mode, i.e. when I force a modeline to another mode in xorg.conf the flickering does not occur.
I've tried all versions up to latest 4.14.0-rc2 and it is still reproducible, 4.10.x were fine. The display driver used (intel or modesetting) does not make a difference.
I tried on all hardware I have here (NUC gen4 d5420, NUC5i5 and NUC6i5SYB) and the behavior is the same. I tried miniDP and HDMI, and it does not change anything.
The captured logs below have been run on a NUC6i5SYB connected with miniDP, running CentOS 7.3, with the kernel 4.11.8 (from mainline, no ct7 or rhel patches). The git bisect was also run on this machine.
Git bisect identified fcc8a22cc9053a8d1bbb94833ec103cd5961feef as first bad commit.
With the log files below, 4.11.8-1 is "original" 4.11.8 kernel (bad), and 4.11.8-2 includes the commit reverted (good).
From the git bisect log and the fact it can be worked around with another modeline, I'm not even sure this is a regression in the kernel, as this might be that the screen is advertising something it cannot support properly...
Created attachment 134459 [details]
dmesg with flickering
Created attachment 134460 [details]
xrandr with flickering
Created attachment 134461 [details]
dmesg without flickering
Created attachment 134462 [details]
xrandr without flickering
Created attachment 134463 [details]
(for reference only, first attempt at bisecting in drm/i915, it does not show the real first bad commit, see https://bugs.freedesktop.org/attachment.cgi?id=134458 instead)