From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 208835] amdgpu fails to resume from suspend
Date: Fri, 30 Oct 2020 16:31:21 +0000 [thread overview]
Message-ID: <bug-208835-2300-NuBInlMsUN@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-208835-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=208835
Tom (tom@collider.in) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tom@collider.in
--- Comment #3 from Tom (tom@collider.in) ---
I am also affected by this. There are a few recent amdgpu suspend bugs open but
this one is most similar.
My card is a Radeon R7 260X (Bonaire XTX [Radeon R7 260X/360]), so I'm using
the experimental amdgpu driver support.
5.4.58 works,
5.4.72 does not,
5.9.1 does not.
My computer seems to be completely unresponsive after resuming. I haven't tried
SSHing but it does not respond to pressing the power button to put it back into
sleep. However there are systemd service logs in the journal after resume.
Kernel messages of note, which are not part of working logs:
18:14:26 amdgpu: [powerplay]
failed to send message 5e ret is 0
18:14:26 amdgpu: [powerplay]
failed to send message 145 ret is 0
------------------
18:14:26 [drm:uvd_v4_2_start [amdgpu]] *ERROR* UVD not responding, trying to
reset the VCPU!!!
18:14:26 [drm:uvd_v4_2_start [amdgpu]] *ERROR* UVD not responding, giving up!!!
18:14:26 [drm:amdgpu_device_ip_set_powergating_state [amdgpu]] *ERROR*
set_powergating_state of IP block <uvd_v4_2> failed -1
------------------
18:14:26 amdgpu 0000:01:00.0: [drm:amdgpu_ring_test_helper [amdgpu]] *ERROR*
ring uvd test failed (-110)
18:14:26 [drm:amdgpu_device_ip_resume_phase2 [amdgpu]] *ERROR* resume of IP
block <uvd_v4_2> failed -110
18:14:26 [drm:amdgpu_device_resume [amdgpu]] *ERROR* amdgpu_device_ip_resume
failed (-110).
18:14:26 PM: dpm_run_callback(): pci_pm_resume+0x0/0xe0 returns -110
18:14:26 PM: Device 0000:01:00.0 failed to resume async: error -110
------------------
18:14:27 [drm] Fence fallback timer expired on ring sdma0
Full journalctl from after resume attached.
--
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:[~2020-10-30 16:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-06 14:27 [Bug 208835] New: amdgpu fails to resume from suspend bugzilla-daemon
2020-08-06 14:38 ` [Bug 208835] " bugzilla-daemon
2020-08-07 14:04 ` bugzilla-daemon
2020-10-30 16:31 ` bugzilla-daemon [this message]
2020-10-30 16:33 ` bugzilla-daemon
2022-07-07 20:48 ` bugzilla-daemon
2022-07-08 7:27 ` bugzilla-daemon
2022-07-08 16:03 ` 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-208835-2300-NuBInlMsUN@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.