From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 108585] *ERROR* hw_init of IP block <gfx_v8_0> failed -22
Date: Wed, 31 Oct 2018 15:13:27 +0000 [thread overview]
Message-ID: <bug-108585-502-r8hZUrnKq4@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-108585-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1118 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=108585
--- Comment #14 from Alex Deucher <alexdeucher@gmail.com> ---
Created attachment 142303
--> https://bugs.freedesktop.org/attachment.cgi?id=142303&action=edit
possible fix
(In reply to Benjamin Herrenschmidt from comment #12)
> We have no control on what firmware is loaded by the target distro so the
> right thing is going to reset the adapter.
>
> We'll probably need to add something to the amdgpu shutdown() path to force
> an adapter reset.
Does the attached patch help? I'd been hesitant to add reset to the shutdown
path because it adds latency to the regular shutdown path and users complain
when that slows down.
>
> Do you have details of what specific PCIe config space write you use ? FLR ?
The reset sequence is asic specific. older parts just happened to use PCI
config space to trigger a GPU reset via an AMD specific sequence. Newer GPUs
reset via the PSP. FLR is only available on SR-IOV capable skus so it's not a
general solution.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2292 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
next prev parent reply other threads:[~2018-10-31 15:13 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-29 10:29 [Bug 108585] *ERROR* hw_init of IP block <gfx_v8_0> failed -22 bugzilla-daemon
2018-10-29 11:04 ` bugzilla-daemon
2018-10-29 12:58 ` bugzilla-daemon
2018-10-29 16:08 ` bugzilla-daemon
2018-10-30 3:39 ` bugzilla-daemon
2018-10-30 14:20 ` bugzilla-daemon
2018-10-30 23:17 ` bugzilla-daemon
2018-10-31 0:44 ` bugzilla-daemon
2018-10-31 7:40 ` bugzilla-daemon
2018-10-31 8:09 ` bugzilla-daemon
2018-10-31 8:12 ` bugzilla-daemon
2018-10-31 8:35 ` bugzilla-daemon
2018-10-31 9:31 ` bugzilla-daemon
2018-10-31 10:13 ` bugzilla-daemon
2018-10-31 15:13 ` bugzilla-daemon [this message]
2018-11-01 5:14 ` bugzilla-daemon
2018-11-01 9:49 ` bugzilla-daemon
2018-11-01 12:37 ` bugzilla-daemon
2018-12-14 20:46 ` bugzilla-daemon
2018-12-14 20:47 ` bugzilla-daemon
2019-01-08 13:43 ` 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-108585-502-r8hZUrnKq4@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;
as well as URLs for NNTP newsgroup(s).