From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 196615] amdgpu - resume from suspend is no longer working on rx480
Date: Fri, 13 Oct 2017 21:36:33 +0000 [thread overview]
Message-ID: <bug-196615-2300-AlZHSOMg6x@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-196615-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=196615
contact@florentflament.com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |contact@florentflament.com
--- Comment #25 from contact@florentflament.com ---
Hi,
Same issue here. OS freezing after resume from suspend with an AMD RX480 GPU.
$ cat /etc/redhat-release
Fedora release 26 (Twenty Six)
$ uname -a
Linux amn 4.13.4-200.fc26.x86_64 #1 SMP Thu Sep 28 20:46:39 UTC 2017 x86_64
x86_64 x86_64 GNU/Linux
$ journalctl -k -b -2 | grep amdgpu | tail -5
Oct 12 01:46:06 amn kernel: [drm] Initialized amdgpu 3.18.0 20150101 for
0000:01:00.0 on minor 0
Oct 12 23:16:29 amn kernel: [drm:amdgpu_vce_ring_test_ring [amdgpu]] *ERROR*
amdgpu: ring 14 test failed
Oct 12 23:16:29 amn kernel: [drm:amdgpu_resume_phase2 [amdgpu]] *ERROR* resume
of IP block <vce_v3_0> failed -110
Oct 12 23:16:29 amn kernel: [drm:amdgpu_device_resume [amdgpu]] *ERROR*
amdgpu_resume failed (-110).
Oct 12 23:16:30 amn kernel: amdgpu 0000:01:00.0: ffff9514d9161800 unpin not
necessary
Regards
--
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2017-10-13 21:36 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-08 20:12 [Bug 196615] New: amdgpu - resume from suspend is no longer working on rx480 bugzilla-daemon
2017-08-08 20:14 ` [Bug 196615] " bugzilla-daemon
2017-08-08 20:15 ` bugzilla-daemon
2017-08-08 20:44 ` bugzilla-daemon
2017-08-09 21:20 ` bugzilla-daemon
2017-08-09 21:21 ` bugzilla-daemon
2017-08-13 10:48 ` bugzilla-daemon
2017-08-17 17:39 ` bugzilla-daemon
2017-08-17 20:12 ` bugzilla-daemon
2017-08-17 20:12 ` bugzilla-daemon
2017-08-17 20:22 ` bugzilla-daemon
2017-08-17 20:28 ` bugzilla-daemon
2017-08-17 20:32 ` bugzilla-daemon
2017-08-25 12:28 ` bugzilla-daemon
2017-08-25 14:18 ` bugzilla-daemon
2017-09-07 17:43 ` bugzilla-daemon
2017-09-07 17:58 ` bugzilla-daemon
2017-09-07 18:07 ` bugzilla-daemon
2017-09-28 7:32 ` bugzilla-daemon
2017-10-01 21:29 ` bugzilla-daemon
2017-10-02 7:04 ` bugzilla-daemon
2017-10-09 14:15 ` bugzilla-daemon
2017-10-12 14:48 ` bugzilla-daemon
2017-10-12 14:56 ` bugzilla-daemon
2017-10-12 15:09 ` bugzilla-daemon
2017-10-12 20:18 ` bugzilla-daemon
2017-10-13 6:03 ` bugzilla-daemon
2017-10-13 21:36 ` bugzilla-daemon [this message]
2017-10-14 9:59 ` bugzilla-daemon
2017-10-17 7:09 ` bugzilla-daemon
2017-10-20 14:09 ` bugzilla-daemon
2017-10-20 20:17 ` bugzilla-daemon
2017-10-20 22:18 ` bugzilla-daemon
2017-10-21 13:58 ` bugzilla-daemon
2017-10-29 23:15 ` bugzilla-daemon
2017-11-02 16:52 ` 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-196615-2300-AlZHSOMg6x@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.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.