From: "Christian König" <christian.koenig@amd.com>
To: Ken Moffat <zarniwhoop@ntlworld.com>
Cc: Alex Deucher <alexdeucher@gmail.com>, <linux-kernel@vger.kernel.org>
Subject: Re: More breakage on HD7480D [ Aruba ]
Date: Mon, 12 May 2014 09:32:54 +0200 [thread overview]
Message-ID: <53707926.5090609@amd.com> (raw)
In-Reply-To: <20140512010310.GA4370@milliways>
Hi Ken,
*sigh* did I already mentioned that I hate PLLs? As soon as you fix
something another use case immediately starts to break.
Please provide dmesg output created with drm.debug=0xe with and without
the patch breaking it.
Thanks in advance,
Christian.
Am 12.05.2014 03:03, schrieb Ken Moffat:
> On Mon, May 12, 2014 at 01:34:06AM +0100, Ken Moffat wrote:
>
> /me swears at myself for failing to copy to lkml.
>
>> Hi Christian, Alex -
>>
>> my A4 Trinity (Radeon HD7480D) was working fine by -rc3. But now
>> that I've tested it in -rc5 it is again broken (the screen goes
>> blank when KMS starts). Bisection blames:
>>
>> 3b333c55485fef0089ae7398906599d000df195e is the first bad commit
>> commit 3b333c55485fef0089ae7398906599d000df195e
>> Author: Christian König <christian.koenig@amd.com>
>> Date: Thu Apr 24 18:39:59 2014 +0200
>>
>> drm/radeon: avoid high jitter with small frac divs
>>
>> Signed-off-by: Christian König <christian.koenig@amd.com>
>>
>> Reverting that from current HEAD [
>>
>> commit 7e338c9991ecee9c2ac7a4cee2c2e11ecb563d02
>> Merge: 9cf22e80df77 aa07c713ecfc
>> Author: Linus Torvalds <torvalds@linux-foundation.org>
>> Date: Sun May 11 18:06:13 2014 +0900
>>
>> Merge branch 'for-3.15' of git://linux-nfs.org/~bfields/linux
>>
>> Pull nfsd fixes from Bruce Fields.
>>
>> ]
>> makes it again boot.
>>
>> Note to Alex - 3.15 has been an "interesting" cycle - you fixed my
>> earlier problem, despite my non-response, and thanks again for that.
>> After that, my other radeon broke after -rc2 (I retested it after
>> rc4 and found that although rc4 was broken, HEAD was fixed, so
>> thanks also for that. Then I retested this one for -rc5. It seems
>> that my boxes always break when I don't have time to test new
>> releases :-(
>>
>> ĸen
>> --
>> das eine Mal als Tragödie, dieses Mal als Farce
next prev parent reply other threads:[~2014-05-12 7:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20140512003405.GA3386@milliways>
2014-05-12 1:03 ` More breakage on HD7480D [ Aruba ] Ken Moffat
2014-05-12 7:32 ` Christian König [this message]
2014-05-12 16:32 ` Ken Moffat
2014-05-13 11:22 ` Christian König
2014-05-13 16:12 ` Ken Moffat
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=53707926.5090609@amd.com \
--to=christian.koenig@amd.com \
--cc=alexdeucher@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=zarniwhoop@ntlworld.com \
/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