From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 87682] Horizontal lines in radeon driver on kernel 3.15 and upwards Date: Thu, 05 May 2016 17:01:21 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1852085205==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [IPv6:2610:10:20:722:a800:ff:fe98:4b55]) by gabe.freedesktop.org (Postfix) with ESMTP id B73116E17F for ; Thu, 5 May 2016 17:01:20 +0000 (UTC) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============1852085205== Content-Type: multipart/alternative; boundary="14624676801.9AFC.28052"; charset="UTF-8" --14624676801.9AFC.28052 Date: Thu, 5 May 2016 17:01:20 +0000 MIME-Version: 1.0 Content-Type: text/plain https://bugs.freedesktop.org/show_bug.cgi?id=87682 --- Comment #9 from Thom --- (In reply to Chris Bainbridge from comment #8) > This is not correct. The 77/69 does not imply a linear ordering because of > forks: > Trust git ;-) Thanks for the update, that explains everything. I hardly know git, and before yesterday I didn't even know what git or what bisecting was...it's a bit overwhelming. > > > c2fb3094669a3205f16a32f4119d0afe40b1a1fd is the first bad commit > > Not familiar with this code, but from the patch the PLL values are printed > out: > > DRM_DEBUG_KMS("%d - %d, pll dividers - fb: %d.%d ref: %d, post > %d\n", > freq, *dot_clock_p * 10, *fb_div_p, *frac_fb_div_p, > ref_div, post_div); > That is like magic :-) How did you get git to give you the source of that patch so quickly ? (I googled for hours on this stuff without success) > So suggest enabling debug log and compare those two lines from a working and > non-working kernel. > I assume that I have to enable debug log via a bootoption because I couldn't find anything in menuconfig that wasn't already marked for inclusion. What bootoption do I have to use to enable the right (and right amount of) debug logging ? (and after that, where do I find the log output?) > It should also be trivial to checkout a recent tag and revert the bad commit I don't even know yet what that is or how to do that, even after reading the man pages about checkout, tag, revert and commit; but I'm convinced I'll get there in the end ;-) -- You are receiving this mail because: You are the assignee for the bug. --14624676801.9AFC.28052 Date: Thu, 5 May 2016 17:01:20 +0000 MIME-Version: 1.0 Content-Type: text/html

Comment # 9 on bug 87682 from 
(In reply to Chris Bainbridge from comment #8)

> This is not correct. The 77/69 does not imply a linear ordering because of
> forks:
> Trust git ;-)

Thanks for the update, that explains everything. I hardly know git, and before
yesterday I didn't even know what git or what bisecting was...it's a bit
overwhelming.

> 
> > c2fb3094669a3205f16a32f4119d0afe40b1a1fd is the first bad commit
> 
> Not familiar with this code, but from the patch the PLL values are printed
> out:
> 
>          DRM_DEBUG_KMS("%d - %d, pll dividers - fb: %d.%d ref: %d, post
> %d\n",
>                       freq, *dot_clock_p * 10, *fb_div_p, *frac_fb_div_p,
>                       ref_div, post_div);
> 

That is like magic :-) How did you get git to give you the source of that patch
so quickly  ?
(I googled for hours on this stuff without success) 

> So suggest enabling debug log and compare those two lines from a working and
> non-working kernel.
>

I assume that I have to enable debug log via a bootoption because I couldn't
find anything in menuconfig that wasn't already marked for inclusion.
What bootoption do I have to use to enable the right (and right amount of)
debug logging ? (and after that, where do I find the log output?)

> It should also be trivial to checkout a recent tag and revert the bad commit

I don't even know yet what that is or how to do that, even after reading the
man pages about checkout, tag, revert and commit; but I'm convinced I'll get
there in the end ;-)

You are receiving this mail because:
  • You are the assignee for the bug.
--14624676801.9AFC.28052-- --===============1852085205== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVsCg== --===============1852085205==--