dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
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: Tue, 08 Jan 2019 13:43:22 +0000	[thread overview]
Message-ID: <bug-108585-502-Yib0g7sQNM@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-108585-502@http.bugs.freedesktop.org/>


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

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

--- Comment #19 from Dan Horák <dan@danny.cz> ---
They (=
https://src.fedoraproject.org/fork/sharkcz/rpms/kernel/blob/talos/f/ppc64-talos-amdgpu-reset.patch)
can go upstream.

I have a 4.20 kernel on the host with recent firmware for polaris11, the
skiroot boot environment (4.15 IIRC) uses polaris11 firmware files from
20181015. The system boots OK in the skiroot kernel -> kexec -> host kernel
sequence.

The diff between the firmware sets is
--- a-old       2019-01-08 14:34:02.300578731 +0100
+++ a-new       2019-01-08 14:34:14.519024951 +0100
@@ -1,19 +1,21 @@
 5dc1006ce1896d997232b9165f2ce8ebad52a63c  polaris11_ce.bin
 193b0baaabf2a0a9e37a201a251013f26b0b70ee  polaris11_ce_2.bin
+8ee2e5db95fe589e8292642e638a15d1b8291bcb  polaris11_k_mc.bin
 cf2b8cd1d7f723f0edb6f17123711d6fa21ef379  polaris11_k_smc.bin
+a4ab9c0484cc9957112ab803d88e5b967c412c01  polaris11_k2_smc.bin
 f6551d45c0b652955009560bea1694c5ca86c1af  polaris11_mc.bin
 a3bfc83f5f52978365428e8756ed165655984a3b  polaris11_me.bin
 eb17beac2b09e25cfdc4662afc353f51a1c23272  polaris11_mec.bin
-c960ba31f13806c889d076bbe0b796281fdb0075  polaris11_mec_2.bin
+4e2290c5e030d6211168802fbe60db53b7c076c5  polaris11_mec_2.bin
 eb17beac2b09e25cfdc4662afc353f51a1c23272  polaris11_mec2.bin
-a13f4c7ce6e30ed930c7a5756196b24114247691  polaris11_mec2_2.bin
+f7956bba6312950db2de12336f79ccb28201593a  polaris11_mec2_2.bin
 a7fb9fab4529707592ce3dd449cd27fbf415fb94  polaris11_me_2.bin
 6377d75775fbe5353c8397ff03d230be0f4d6bcf  polaris11_pfp.bin
-af8c1b94170ada698379d1dab33924003ee525c0  polaris11_pfp_2.bin
+01eda59a1f159889d9a0ea2a9744eae4e09eaa1c  polaris11_pfp_2.bin
 38c512c82fe4773f33e53ba1ada414ddbe9b9e09  polaris11_rlc.bin
 82d8fcf56ac3051981b9e70199b115ed9d46995f  polaris11_sdma.bin
 8b21e98cb7e0ab000d131543c13a3ed95aa6687a  polaris11_sdma1.bin
 e01ac87abb011582d1da84eda9444353de082d11  polaris11_smc.bin
-6b804243472b5653ba449106426a0da1c46a9d84  polaris11_smc_sk.bin
+f8680ef51f84df00b388d9c230a28d150836ce08  polaris11_smc_sk.bin
 85a2f70f1f3b63e02a1bfbaba73a1729cee2104e  polaris11_uvd.bin
 a9abead599bb8497f38d587f682726a00bc067d2  polaris11_vce.bin

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

[-- Attachment #1.2: Type: text/html, Size: 3273 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:[~2019-01-08 13:43 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
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 [this message]

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-Yib0g7sQNM@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).