Sure thing!
Tracing it out, it seems to happen after the function
psp_v11_0_ring_set_wptr is called, but I'm having trouble figuring out
*why* the timing is messing it up. It also runs fine if any print
statements are called before amdgpu_device_ip_init, however DRMDEBUG has to
be disabled. It
On Mon, Nov 30, 2020 at 12:02:15AM -0600, Charlie Burnett wrote:
> Doesn’t DRM_INFO output even if DRMDEBUG is enabled? I thought DRM_DEBUG
> only output when debug’s enabled while DRM_INFO is pretty much just a
> wrapper for printk?
Currently DRM_INFO will call into printk which returns early
Doesn’t DRM_INFO output even if DRMDEBUG is enabled? I thought DRM_DEBUG
only output when debug’s enabled while DRM_INFO is pretty much just a
wrapper for printk?
Either way, I found the call writing to the GPU register it doesn’t like
earlier this weekend, but haven’t figured out what exactly
On Sun, Nov 29, 2020 at 10:17:22PM -0600, Charlie Burnett wrote:
> Howdy all,
> For reasons that are beyond me, when printf is called in amdgpu_device.c to
> print the CU info, it gives me a psp firmware load failure on a Radeon VII
> (Vega 20) gpu. Switching the printf statement to a DRM_INFO
Howdy all,
For reasons that are beyond me, when printf is called in amdgpu_device.c to
print the CU info, it gives me a psp firmware load failure on a Radeon VII
(Vega 20) gpu. Switching the printf statement to a DRM_INFO statement as
used in the rest of amdgpu seems to fix it though.
ok?
diff
