All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 102972] Flickering since 4.11
Date: Mon, 25 Sep 2017 12:20:28 +0000	[thread overview]
Message-ID: <bug-102972-502@http.bugs.freedesktop.org/> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 2181 bytes --]

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

            Bug ID: 102972
           Summary: Flickering since 4.11
           Product: DRI
           Version: XOrg git
          Hardware: All
                OS: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: DRM/other
          Assignee: dri-devel@lists.freedesktop.org
          Reporter: lionel-fdo@lefolgoc.net

Created attachment 134458
  --> https://bugs.freedesktop.org/attachment.cgi?id=134458&action=edit
bisect log (drm)

Hi,

(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...

Thanks.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 3584 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

             reply	other threads:[~2017-09-25 12:20 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-25 12:20 bugzilla-daemon [this message]
2017-09-25 12:20 ` [Bug 102972] Flickering since 4.11 bugzilla-daemon
2017-09-25 12:21 ` bugzilla-daemon
2017-09-25 12:21 ` bugzilla-daemon
2017-09-25 12:21 ` bugzilla-daemon
2017-09-25 12:22 ` bugzilla-daemon
2017-09-25 12:23 ` bugzilla-daemon
2017-09-25 12:23 ` bugzilla-daemon
2017-09-25 12:23 ` bugzilla-daemon
2017-09-25 12:23 ` bugzilla-daemon
2017-09-25 12:27 ` bugzilla-daemon
2019-10-14 13:20 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-102972-502@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.