All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 105083] Random blinking display
Date: Tue, 20 Feb 2018 21:59:18 +0000	[thread overview]
Message-ID: <bug-105083-502-1rD0FJGE4P@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-105083-502@http.bugs.freedesktop.org/>


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

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

--- Comment #9 from Öyvind Saether <oyvinds@everdot.org> ---
I get random blue color screen flickering perhaps once every few minutes on
each monitor with redshift and a RX 580 and a 3x4k 60Hz setup with kernel
4.15.3 and amdgpu.dc=1. My initial response was that amdgpu.dc is broken so I
reverted back to 4.14.x and used that until I found this bug and realized it's
the redshift that's badly handled / problematic with the amdgpu.dc code.

This isn't really a redshift bug, just the way it behaves with this new code
since I've used redshift since forever on numerous configurations and this is a
new problem.

The random blue flickering with redshift seems to randomly appear on one of the
monitors, not all or two at once. All do not blink the same time. I can't
really see any pattern either. Every few minutes one of the monitors will blink
blue. Sometimes none of them blink blue for a long time.

Everything seems fine so far without redshift apart from the blue color
spectrum now violently smashing my eyes. My eyes, my eyes! I'll test if
redshift is OK with transition = 0 later, it could be a workaround if it is the
gradual adjustment of gamma/color that causes the flickering.

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

[-- Attachment #1.2: Type: text/html, Size: 2079 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

  parent reply	other threads:[~2018-02-20 21:59 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-13 20:34 [Bug 105083] Random blinking display bugzilla-daemon
2018-02-14  9:06 ` bugzilla-daemon
2018-02-14 10:21 ` bugzilla-daemon
2018-02-14 20:11 ` bugzilla-daemon
2018-02-14 20:19 ` bugzilla-daemon
2018-02-17 11:05 ` bugzilla-daemon
2018-02-17 11:15 ` bugzilla-daemon
2018-02-17 13:30 ` bugzilla-daemon
2018-02-20 16:24 ` bugzilla-daemon
2018-02-20 21:59 ` bugzilla-daemon [this message]
2018-02-27  0:15 ` bugzilla-daemon
2018-03-03 13:00 ` bugzilla-daemon
2018-03-03 13:07 ` bugzilla-daemon
2018-03-05 14:31 ` bugzilla-daemon
2018-03-05 20:33 ` bugzilla-daemon
2018-03-09  9:19 ` bugzilla-daemon
2018-03-09 14:02 ` bugzilla-daemon
2018-04-03  6:04 ` bugzilla-daemon
2018-04-17 18:10 ` bugzilla-daemon
2018-05-13 12:11 ` bugzilla-daemon
2018-06-08 21:11 ` bugzilla-daemon
2018-06-17  8:21 ` 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-105083-502-1rD0FJGE4P@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.