From: Borislav Petkov <bp@alien8.de>
To: Jerome Glisse <jglisse@redhat.com>
Cc: "Christian König" <christian.koenig@amd.com>,
"Alex Deucher" <alexander.deucher@amd.com>,
dri-devel@lists.freedesktop.org,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: 274ad65c9d02 ("drm/radeon: hard reset r600 and newer GPU when hibernating.")
Date: Wed, 8 Jun 2016 16:18:12 +0200 [thread overview]
Message-ID: <20160608141812.GC19090@pd.tnic> (raw)
In-Reply-To: <436069698.4632080.1465394783928.JavaMail.zimbra@redhat.com>
On Wed, Jun 08, 2016 at 10:06:23AM -0400, Jerome Glisse wrote:
> To be clear, you mean that after hibernation video acceleration keeps working ?
Apparently. At lest the vdpau output looks fine to me.
> Can you copy radeon dmesg after hibernation cycle (once you resumed
> from hibernation).
$ dmesg | grep -Ei "(radeon|drm)"
...
(boot messages)
...
[ 8.149356] fbcon: radeondrmfb (fb0) is primary device
[ 8.218800] radeon 0000:01:00.0: fb0: radeondrmfb frame buffer device
[ 8.238402] [drm] Initialized radeon 2.45.0 20080528 for 0000:01:00.0 on minor 0
<-- hibernate.
[ 64.711657] [drm] enabling PCIE gen 2 link speeds, disable with radeon.pcie_gen2=0
[ 64.714898] [drm] PCIE GART of 512M enabled (table at 0x0000000000142000).
[ 64.714920] radeon 0000:01:00.0: WB enabled
[ 64.714923] radeon 0000:01:00.0: fence driver on ring 0 use gpu addr 0x0000000020000c00 and cpu addr 0xffff88042b342c00
[ 64.715123] radeon 0000:01:00.0: fence driver on ring 5 use gpu addr 0x00000000000521d0 and cpu addr 0xffffc900030121d0
[ 64.745988] [drm] ring test on 0 succeeded in 1 usecs
[ 64.920633] [drm] ring test on 5 succeeded in 1 usecs
[ 64.920637] [drm] UVD initialized successfully.
[ 64.920652] [drm] ib test on ring 0 succeeded in 0 usecs
[ 65.128759] ata1.00: supports DRM functions and may not be fully accessible
[ 65.128799] ata2.00: supports DRM functions and may not be fully accessible
[ 65.133700] ata1.00: supports DRM functions and may not be fully accessible
[ 65.133811] ata2.00: supports DRM functions and may not be fully accessible
[ 65.566744] [drm] ib test on ring 5 succeeded
Let me know if you need more stuff dumped.
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
next prev parent reply other threads:[~2016-06-08 14:18 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-06 14:02 274ad65c9d02 ("drm/radeon: hard reset r600 and newer GPU when hibernating.") Borislav Petkov
2016-06-06 21:40 ` Jerome Glisse
2016-06-06 22:00 ` Borislav Petkov
2016-06-07 21:51 ` Jerome Glisse
2016-06-08 7:38 ` Christian König
2016-06-08 11:36 ` Borislav Petkov
2016-06-08 11:50 ` Christian König
2016-06-08 13:26 ` Borislav Petkov
2016-06-08 13:30 ` Christian König
2016-06-08 13:47 ` Borislav Petkov
2016-06-08 13:55 ` Borislav Petkov
2016-06-08 14:06 ` Jerome Glisse
2016-06-08 14:18 ` Borislav Petkov [this message]
2016-06-08 15:28 ` Grigori Goronzy
2016-06-08 16:32 ` Borislav Petkov
2016-06-08 16:44 ` Alex Deucher
2016-06-08 16:51 ` Borislav Petkov
2016-06-09 15:40 ` Alex Deucher
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=20160608141812.GC19090@pd.tnic \
--to=bp@alien8.de \
--cc=alexander.deucher@amd.com \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jglisse@redhat.com \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).