dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 96326] Heavy screen flickering in OpenGL apps on R9 390
Date: Fri, 29 Jul 2016 10:26:41 +0000	[thread overview]
Message-ID: <bug-96326-502-vLxeUwYNiL@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-96326-502@http.bugs.freedesktop.org/>


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

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

--- Comment #2 from Jan Ziak <0xe2.0x9a.0x9b@gmail.com> ---
The flickering disappears after switching from X11 to Linux console
(Ctrl+Alt+F1) and back (Ctrl+Alt+F7). mclk transitions 150MHz <-> 1500MHz no
longer cause monitor flickering after that.

The code in the Linux kernel executed during the switch to Linux console and
back fixes the issue, we just need to pinpoint the code lines responsible for
the fix.

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

[-- Attachment #1.2: Type: text/html, Size: 1340 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:[~2016-07-29 10:26 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-02 14:51 [Bug 96326] Heavy screen flickering in OpenGL apps on R9 390 bugzilla-daemon
2016-06-17 13:50 ` bugzilla-daemon
2016-07-29 10:26 ` bugzilla-daemon [this message]
2016-07-29 14:20 ` bugzilla-daemon
2016-07-29 18:57 ` bugzilla-daemon
2016-07-29 18:59 ` bugzilla-daemon
2016-07-29 19:08 ` bugzilla-daemon
2016-08-01 13:52 ` bugzilla-daemon
2016-08-01 14:04 ` bugzilla-daemon
2019-11-19  9:16 ` 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-96326-502-vLxeUwYNiL@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox