All of 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, 04 May 2016 09:39:34 +0000	[thread overview]
Message-ID: <bug-87682-502-a14KBabKUG@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-87682-502@http.bugs.freedesktop.org/>


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

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

--- Comment #7 from Thom <madeforspam@telfort.nl> ---
Ok, I did my first bisect, it worked out well but I encountered something that
puzzles me a bit.
Here is the last part of the bisect:

3.15.0-rc3-00725-g1465967  bad

Bisecting: 658 revisions left to test after this (roughly 9 steps)
[e9dba837640d960f56bef22ff08611955ff8a5b4] Merge tag 'pm+acpi-3.15-rc3' of
git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm

3.15.0-rc2-00219-ge9dba83  bad

Bisecting: 355 revisions left to test after this (roughly 8 steps)
[6e66d5dab5d530a368314eb631201a02aabb075d] Merge branch 'for-next' of
git://git.samba.org/sfrench/cifs-2.6


3.15.0-rc1-00303-g6e66d5d good

Bisecting: 176 revisions left to test after this (roughly 8 steps)
[4d0fa8a0f01272d4de33704f20303dcecdb55df1] Merge tag 'gpio-v3.15-2' of
git://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-gpio

3.15.0-rc2-00042-g4d0fa8a good

Bisecting: 99 revisions left to test after this (roughly 7 steps)
[76e7745e8e4330fdb30f049303d524261c0b7a2c] Merge tag 'zynq-dt-fixes-for-3.15'
of git://git.xilinx.com/linux-xlnx into fixes

3.15.0-rc2-00077-g76e7745 good (how can this be ??)

Bisecting: 49 revisions left to test after this (roughly 6 steps)
[92891ed6b1fdb49655f9a071ef2880a567807375] Merge branch 'fixes_for_v3.15' of
git://git.linaro.org/people/mszyprowski/linux-dma-mapping

3.15.0-rc2-00092-g92891ed bad

Bisecting: 22 revisions left to test after this (roughly 5 steps)
[1aae31c8306e5f1bdeafd87b2cd9e3f0df3709e5] Merge branch 'for-linus' of
git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input

3.15.0-rc2-00069-g1aae31c bad

Bisecting: 13 revisions left to test after this (roughly 4 steps)
[7740fc52105c9e6d2beac389a9ae0ce7138cf5ab] Input: soc_button_array - fix a
crash during rmmod

3.14.0-rc4-00065-g7740fc5 good

Bisecting: 6 revisions left to test after this (roughly 3 steps)
[3ed9a335cfc64b2c83545f341cdddf2347b12b97] drm/radeon/pm: don't walk the crtc
list before it has been initialized (v2)

3.15.0-rc1-00075-g3ed9a33 bad

Bisecting: 3 revisions left to test after this (roughly 2 steps)
[c2fb3094669a3205f16a32f4119d0afe40b1a1fd] drm/radeon: improve PLL limit
handling in post div calculation

3.15.0-rc1-00071-gc2fb309 bad

Bisecting: 0 revisions left to test after this (roughly 1 step)
[24315814239a3fdb306244c99bd076bc79db4ade] drm/radeon: use fixed PPL ref
divider if needed

3.15.0-rc1-00070-g2431581 good

c2fb3094669a3205f16a32f4119d0afe40b1a1fd is the first bad commit

commit c2fb3094669a3205f16a32f4119d0afe40b1a1fd
Author: Christian König <christian.koenig@amd.com>
Date:   Sun Apr 20 13:24:32 2014 +0200

    drm/radeon: improve PLL limit handling in post div calculation

    This improves the PLL parameters when we work at
    the limits of the allowed ranges.

    Signed-off-by: Christian König <christian.koenig@amd.com>

:040000 040000 5c3ac5ddf911c2c1f8926ecde2d83fdbcd6bb269
4731ceed6e1c149abd6fda6a06318700750f8

So far so good, but what I'm puzzled about is this:

As far as I understand; 3.15.0-rc2-00077-g76e7745 is a later revision (good)
than 3.15.0-rc2-00069-g1aae31c (bad) and an earlier revision than
3.15.0-rc2-00092-g92891ed (bad) which doesn't seem to make sense to me.

It is as if someone did a patch to improve on 3.15.0-rc1-00071-gc2fb309 but
that it got revoked afterwards, is that possible ?

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

[-- Attachment #1.2: Type: text/html, Size: 4352 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-04  9:39 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 [this message]
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-a14KBabKUG@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.