All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 89198] Setting Refresh Rate on monitor causes flickering/artifacting
Date: Fri, 20 Feb 2015 01:12:52 +0000	[thread overview]
Message-ID: <bug-89198-502-RzjGVWZf36@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-89198-502@http.bugs.freedesktop.org/>


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

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

--- Comment #18 from Alex Deucher <alexdeucher@gmail.com> ---
(In reply to andre35822 from comment #17)
> Alright so I tried out the kernel I compiled with the patch from comment 15
> on the other bug report, and either I didn't install the patch correctly (or
> it didnt install correctly) or the patch is not solving the problem. I am
> still getting the flickering/artifacts. I have attached an xorg log and
> dmesg log and added comment15_patch to each of their file names so they are
> easily distinguishable. Should I be compiling another kernel with the
> patches from comment 19 and 20?

The patch from comment 15 doesn't fix anything.  It just adds some additional
debugging output that might be useful in fine tuning the patches in comments 19
and 20.  To fix the issue, use the patches in comments 19 and 20.

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

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

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

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

  parent reply	other threads:[~2015-02-20  1:12 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-89198-502@http.bugs.freedesktop.org/>
2015-02-18  5:18 ` [Bug 89198] Setting Refresh Rate on monitor causes flickering/artifacting bugzilla-daemon
2015-02-18  5:33 ` bugzilla-daemon
2015-02-18  5:35 ` bugzilla-daemon
2015-02-18  5:35 ` bugzilla-daemon
2015-02-18  5:44 ` bugzilla-daemon
2015-02-18 13:22 ` bugzilla-daemon
2015-02-18 13:22 ` bugzilla-daemon
2015-02-18 14:06 ` bugzilla-daemon
2015-02-18 15:17 ` bugzilla-daemon
2015-02-18 15:22 ` bugzilla-daemon
2015-02-18 19:26 ` bugzilla-daemon
2015-02-18 20:56 ` bugzilla-daemon
2015-02-19 20:34 ` bugzilla-daemon
2015-02-19 20:41 ` bugzilla-daemon
2015-02-20  1:07 ` bugzilla-daemon
2015-02-20  1:07 ` bugzilla-daemon
2015-02-20  1:09 ` bugzilla-daemon
2015-02-20  1:12 ` bugzilla-daemon [this message]
2015-02-20  2:15 ` bugzilla-daemon
2015-02-20  3:21 ` bugzilla-daemon
2015-02-20  3:56 ` 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-89198-502-RzjGVWZf36@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.