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 87682] Horizontal lines in radeon driver on kernel 3.15 and upwards
Date: Wed, 24 Dec 2014 15:35:20 +0000	[thread overview]
Message-ID: <bug-87682-502@http.bugs.freedesktop.org/> (raw)


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

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

            Bug ID: 87682
           Summary: Horizontal lines in radeon driver on kernel 3.15 and
                    upwards
           Product: Mesa
           Version: git
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: major
          Priority: medium
         Component: Drivers/Gallium/r600
          Assignee: dri-devel@lists.freedesktop.org
          Reporter: qwrules@gmail.com

Created attachment 111292
  --> https://bugs.freedesktop.org/attachment.cgi?id=111292&action=edit
Youtube video depicting the artefacts.

This is what I get if I run any kernel newer than 3.14:
https://www.youtube.com/watch?v=nx2-Fvihzxg
Those artefacts appear as soon as new kernel is selected in GRUB, and remain
after logging into X session.

The last kernel working without artefacts is v3.15-rc2-trusty for Ubuntu, and
3.14.7 for Arch. All later kernels have those artefacts.

I updated mesa and xorg to those form ppaibaf/graphics-drivers ppa on Ubuntu,
and on using git version on Arch but it did not change a thing. This regression
is solely kernel-related.

GPU: Mobility Radeon HD 3200 (RS780M)
System tested: Arch, Ubuntu 14.04, 14.10
Kernels affected: 3.15 and onwards (tested up to 3.19-rc1)

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

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

             reply	other threads:[~2014-12-24 15:35 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-24 15:35 bugzilla-daemon [this message]
2014-12-24 15:38 ` [Bug 87682] Horizontal lines in radeon driver on kernel 3.15 and upwards bugzilla-daemon
2014-12-25  1:17 ` bugzilla-daemon
2014-12-25 12:37 ` bugzilla-daemon
2014-12-25 15:11 ` bugzilla-daemon
2015-01-05 17:24 ` bugzilla-daemon
2015-01-05 17:25 ` bugzilla-daemon
2016-05-02 23:10 ` bugzilla-daemon
2016-05-03  8:02 ` bugzilla-daemon
2016-05-04  9:39 ` bugzilla-daemon
2016-05-04 22:13 ` bugzilla-daemon
2016-05-05 17:01 ` bugzilla-daemon
2016-05-05 17:37 ` bugzilla-daemon
2016-05-06  2:25 ` bugzilla-daemon
2016-05-06 14:26 ` bugzilla-daemon
2016-05-09  9:26 ` bugzilla-daemon
2016-05-09 20:42 ` bugzilla-daemon
2016-05-10  1:42 ` bugzilla-daemon
2016-05-10  9:06 ` bugzilla-daemon
2016-05-10 22:12 ` bugzilla-daemon
2016-05-12 20:58 ` bugzilla-daemon
2016-06-14  8:03 ` bugzilla-daemon
2016-07-22 20:03 ` bugzilla-daemon
2016-07-22 22:34 ` bugzilla-daemon
2016-07-22 23:20 ` bugzilla-daemon
2016-07-23 21:02 ` bugzilla-daemon
2016-07-28 15:53 ` bugzilla-daemon
2016-07-28 16:23 ` 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-87682-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox