dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 103102] Cannot wake-up with an AMD RX 480 on Linux 4.13 and Linux 4.14
Date: Thu, 05 Oct 2017 19:11:11 +0000	[thread overview]
Message-ID: <bug-103102-502-0Dcu674Sbv@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-103102-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 1137 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=103102

--- Comment #2 from Hadrien <freedesktop@psydk.org> ---
I tried several kernels:

4.12.4: OK
4.12.5: OK
4.12.6: FAIL, but after 20 seconds the monitor displays something: pure garbage
4.12.7: FAIL, the monitor stays OFF

I'll attach the kernel logs.

Interesting part in 4.12.6:

Oct  5 20:56:21 c18 kernel: [   37.277968] [drm:amdgpu_vce_ring_test_ring
[amdgpu]] *ERROR* amdgpu: ring 13 test failed
Oct  5 20:56:21 c18 kernel: [   37.277976] [drm:amdgpu_resume [amdgpu]] *ERROR*
resume of IP block <vce_v3_0> failed -110
Oct  5 20:56:21 c18 kernel: [   37.277983] [drm:amdgpu_device_resume [amdgpu]]
*ERROR* amdgpu_resume failed (-110).
Oct  5 20:56:21 c18 kernel: [   37.277985] dpm_run_callback():
pci_pm_resume+0x0/0xa0 returns -110
Oct  5 20:56:21 c18 kernel: [   37.277986] PM: Device 0000:01:00.0 failed to
resume async: error -110

There is a slight difference with more recent kernels, where the message
mentions ring 14 instead of ring 13 and some other functions too.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 1949 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2017-10-05 19:11 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-04 18:52 [Bug 103102] Cannot wake-up with an AMD RX 480 on Linux 4.13 and Linux 4.14 bugzilla-daemon
2017-10-05 18:34 ` bugzilla-daemon
2017-10-05 19:11 ` bugzilla-daemon [this message]
2017-10-05 19:12 ` bugzilla-daemon
2017-10-05 19:12 ` bugzilla-daemon
2017-10-05 19:25 ` bugzilla-daemon
2017-10-09 19:47 ` bugzilla-daemon
2017-10-11 17:00 ` bugzilla-daemon
2017-10-11 17:14 ` bugzilla-daemon
2017-10-11 19:54 ` bugzilla-daemon
2017-10-13 20:11 ` bugzilla-daemon
2017-10-14 16:57 ` bugzilla-daemon
2017-10-21  8:05 ` bugzilla-daemon
2017-12-07 22:08 ` bugzilla-daemon
2017-12-08 13:50 ` 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-103102-502-0Dcu674Sbv@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox