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: Fri, 06 May 2016 02:25:44 +0000	[thread overview]
Message-ID: <bug-87682-502-00y8IOeTFp@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-87682-502@http.bugs.freedesktop.org/>


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

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

--- Comment #11 from Thom <madeforspam@telfort.nl> ---
ok, some results:

PLL-readings on good working compilations:

3.15.0-rc1-00303-g6e66d5d
[drm:radeon_compute_pll_avivo] 69300 - 6949, pll dividers - fb: 165.0 ref: 2,
post 17

3.15.0-rc2-00042-g4d0fa8a
[drm:radeon_compute_pll_avivo] 69300 - 6930, pll dividers - fb: 329.1 ref: 4,
post 17

3.15.0-rc2-00077-g76e7745
[drm:radeon_compute_pll_avivo] 69300 - 6930, pll dividers - fb: 329.1 ref: 4,
post 17

3.15.0-rc1-00070-g2431581
no output, system hangs loading driver in debug mode
(probably because this one didn't had the patch yet.)
works ok when not in debug mode.



PLL-readings on bad noisy-artefacty compilations:

3.15.0-rc2-00069-g1aae31c
[drm:radeon_compute_pll_avivo] 69300 - 69290, pll dividers - fb: 135.5 ref: 2,
post 14

3.15.0-rc1-00071-gc2fb309
[drm:radeon_compute_pll_avivo] 69300 - 69290, pll dividers - fb: 135.5 ref: 2,
post 14

3.15.0-rc1-00075-g3ed9a33
[drm:radeon_compute_pll_avivo] 69300 - 69290, pll dividers - fb: 135.5 ref: 2,
post 14

3.15.0-rc2-00092-g92891ed
[drm:radeon_compute_pll_avivo] 69300 - 69290, pll dividers - fb: 135.5 ref: 2,
post 14


Problem is: I haven't the slightest clue what it all means.

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

[-- Attachment #1.2: Type: text/html, Size: 2104 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-06  2:25 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
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 [this message]
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-00y8IOeTFp@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