From: "Christian König" <christian.koenig@amd.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: linux-pm@vger.kernel.org, rjw@rjwysocki.net,
kernel list <linux-kernel@vger.kernel.org>,
dri-devel@lists.freedesktop.org, linux-acpi@vger.kernel.org,
alexander.deucher@amd.com, lenb@kernel.org
Subject: Re: 4.1-rc7: Xorg broken after resume on thinkpad T40p, radeon problem?
Date: Wed, 17 Jun 2015 15:31:34 +0200 [thread overview]
Message-ID: <558176B6.9010607@amd.com> (raw)
In-Reply-To: <20150617132121.GA24634@amd>
On 17.06.2015 15:21, Pavel Machek wrote:
> On Wed 2015-06-17 15:07:41, Christian König wrote:
>> On 17.06.2015 14:49, Pavel Machek wrote:
>>> On Wed 2015-06-17 14:43:47, Pavel Machek wrote:
>>>> Hi!
>>>>
>>>> Video is broken on thinkpad T40p after resume from suspend. (In X
>>>> only, text console still works.)
>>>>
>>>> Maybe this is related?
>>>>
>>>> [ 5430.193071] radeon 0000:01:00.0: putting AGP V2 device into 4x mode
>>>> [ 5430.193107] radeon 0000:01:00.0: GTT: 256M 0xD0000000 - 0xDFFFFFFF
>>>> [ 5430.214670] radeon 0000:01:00.0: WB disabled
>>>> [ 5430.214675] radeon 0000:01:00.0: fence driver on ring 0 use gpu addr 0x00000000d0000000 and cpu addr 0xf841a000
>>>> [ 5430.214721] [drm] radeon: ring at 0x00000000D0001000
>>>> [ 5430.370867] [drm:r100_ring_test] *ERROR* radeon: ring test failed (scratch(0x15E8)=0xCAFEDEAD)
>>>> [ 5430.370869] [drm:r100_cp_init] *ERROR* radeon: cp isn't working (-22).
>>>> [ 5430.370872] radeon 0000:01:00.0: failed initializing CP (-22).
>>>>
>>>> Hibernation works well here, including X. (Which has small glitch with
>>>> mouse cursor being corrupted until it is changed by application).
>>>>
>>> 3.16.0-4-686-pae Debian 3.16.7-cktt11-1 kernel seems to have same
>>> problem, with same scratch(0x15E8)=0xCAFEDEAD message... so this is
>>> not "new" problem...
>>>
>> Looks like CP init doesn't work. Well is there any kernel where that did
>> worked?
> Unfortunately, not as far as I know.
In this case we probably can't help in any way, it's most likely some
special handling required for exactly this configuration that isn't
document anymore anywhere (Well, we are talking about hardware that is
more than a decade old).
Sorry that I don't have any better news,
Christian.
>
>> If yes it might be a good idea to bisect to narrow down the problem.
> No such luck. I may try something like "3.0" if we are really
> desperate (2.6.X kernels probably won't won't boot with recent
> userland), but I suspect it just never worked.
>
> Pavel
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2015-06-17 13:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-17 12:43 4.1-rc7: Xorg broken after resume on thinkpad T40p, radeon problem? Pavel Machek
2015-06-17 12:49 ` Pavel Machek
2015-06-17 13:07 ` Christian König
2015-06-17 13:21 ` Pavel Machek
2015-06-17 13:31 ` Christian König [this message]
2015-06-17 13:50 ` Paul Bolle
2015-06-17 14:10 ` Pavel Machek
2015-06-17 14:22 ` Paul Bolle
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=558176B6.9010607@amd.com \
--to=christian.koenig@amd.com \
--cc=alexander.deucher@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=rjw@rjwysocki.net \
/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;
as well as URLs for NNTP newsgroup(s).