mesa-22.3.0-devel + linux-5.19.6 + mediapipe: panfrost js fault

Robin Murphy robin.murphy at arm.com
Tue Sep 6 12:06:01 UTC 2022


On 2022-09-04 05:13, Chris Ruehl wrote:
> Hi,
> 
> Something you might have a head up for it,
> 
> have a mediapipe application for POSE which use the T860 GPU for the 
> calculation
> but the kernel driver report error (js fault) - I see one or 2 
> calculation frames on the mat-picture output only before
> the pipe stop working.
> 
> Linux bullseye64 5.19.6 #1 SMP PREEMPT Fri Sep 2 02:25:59 UTC 2022 
> aarch64 GNU/Linux
> 
> [    5.164415] panfrost ff9a0000.gpu: clock rate = 500000000
> [    5.169845] panfrost ff9a0000.gpu: [drm:panfrost_devfreq_init 
> [panfrost]] Failed to register cooling device
> [    5.169989] panfrost ff9a0000.gpu: mali-t860 id 0x860 major 0x2 minor 
> 0x0 status 0x0
> [    5.169999] panfrost ff9a0000.gpu: features: 00000000,00000407, 
> issues: 00000000,24040400
> [    5.170008] panfrost ff9a0000.gpu: Features: L2:0x07120206 
> Shader:0x00000000 Tiler:0x00000809 Mem:0x1 MMU:0x00002830 AS:0xff JS:0x7
> [    5.170017] panfrost ff9a0000.gpu: shader_present=0xf l2_present=0x1
> [    5.206827] [drm] Initialized panfrost 1.2.0 20180908 for 
> ff9a0000.gpu on minor 1
> ...
> [  162.862064] panfrost ff9a0000.gpu: js fault, js=1, 
> status=DATA_INVALID_FAULT, head=0xaba7100, tail=0xaba7100
> [  162.862269] panfrost ff9a0000.gpu: js fault, js=1, 
> status=DATA_INVALID_FAULT, head=0xa1e0100, tail=0xa1e0100
> 
> Have a RK3399 customized board and compiled the mesa drivers for it
> 
> meson $1 . build/ \
> -D dri-drivers= \
> -D vulkan-drivers= \
> -D gallium-drivers=panfrost,kmsro \
> -D llvm=disabled \
> -D libunwind=false \
> -D platforms=x11,wayland
> 
> glmark2 runs flawless scores 588.
> 
> Same code run on a x86_64 with an AMD GPU working fine.
> 
> Anything help fix the bug is welcome.

This is almost certainly a userspace problem, so you're best off raising 
a Mesa issue with some more details - an apitrace of the failing 
application and/or PAN_MESA_DEBUG=trace output capturing the offending 
invalid descriptors would probably be a good starting point.

Robin.


More information about the dri-devel mailing list