when you refer to API traces, you're suggesting to strace
kodi, or what do you mean?
What I meant was apitrace (https://github.com/apitrace/apitrace), but when even the lightdm login screen crashes than this won't be much helpful.

That strongly sounds like a ARM specific problem, maybe USWC doesn't work as it should? See function drm_arch_can_wc_memory() in the kernel source and try if it helps if you always return false.

Apart from that the only other explanation I have is that some system memory isn't accessible for the GPU while some other is working fine.

Please provide the output of "sudo cat /proc/iomem" to double check that.

Regards,
Christian.

Am 02.01.2018 um 14:09 schrieb Luís Mendes:
Dear Mr. David, Mr. Christian,

First of all, thanks for your replies!

David, I will try the same software versions on x86 to see if I am
able to replicate the problem on x86, but I suspect it is ARM
specific... I'll report back when I have more details.

Christian, I'll collect the data you've referred and will disable the
power management. Regarding the mesa master version, I've tried it,
and the problem just gets worse. With latest mesa, It easily locks up
in lightdm login screen, or when navigating through the Ubuntu Mate
menus, or with Kodi.  I've tested with mesa commit "radv: Implement
binning on GFX9" - 6a36bfc64d2096aa338958c4605f5fc6372c07b8. Just one
question... when you refer to API traces, you're suggesting to strace
kodi, or what do you mean?

Regards,
Luís

On Tue, Jan 2, 2018 at 2:51 AM, Chunming Zhou <[email protected]> wrote:
Did you try it on x86 board? Is there same issue?

We should identify it is ARM specific or genera issue for amdgpu driver.


Thanks,

David Zhou




_______________________________________________
amd-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/amd-gfx

Reply via email to