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: Mon, 02 May 2016 23:10:19 +0000	[thread overview]
Message-ID: <bug-87682-502-hYAu2k4JG6@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-87682-502@http.bugs.freedesktop.org/>


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

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

--- Comment #5 from Thom <madeforspam@telfort.nl> ---
I can confirm this bug: Laptop HP 6735s 2xTurion + RS780M videochip
I happen to have the exact same artefacts with any kernelversion higher than
3.13
It affects the buildin LVDS but NOT the VGA-output.

I tested kernels up to 4.4.0 (to no avail)

I don't know what "git bisect" is but eager to learn.
I also dropped a note on https://bugzilla.kernel.org/show_bug.cgi?id=83461

I used the link to Lockheed's video as illustration on
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1479136 where I originally
filed a bug.

I am in the happy circumstances to dedicate this laptop to any test you want me
to throw at it.

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

[-- Attachment #1.2: Type: text/html, Size: 1734 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-05-02 23:10 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-24 15:35 [Bug 87682] Horizontal lines in radeon driver on kernel 3.15 and upwards bugzilla-daemon
2014-12-24 15:38 ` 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 [this message]
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-hYAu2k4JG6@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