From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 215436] admgpu: suspend and resuming from suspend don't work
Date: Mon, 03 Jan 2022 10:29:48 +0000 [thread overview]
Message-ID: <bug-215436-2300-NZL96Cox51@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-215436-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=215436
--- Comment #14 from spasswolf@web.de ---
Created attachment 300212
--> https://bugzilla.kernel.org/attachment.cgi?id=300212&action=edit
dmesg with linux-5.16-rc8 while ignoring adev->in_s0ix
Simply ignoring the value of adev->in_s0ix and calling reset anyway does not
work either:
Jan 3 11:23:51 lisa kernel: [ 32.649142] amdgpu 0000:08:00.0: amdgpu:
amdgpu_device_suspend(...) = 0
Jan 3 11:23:51 lisa kernel: [ 32.649146] amdgpu 0000:08:00.0: amdgpu:
adev->in_s0ix = 1
Jan 3 11:23:51 lisa kernel: [ 32.649149] amdgpu 0000:08:00.0: amdgpu: MODE2
reset
Jan 3 11:23:51 lisa kernel: [ 37.404614] amdgpu 0000:08:00.0: amdgpu: Mode2
reset failed!
Jan 3 11:23:51 lisa kernel: [ 37.404616] PM: pci_pm_suspend():
amdgpu_pmops_suspend+0x0/0x60 [amdgpu] returns -62
Jan 3 11:23:51 lisa kernel: [ 37.404733] PM: dpm_run_callback():
pci_pm_suspend+0x0/0x150 returns -62
--
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:[~2022-01-03 10:29 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-29 12:28 [Bug 215436] New: admgpu: suspend and resuming from suspend don't work bugzilla-daemon
2021-12-29 15:08 ` [Bug 215436] " bugzilla-daemon
2021-12-29 15:10 ` bugzilla-daemon
2021-12-30 13:03 ` bugzilla-daemon
2021-12-30 13:16 ` bugzilla-daemon
2021-12-30 14:33 ` bugzilla-daemon
2021-12-31 0:17 ` bugzilla-daemon
2021-12-31 0:22 ` bugzilla-daemon
2021-12-31 15:10 ` bugzilla-daemon
2021-12-31 16:14 ` bugzilla-daemon
2022-01-01 1:42 ` bugzilla-daemon
2022-01-03 9:29 ` bugzilla-daemon
2022-01-03 9:35 ` bugzilla-daemon
2022-01-03 9:36 ` bugzilla-daemon
2022-01-03 10:20 ` bugzilla-daemon
2022-01-03 10:29 ` bugzilla-daemon [this message]
2022-01-03 15:48 ` bugzilla-daemon
2022-01-03 17:12 ` bugzilla-daemon
2022-01-03 17:49 ` bugzilla-daemon
2022-01-03 17:51 ` bugzilla-daemon
2022-01-04 10:17 ` bugzilla-daemon
2022-01-04 10:25 ` bugzilla-daemon
2022-01-04 11:15 ` bugzilla-daemon
2022-01-04 11:27 ` bugzilla-daemon
2022-01-04 14:14 ` bugzilla-daemon
2022-01-04 14:59 ` bugzilla-daemon
2022-01-04 15:03 ` bugzilla-daemon
2022-01-04 15:27 ` bugzilla-daemon
2022-01-04 15:28 ` bugzilla-daemon
2022-01-24 22:45 ` bugzilla-daemon
2022-01-25 20:25 ` 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-215436-2300-NZL96Cox51@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).