* [Bug 108585] *ERROR* hw_init of IP block <gfx_v8_0> failed -22
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
` (18 subsequent siblings)
19 siblings, 0 replies; 21+ messages in thread
From: bugzilla-daemon @ 2018-10-29 11:04 UTC (permalink / raw)
To: dri-devel
[-- Attachment #1.1: Type: text/plain, Size: 374 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=108585
--- Comment #1 from Michel Dänzer <michel@daenzer.net> ---
There were no amdgpu driver changes between rc8 and final... Are you sure this
is 100% reproducible with the latter and not reproducible with the former? If
so, can you bisect?
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1170 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
^ permalink raw reply [flat|nested] 21+ messages in thread
* [Bug 108585] *ERROR* hw_init of IP block <gfx_v8_0> failed -22
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
` (17 subsequent siblings)
19 siblings, 0 replies; 21+ messages in thread
From: bugzilla-daemon @ 2018-10-29 12:58 UTC (permalink / raw)
To: dri-devel
[-- Attachment #1.1: Type: text/plain, Size: 734 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=108585
--- Comment #2 from Dan Horák <dan@danny.cz> ---
(In reply to Michel Dänzer from comment #1)
> There were no amdgpu driver changes between rc8 and final... Are you sure
> this is 100% reproducible with the latter and not reproducible with the
> former? If so, can you bisect?
till now 100% reproduceable, will try bisecting the kernel sources and also
will look what else might have changed
for the record
- you can find the kernels at
https://copr.fedorainfracloud.org/coprs/sharkcz/talos-kernel/builds/
- amdgpu.dc=0 or 1 makes no difference (0 is my default value, see bug 107049)
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1820 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
^ permalink raw reply [flat|nested] 21+ messages in thread
* [Bug 108585] *ERROR* hw_init of IP block <gfx_v8_0> failed -22
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
` (16 subsequent siblings)
19 siblings, 0 replies; 21+ messages in thread
From: bugzilla-daemon @ 2018-10-29 16:08 UTC (permalink / raw)
To: dri-devel
[-- Attachment #1.1: Type: text/plain, Size: 436 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=108585
--- Comment #3 from Dan Horák <dan@danny.cz> ---
Ha, so it's the firmware stored in the initrds, what is different (lsinitrd
lied). And the latest polaris11* ones provoke the crash. When I manually
replaced them with the ones from the rc8 initrd, I've successfully booted into
the 4.19 GA kernel.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1222 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
^ permalink raw reply [flat|nested] 21+ messages in thread
* [Bug 108585] *ERROR* hw_init of IP block <gfx_v8_0> failed -22
2018-10-29 10:29 [Bug 108585] *ERROR* hw_init of IP block <gfx_v8_0> failed -22 bugzilla-daemon
` (2 preceding siblings ...)
2018-10-29 16:08 ` bugzilla-daemon
@ 2018-10-30 3:39 ` bugzilla-daemon
2018-10-30 14:20 ` bugzilla-daemon
` (15 subsequent siblings)
19 siblings, 0 replies; 21+ messages in thread
From: bugzilla-daemon @ 2018-10-30 3:39 UTC (permalink / raw)
To: dri-devel
[-- Attachment #1.1: Type: text/plain, Size: 589 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=108585
--- Comment #4 from Joel <joel.stan@gmail.com> ---
I see a similar backtrace on 4.19.0-11706-g11743c56785c (Linus' tree mid-merge
window).
My system has a "fiji" card. The first kernel is 4.19 (upstream release), and
the second kernel where the backtrace occurs is with 4.19+.
The second kernel is kexec'd from the first.
If I don't load amdgpu in the first kernel, the second kernel works. So there
is something missed in the shutdown path.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1386 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
^ permalink raw reply [flat|nested] 21+ messages in thread
* [Bug 108585] *ERROR* hw_init of IP block <gfx_v8_0> failed -22
2018-10-29 10:29 [Bug 108585] *ERROR* hw_init of IP block <gfx_v8_0> failed -22 bugzilla-daemon
` (3 preceding siblings ...)
2018-10-30 3:39 ` bugzilla-daemon
@ 2018-10-30 14:20 ` bugzilla-daemon
2018-10-30 23:17 ` bugzilla-daemon
` (14 subsequent siblings)
19 siblings, 0 replies; 21+ messages in thread
From: bugzilla-daemon @ 2018-10-30 14:20 UTC (permalink / raw)
To: dri-devel
[-- Attachment #1.1: Type: text/plain, Size: 618 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=108585
--- Comment #5 from Alex Deucher <alexdeucher@gmail.com> ---
(In reply to Joel from comment #4)
> I see a similar backtrace on 4.19.0-11706-g11743c56785c (Linus' tree
> mid-merge window).
>
> My system has a "fiji" card. The first kernel is 4.19 (upstream release),
> and the second kernel where the backtrace occurs is with 4.19+.
>
> The second kernel is kexec'd from the first.
Please file your own bug. Kexec is not likely to work and should be tracked
separately.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1514 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
^ permalink raw reply [flat|nested] 21+ messages in thread
* [Bug 108585] *ERROR* hw_init of IP block <gfx_v8_0> failed -22
2018-10-29 10:29 [Bug 108585] *ERROR* hw_init of IP block <gfx_v8_0> failed -22 bugzilla-daemon
` (4 preceding siblings ...)
2018-10-30 14:20 ` bugzilla-daemon
@ 2018-10-30 23:17 ` bugzilla-daemon
2018-10-31 0:44 ` bugzilla-daemon
` (13 subsequent siblings)
19 siblings, 0 replies; 21+ messages in thread
From: bugzilla-daemon @ 2018-10-30 23:17 UTC (permalink / raw)
To: dri-devel
[-- Attachment #1.1: Type: text/plain, Size: 945 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=108585
--- Comment #6 from Benjamin Herrenschmidt <benh@kernel.crashing.org> ---
They may or may not be related ... Alex, kexec is how we boot these machines,
there's a Linux kernel in flash that runs a Linux based bootloader.
Until recently however, that didn't have an amdgpu driver. This might have
changed.
Dan... did you do some firmware changes here ? Could it have to do with the
versions differences between petitboot and the final kernel ?
Alex, whether we track it here or separately, we probably need to look into
kexec support. It's not just us, there's a bit of momentum around kexec based
bootloaders (google's on it too) as was seen at the recent OSFC (firmware
conf).
A workaround in the meantime (for kexec problems) could be to hot reset the
card during the transition I suppose.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1755 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
^ permalink raw reply [flat|nested] 21+ messages in thread
* [Bug 108585] *ERROR* hw_init of IP block <gfx_v8_0> failed -22
2018-10-29 10:29 [Bug 108585] *ERROR* hw_init of IP block <gfx_v8_0> failed -22 bugzilla-daemon
` (5 preceding siblings ...)
2018-10-30 23:17 ` bugzilla-daemon
@ 2018-10-31 0:44 ` bugzilla-daemon
2018-10-31 7:40 ` bugzilla-daemon
` (12 subsequent siblings)
19 siblings, 0 replies; 21+ messages in thread
From: bugzilla-daemon @ 2018-10-31 0:44 UTC (permalink / raw)
To: dri-devel
[-- Attachment #1.1: Type: text/plain, Size: 557 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=108585
--- Comment #7 from Joel <joel.stan@gmail.com> ---
(In reply to Benjamin Herrenschmidt from comment #6)
> Dan... did you do some firmware changes here ? Could it have to do with the
> versions differences between petitboot and the final kernel ?
FWIW, Talos II machines use a fork of op-build that include the amdgpu driver
in petitboot. (They also appear to be stuck on 4.16).
I was experimenting with the same.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1418 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
^ permalink raw reply [flat|nested] 21+ messages in thread
* [Bug 108585] *ERROR* hw_init of IP block <gfx_v8_0> failed -22
2018-10-29 10:29 [Bug 108585] *ERROR* hw_init of IP block <gfx_v8_0> failed -22 bugzilla-daemon
` (6 preceding siblings ...)
2018-10-31 0:44 ` bugzilla-daemon
@ 2018-10-31 7:40 ` bugzilla-daemon
2018-10-31 8:09 ` bugzilla-daemon
` (11 subsequent siblings)
19 siblings, 0 replies; 21+ messages in thread
From: bugzilla-daemon @ 2018-10-31 7:40 UTC (permalink / raw)
To: dri-devel
[-- Attachment #1.1: Type: text/plain, Size: 434 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=108585
--- Comment #8 from Dan Horák <dan@danny.cz> ---
I should have mentioned I'm kexec-ing too. It's from 4.15.9 (in skiroot) to
Fedora kernels 4.16, 4.17, 4.18 and now 4.19 during the time. It worked fine
until the recent amdgpu firmware update. The skiroot kernel uses amdgpu
firmware from ~June.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1220 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
^ permalink raw reply [flat|nested] 21+ messages in thread
* [Bug 108585] *ERROR* hw_init of IP block <gfx_v8_0> failed -22
2018-10-29 10:29 [Bug 108585] *ERROR* hw_init of IP block <gfx_v8_0> failed -22 bugzilla-daemon
` (7 preceding siblings ...)
2018-10-31 7:40 ` bugzilla-daemon
@ 2018-10-31 8:09 ` bugzilla-daemon
2018-10-31 8:12 ` bugzilla-daemon
` (10 subsequent siblings)
19 siblings, 0 replies; 21+ messages in thread
From: bugzilla-daemon @ 2018-10-31 8:09 UTC (permalink / raw)
To: dri-devel
[-- Attachment #1.1: Type: text/plain, Size: 1412 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=108585
Christian König <ckoenig.leichtzumerken@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |NOTABUG
Status|NEW |RESOLVED
--- Comment #9 from Christian König <ckoenig.leichtzumerken@gmail.com> ---
(In reply to Benjamin Herrenschmidt from comment #6)
> They may or may not be related ... Alex, kexec is how we boot these
> machines, there's a Linux kernel in flash that runs a Linux based bootloader.
Yeah, you guys should have noted that because that combination is known to not
work correctly.
The problem is that some parts of the hardware are explicitly designed in a way
which only allows loading one firmware after an ASIC reset. So as long as kexec
doesn't makes a full PCIe level ASIC reset the second driver load is intended
to fail.
We have the same problem with virtualization and used to have a workaround in
KVM which triggers the ASIC reset with a PCIe config space write. Alex should
know the details.
Only solution I can see is to either use the same workaround as the KVM guys or
use the same firmware for both the loader and the final kernel.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3044 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
^ permalink raw reply [flat|nested] 21+ messages in thread
* [Bug 108585] *ERROR* hw_init of IP block <gfx_v8_0> failed -22
2018-10-29 10:29 [Bug 108585] *ERROR* hw_init of IP block <gfx_v8_0> failed -22 bugzilla-daemon
` (8 preceding siblings ...)
2018-10-31 8:09 ` bugzilla-daemon
@ 2018-10-31 8:12 ` bugzilla-daemon
2018-10-31 8:35 ` bugzilla-daemon
` (9 subsequent siblings)
19 siblings, 0 replies; 21+ messages in thread
From: bugzilla-daemon @ 2018-10-31 8:12 UTC (permalink / raw)
To: dri-devel
[-- Attachment #1.1: Type: text/plain, Size: 545 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=108585
Christian König <ckoenig.leichtzumerken@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |joel.stan@gmail.com
--- Comment #10 from Christian König <ckoenig.leichtzumerken@gmail.com> ---
*** Bug 108607 has been marked as a duplicate of this bug. ***
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2211 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
^ permalink raw reply [flat|nested] 21+ messages in thread
* [Bug 108585] *ERROR* hw_init of IP block <gfx_v8_0> failed -22
2018-10-29 10:29 [Bug 108585] *ERROR* hw_init of IP block <gfx_v8_0> failed -22 bugzilla-daemon
` (9 preceding siblings ...)
2018-10-31 8:12 ` bugzilla-daemon
@ 2018-10-31 8:35 ` bugzilla-daemon
2018-10-31 9:31 ` bugzilla-daemon
` (8 subsequent siblings)
19 siblings, 0 replies; 21+ messages in thread
From: bugzilla-daemon @ 2018-10-31 8:35 UTC (permalink / raw)
To: dri-devel
[-- Attachment #1.1: Type: text/plain, Size: 348 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=108585
--- Comment #11 from Dan Horák <dan@danny.cz> ---
Thanks for the info, I've documented that in the Talos wiki under
https://wiki.raptorcs.com/wiki/Troubleshooting/GPU#AMDGPU_driver_crashes_after_firmware_update
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1300 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
^ permalink raw reply [flat|nested] 21+ messages in thread
* [Bug 108585] *ERROR* hw_init of IP block <gfx_v8_0> failed -22
2018-10-29 10:29 [Bug 108585] *ERROR* hw_init of IP block <gfx_v8_0> failed -22 bugzilla-daemon
` (10 preceding siblings ...)
2018-10-31 8:35 ` bugzilla-daemon
@ 2018-10-31 9:31 ` bugzilla-daemon
2018-10-31 10:13 ` bugzilla-daemon
` (7 subsequent siblings)
19 siblings, 0 replies; 21+ messages in thread
From: bugzilla-daemon @ 2018-10-31 9:31 UTC (permalink / raw)
To: dri-devel
[-- Attachment #1.1: Type: text/plain, Size: 506 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=108585
--- Comment #12 from Benjamin Herrenschmidt <benh@kernel.crashing.org> ---
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.
Do you have details of what specific PCIe config space write you use ? FLR ?
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1373 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
^ permalink raw reply [flat|nested] 21+ messages in thread
* [Bug 108585] *ERROR* hw_init of IP block <gfx_v8_0> failed -22
2018-10-29 10:29 [Bug 108585] *ERROR* hw_init of IP block <gfx_v8_0> failed -22 bugzilla-daemon
` (11 preceding siblings ...)
2018-10-31 9:31 ` bugzilla-daemon
@ 2018-10-31 10:13 ` bugzilla-daemon
2018-10-31 15:13 ` bugzilla-daemon
` (6 subsequent siblings)
19 siblings, 0 replies; 21+ messages in thread
From: bugzilla-daemon @ 2018-10-31 10:13 UTC (permalink / raw)
To: dri-devel
[-- Attachment #1.1: Type: text/plain, Size: 1069 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=108585
--- Comment #13 from Christian König <ckoenig.leichtzumerken@gmail.com> ---
(In reply to Benjamin Herrenschmidt from comment #12)
> We'll probably need to add something to the amdgpu shutdown() path to force
> an adapter reset.
If that would be possible we would have already done that.
The problem is that you do a full ASIC reset. So not only the GPU is affected,
but also bridges, sound codecs etc... If any of those parts have a driver
loaded while you do the reset you usually crash the system.
Additional to that AFAIK this doesn't work on APUs. Because there the GPU is
part of the CPU and so you would need to to reset both.
How about stopping to use amdgpu in the boot loader? For just displaying a
splash screen vesafb or efifb should do fine as well.
> Do you have details of what specific PCIe config space write you use ? FLR ?
Alex knows the details of that, but a FLR alone doesn't work AFAIK.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2044 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
^ permalink raw reply [flat|nested] 21+ messages in thread
* [Bug 108585] *ERROR* hw_init of IP block <gfx_v8_0> failed -22
2018-10-29 10:29 [Bug 108585] *ERROR* hw_init of IP block <gfx_v8_0> failed -22 bugzilla-daemon
` (12 preceding siblings ...)
2018-10-31 10:13 ` bugzilla-daemon
@ 2018-10-31 15:13 ` bugzilla-daemon
2018-11-01 5:14 ` bugzilla-daemon
` (5 subsequent siblings)
19 siblings, 0 replies; 21+ messages in thread
From: bugzilla-daemon @ 2018-10-31 15:13 UTC (permalink / raw)
To: dri-devel
[-- 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
^ permalink raw reply [flat|nested] 21+ messages in thread
* [Bug 108585] *ERROR* hw_init of IP block <gfx_v8_0> failed -22
2018-10-29 10:29 [Bug 108585] *ERROR* hw_init of IP block <gfx_v8_0> failed -22 bugzilla-daemon
` (13 preceding siblings ...)
2018-10-31 15:13 ` bugzilla-daemon
@ 2018-11-01 5:14 ` bugzilla-daemon
2018-11-01 9:49 ` bugzilla-daemon
` (4 subsequent siblings)
19 siblings, 0 replies; 21+ messages in thread
From: bugzilla-daemon @ 2018-11-01 5:14 UTC (permalink / raw)
To: dri-devel
[-- Attachment #1.1: Type: text/plain, Size: 469 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=108585
--- Comment #15 from Alex Deucher <alexdeucher@gmail.com> ---
Created attachment 142316
--> https://bugs.freedesktop.org/attachment.cgi?id=142316&action=edit
more involved fix
These patches attempt to reset the GPU on init if the GPU was already running
from a previous load of the driver. Compile tested only at the moment.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1449 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
^ permalink raw reply [flat|nested] 21+ messages in thread
* [Bug 108585] *ERROR* hw_init of IP block <gfx_v8_0> failed -22
2018-10-29 10:29 [Bug 108585] *ERROR* hw_init of IP block <gfx_v8_0> failed -22 bugzilla-daemon
` (14 preceding siblings ...)
2018-11-01 5:14 ` bugzilla-daemon
@ 2018-11-01 9:49 ` bugzilla-daemon
2018-11-01 12:37 ` bugzilla-daemon
` (3 subsequent siblings)
19 siblings, 0 replies; 21+ messages in thread
From: bugzilla-daemon @ 2018-11-01 9:49 UTC (permalink / raw)
To: dri-devel
[-- Attachment #1.1: Type: text/plain, Size: 425 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=108585
--- Comment #16 from Dan Horák <dan@danny.cz> ---
Reset on init sounds better to me as the loader kernel (in kexec case) is more
difficult to update than the host kernel.
And for the record - after updating the skiroot kernel firmware version to the
latest there is no problem/crash.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1268 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
^ permalink raw reply [flat|nested] 21+ messages in thread
* [Bug 108585] *ERROR* hw_init of IP block <gfx_v8_0> failed -22
2018-10-29 10:29 [Bug 108585] *ERROR* hw_init of IP block <gfx_v8_0> failed -22 bugzilla-daemon
` (15 preceding siblings ...)
2018-11-01 9:49 ` bugzilla-daemon
@ 2018-11-01 12:37 ` bugzilla-daemon
2018-12-14 20:46 ` bugzilla-daemon
` (2 subsequent siblings)
19 siblings, 0 replies; 21+ messages in thread
From: bugzilla-daemon @ 2018-11-01 12:37 UTC (permalink / raw)
To: dri-devel
[-- Attachment #1.1: Type: text/plain, Size: 332 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=108585
--- Comment #17 from Dan Horák <dan@danny.cz> ---
Fedora/ppc64le users can find a pre-built kernel with the patchset at
https://copr.fedorainfracloud.org/coprs/sharkcz/talos-kernel/build/817728/
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1264 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
^ permalink raw reply [flat|nested] 21+ messages in thread
* [Bug 108585] *ERROR* hw_init of IP block <gfx_v8_0> failed -22
2018-10-29 10:29 [Bug 108585] *ERROR* hw_init of IP block <gfx_v8_0> failed -22 bugzilla-daemon
` (16 preceding siblings ...)
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
19 siblings, 0 replies; 21+ messages in thread
From: bugzilla-daemon @ 2018-12-14 20:46 UTC (permalink / raw)
To: dri-devel
[-- Attachment #1.1: Type: text/plain, Size: 466 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=108585
--- Comment #18 from Alex Deucher <alexdeucher@gmail.com> ---
(In reply to Dan Horák from comment #17)
> Fedora/ppc64le users can find a pre-built kernel with the patchset at
> https://copr.fedorainfracloud.org/coprs/sharkcz/talos-kernel/build/817728/
Should these patches go upstream? Can you confirm they fix your issues?
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1484 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
^ permalink raw reply [flat|nested] 21+ messages in thread
* [Bug 108585] *ERROR* hw_init of IP block <gfx_v8_0> failed -22
2018-10-29 10:29 [Bug 108585] *ERROR* hw_init of IP block <gfx_v8_0> failed -22 bugzilla-daemon
` (17 preceding siblings ...)
2018-12-14 20:46 ` bugzilla-daemon
@ 2018-12-14 20:47 ` bugzilla-daemon
2019-01-08 13:43 ` bugzilla-daemon
19 siblings, 0 replies; 21+ messages in thread
From: bugzilla-daemon @ 2018-12-14 20:47 UTC (permalink / raw)
To: dri-devel
[-- Attachment #1.1: Type: text/plain, Size: 469 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=108585
Alex Deucher <alexdeucher@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
See Also| |https://bugs.freedesktop.or
| |g/show_bug.cgi?id=108754
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1164 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
^ permalink raw reply [flat|nested] 21+ messages in thread
* [Bug 108585] *ERROR* hw_init of IP block <gfx_v8_0> failed -22
2018-10-29 10:29 [Bug 108585] *ERROR* hw_init of IP block <gfx_v8_0> failed -22 bugzilla-daemon
` (18 preceding siblings ...)
2018-12-14 20:47 ` bugzilla-daemon
@ 2019-01-08 13:43 ` bugzilla-daemon
19 siblings, 0 replies; 21+ messages in thread
From: bugzilla-daemon @ 2019-01-08 13:43 UTC (permalink / raw)
To: dri-devel
[-- 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
^ permalink raw reply [flat|nested] 21+ messages in thread