• State Not Answered
  • Locked Locked
  • Replies 4 replies
  • Subscribers 120 subscribers
  • Views 2800 views
  • Users 0 members are here
2025 survey

We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.

Options
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Mali G52 - Failed to create reader for mali GPU # 0

Qing Xia

Streamline version: Version 8.0.0, Build 20220217_150925 windows 64-bit.

Device: Mali G52(Bifrost - r21p0)  on Android.

If any GPU perf counters are selected from "Add counters from a template", the capture will not start with:  

If I capture without any mali counters selected, I can successfully get a capture(with only CPU info).

Parents
  • 0 Arm Employee Badge

    Hi ; can you please provide a debug log from gatord. You can do so as follows:

    adb push <streamline-install>/bin/arm64/gatord /data/local/tmp/
    adb shell /data/local/tmp/gatord -d -S no -A find / 1> /data/local/tmp/gatord.log 2>&1

    < try counter configuration, you may need to use the TCP/Advanced view in Streamline rather than the Android view >

    < stop gatord with ctrl-c, once the above error message is seen >

    adb pull /data/local/tmp/gatord.log

    This file should help identify the reason for the failure.

    Thanks
    Ben

Reply
  • 0 Arm Employee Badge

    Hi ; can you please provide a debug log from gatord. You can do so as follows:

    adb push <streamline-install>/bin/arm64/gatord /data/local/tmp/
    adb shell /data/local/tmp/gatord -d -S no -A find / 1> /data/local/tmp/gatord.log 2>&1

    < try counter configuration, you may need to use the TCP/Advanced view in Streamline rather than the Android view >

    < stop gatord with ctrl-c, once the above error message is seen >

    adb pull /data/local/tmp/gatord.log

    This file should help identify the reason for the failure.

    Thanks
    Ben

Children
  • 0 in reply to Ben Gainey

    Hi Ben,

    Thank you for your reply.

    I cannot find out how to upload the full log here. :( 

    I am posting what I think is relevant here:

    [56634.1078929] DEBUG: #23473 (mali_userspace/MaliDeviceApi.cpp:234): MaliDeviceApi: Failed setting ABI version ioctl - may be r21p0 or later...
    [56634.1079485] DEBUG: #23473 (mali_userspace/MaliDeviceApi.cpp:550): MaliDeviceApi: ABI version: 11.17
    [56634.1116110] SETUP: #23473 (mali_userspace/MaliDeviceApi.cpp:88): Mali GPU counters
    Successfully probed Mali device /dev/mali0 as Mali-G52 (0x7402 r1p0), 2 L2 Slices, 128-bit Bus, 6 Shader Cores (sparse layout, mask is 0x77).
    [56634.5433418] DEBUG: #23473 (mali_userspace/MaliHwCntrDriver.cpp:54): Added counter 'ARM_Mali-TGOx_MESSAGES_SENT' @ 0 4
    [56634.5434768] DEBUG: #23473 (mali_userspace/MaliHwCntrDriver.cpp:54): Added counter 'ARM_Mali-TGOx_MESSAGES_RECEIVED' @ 0 5
    [56634.5435168] DEBUG: #23473 (mali_userspace/MaliHwCntrDriver.cpp:54): Added counter 'ARM_Mali-TGOx_GPU_ACTIVE' @ 0 6

    ......(Other counter probe infomation)

    [56656.2503618] DEBUG: #23896 (Child.cpp:346): Started ext_source agent
    [56656.2503846] DEBUG: #23895 (Child.cpp:358): Waiting for agent complete
    [56656.2505191] DEBUG: #23895 (mali_userspace/MaliDeviceApi.cpp:479): MaliDeviceApi: Failed sending hwcnt reader ioctl
    [56656.2505678] DEBUG: #23895 (mali_userspace/MaliDeviceApi.cpp:479): MaliDeviceApi: Failed sending hwcnt reader ioctl

    ......(repeat "Failed sending hwcnt reader ioctl" about 1000 times)

    [56656.2908737] DEBUG: #23895 (mali_userspace/MaliDeviceApi.cpp:479): MaliDeviceApi: Failed sending hwcnt reader ioctl
    [56656.2909118] DEBUG: #23895 (mali_userspace/MaliDeviceApi.cpp:479): MaliDeviceApi: Failed sending hwcnt reader ioctl
    [56656.2909513] ERROR: #23895 (mali_userspace/MaliHwCntrSource.cpp:52): Failed to create reader for mali GPU # 0. Please try again, and if this happens repeatedly please try rebooting your device.
    [56656.2910466] DEBUG: #23895 (Sender.cpp:115): Sending data with length 124

    I hope this is enough for you to identify the reason. If not, I'll try somehow upload the full log.

  • 0 Arm Employee Badge in reply to Qing Xia

    Just to confirm - have you tried power cycling the device? 

    Cheers, 
    Pete

  • 0 in reply to Peter Harris

    Tried reboot the device. Same problem.

    Thank you.