From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 209457] AMDGPU resume fail with RX 580 GPU
Date: Sat, 15 May 2021 17:48:14 +0000 [thread overview]
Message-ID: <bug-209457-2300-MIHamsNRNT@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-209457-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=209457
Marius (marius.andreiana@gmail.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |marius.andreiana@gmail.com
--- Comment #22 from Marius (marius.andreiana@gmail.com) ---
With 5.12.3, monitor remains blank after resume.
Relevant log:
```
May 15 20:21:37 fedora kernel: amdgpu 0000:04:00.0: amdgpu: failed to write reg
28b4 wait reg 28c6
May 15 20:21:37 fedora kernel: amdgpu 0000:04:00.0: amdgpu: failed to write reg
1a6f4 wait reg 1a706
May 15 20:21:37 fedora kernel: amdgpu 0000:04:00.0: amdgpu: SMU is resuming...
May 15 20:21:37 fedora kernel: amdgpu 0000:04:00.0: amdgpu: dpm has been
disabled
May 15 20:21:37 fedora kernel: amdgpu 0000:04:00.0: amdgpu: SMU is resumed
successfully!
May 15 20:21:37 fedora kernel: amdgpu 0000:04:00.0:
[drm:amdgpu_ring_test_helper [amdgpu]] *ERROR* ring sdma0 test failed (-110)
May 15 20:21:37 fedora kernel: [drm:amdgpu_device_ip_resume_phase2 [amdgpu]]
*ERROR* resume of IP block <sdma_v4_0> failed -110
May 15 20:21:37 fedora kernel: amdgpu 0000:04:00.0: amdgpu:
amdgpu_device_ip_resume failed (-110).
May 15 20:21:37 fedora kernel: amdgpu 0000:04:00.0: PM: failed to resume async:
error -110
May 15 20:21:37 fedora kernel: amdgpu 0000:04:00.0: amdgpu: couldn't schedule
ib on ring <sdma0>
May 15 20:21:37 fedora kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error
scheduling IBs (-22)
May 15 20:21:37 fedora kernel: amdgpu 0000:04:00.0: amdgpu: couldn't schedule
ib on ring <sdma0>
May 15 20:21:37 fedora kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error
scheduling IBs (-22)
May 15 20:21:47 fedora kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring
gfx timeout, signaled seq=139973, emitted seq=139977
May 15 20:21:47 fedora kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR*
Process information: process gnome-shell pid 1895 thread gnome-shel:cs0 pid
1926
May 15 20:21:47 fedora kernel: amdgpu 0000:04:00.0: amdgpu: GPU reset begin!
May 15 20:21:47 fedora kernel: amdgpu 0000:04:00.0:
[drm:amdgpu_ring_test_helper [amdgpu]] *ERROR* ring kiq_2.1.0 test failed
(-110)
May 15 20:21:47 fedora kernel: amdgpu 0000:04:00.0: amdgpu: MODE2 reset
May 15 20:21:47 fedora kernel: amdgpu 0000:04:00.0: amdgpu: GPU reset
succeeded, trying to resume
May 15 20:21:48 fedora kernel: amdgpu 0000:04:00.0: amdgpu: RAS: optional ras
ta ucode is not available
May 15 20:21:48 fedora kernel: amdgpu 0000:04:00.0: amdgpu: RAP: optional rap
ta ucode is not available
May 15 20:21:48 fedora kernel: amdgpu 0000:04:00.0: amdgpu: SECUREDISPLAY:
securedisplay ta ucode is not available
May 15 20:21:48 fedora kernel: amdgpu 0000:04:00.0: amdgpu: SMU is resuming...
May 15 20:21:48 fedora kernel: amdgpu 0000:04:00.0: amdgpu: dpm has been
disabled
May 15 20:21:48 fedora kernel: amdgpu 0000:04:00.0: amdgpu: SMU is resumed
successfully!
May 15 20:21:48 fedora kernel: amdgpu 0000:04:00.0:
[drm:amdgpu_ring_test_helper [amdgpu]] *ERROR* ring sdma0 test failed (-110)
May 15 20:21:48 fedora kernel: [drm:amdgpu_device_ip_resume_phase2 [amdgpu]]
*ERROR* resume of IP block <sdma_v4_0> failed -110
May 15 20:21:48 fedora kernel: amdgpu 0000:04:00.0: amdgpu: GPU reset(2) failed
May 15 20:21:48 fedora kernel: amdgpu 0000:04:00.0: amdgpu: GPU reset end with
ret = -110
May 15 20:21:58 fedora kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring
gfx timeout, but soft recovered
May 15 20:22:08 fedora kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring
gfx timeout, but soft recovered
May 15 20:22:12 fedora kernel: amdgpu 0000:04:00.0: amdgpu: couldn't schedule
ib on ring <sdma0>
May 15 20:22:12 fedora kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error
scheduling IBs (-22)
May 15 20:22:12 fedora kernel: amdgpu 0000:04:00.0: amdgpu: couldn't schedule
ib on ring <sdma0>
```
AMD Ryzen 7 4700U with Radeon Graphics, Lenovo Ideapad 5.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2021-05-15 17:48 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-01 17:15 [Bug 209457] New: AMDGPU resume fail with RX 580 GPU bugzilla-daemon
2020-10-01 17:56 ` [Bug 209457] " bugzilla-daemon
2020-10-01 18:36 ` bugzilla-daemon
2020-10-01 18:56 ` bugzilla-daemon
2020-10-01 19:36 ` bugzilla-daemon
2020-10-02 1:25 ` bugzilla-daemon
2020-10-02 1:26 ` bugzilla-daemon
2020-10-14 20:07 ` bugzilla-daemon
2020-10-14 20:36 ` bugzilla-daemon
2020-10-14 21:08 ` bugzilla-daemon
2020-10-15 22:54 ` bugzilla-daemon
2020-10-29 23:11 ` bugzilla-daemon
2020-10-29 23:35 ` bugzilla-daemon
2020-10-29 23:41 ` bugzilla-daemon
2020-10-30 0:09 ` bugzilla-daemon
2020-11-11 16:51 ` bugzilla-daemon
2020-11-11 16:53 ` bugzilla-daemon
2020-11-11 16:54 ` bugzilla-daemon
2020-12-12 10:43 ` bugzilla-daemon
2020-12-12 11:21 ` bugzilla-daemon
2020-12-23 18:15 ` bugzilla-daemon
2021-03-05 14:35 ` bugzilla-daemon
2021-03-05 15:34 ` bugzilla-daemon
2021-05-15 17:48 ` bugzilla-daemon [this message]
2021-06-01 17:51 ` bugzilla-daemon
2021-06-01 20:21 ` bugzilla-daemon
2021-06-15 22:08 ` bugzilla-daemon
2021-06-16 20:57 ` bugzilla-daemon
2021-06-16 20:58 ` bugzilla-daemon
2021-06-18 18:22 ` bugzilla-daemon
2021-06-22 17:16 ` bugzilla-daemon
2021-06-30 19:01 ` bugzilla-daemon
2021-07-05 16:56 ` bugzilla-daemon
2021-07-06 13:44 ` bugzilla-daemon
2021-07-06 17:31 ` bugzilla-daemon
2021-07-14 14:51 ` bugzilla-daemon
2021-07-14 14:54 ` bugzilla-daemon
2021-07-14 14:55 ` bugzilla-daemon
2021-07-14 17:56 ` bugzilla-daemon
2021-07-14 18:43 ` bugzilla-daemon
2021-07-15 13:35 ` 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-209457-2300-MIHamsNRNT@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 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).