dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 108514] heavy screen flickering with Mobility Radeon X1600 and kernel version 3.15rc2 onward
Date: Thu, 07 Feb 2019 22:54:34 +0000	[thread overview]
Message-ID: <bug-108514-502-iFYvF2dbQW@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-108514-502@http.bugs.freedesktop.org/>


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

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

--- Comment #24 from Paul Dufresne <dufresnep@gmail.com> ---
Created attachment 143333
  --> https://bugs.freedesktop.org/attachment.cgi?id=143333&action=edit
dufrp's dmesg for kernel 5.0rc5 (xstarted as root) with no flickering

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

[-- Attachment #1.2: Type: text/html, Size: 1451 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:[~2019-02-07 22:54 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-22 16:07 [Bug 108514] heavy screen flickering with Mobility Radeon X1600 and kernel version onwards 3.13 bugzilla-daemon
2018-10-22 18:14 ` bugzilla-daemon
2018-10-23 16:31 ` bugzilla-daemon
2018-10-23 16:34 ` bugzilla-daemon
2018-10-23 16:45 ` bugzilla-daemon
2018-10-23 17:07 ` bugzilla-daemon
2018-10-24 13:29 ` bugzilla-daemon
2018-10-30 15:54 ` bugzilla-daemon
2018-11-04 14:41 ` bugzilla-daemon
2018-11-04 14:43 ` bugzilla-daemon
2018-11-04 14:48 ` bugzilla-daemon
2018-12-04 14:39 ` bugzilla-daemon
2018-12-07 16:40 ` bugzilla-daemon
2019-02-06 19:34 ` bugzilla-daemon
2019-02-06 22:42 ` bugzilla-daemon
2019-02-07  8:07 ` [Bug 108514] heavy screen flickering with Mobility Radeon X1600 and kernel version 3.15rc2 onward bugzilla-daemon
2019-02-07  8:13 ` bugzilla-daemon
2019-02-07 19:38 ` bugzilla-daemon
2019-02-07 19:40 ` bugzilla-daemon
2019-02-07 19:53 ` bugzilla-daemon
2019-02-07 19:54 ` bugzilla-daemon
2019-02-07 21:34 ` bugzilla-daemon
2019-02-07 21:36 ` bugzilla-daemon
2019-02-07 21:58 ` bugzilla-daemon
2019-02-07 22:04 ` bugzilla-daemon
2019-02-07 22:53 ` bugzilla-daemon
2019-02-07 22:54 ` bugzilla-daemon [this message]
2019-02-07 23:02 ` bugzilla-daemon
2019-02-07 23:05 ` bugzilla-daemon
2019-02-08 20:05 ` bugzilla-daemon
2019-02-12 21:43 ` bugzilla-daemon
2019-02-12 21:43 ` bugzilla-daemon
2019-02-12 21:49 ` bugzilla-daemon
2019-02-14 21:36 ` bugzilla-daemon
2019-02-14 22:22 ` bugzilla-daemon
2019-02-19 21:25 ` bugzilla-daemon
2019-04-15 13:07 ` bugzilla-daemon
2019-04-15 13:13 ` bugzilla-daemon
2019-05-06 14:18 ` bugzilla-daemon
2019-05-06 14:19 ` bugzilla-daemon
2019-05-15  6:36 ` bugzilla-daemon
2019-06-12 16:27 ` bugzilla-daemon
2019-11-23  2:24 ` bugzilla-daemon
2019-11-23  2:28 ` bugzilla-daemon
2019-11-25  9:46 ` bugzilla-daemon
2019-12-08  6:00 ` bugzilla-daemon
2019-12-09 10:58 ` 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-108514-502-iFYvF2dbQW@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;
as well as URLs for NNTP newsgroup(s).