• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 99 subscribers
  • Views 554 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

TDA2HG: 3D GPU SGX544 SrvInit failed (24) [47, /pvrsrvinit.c]

Mukund Jadhav64
Prodigy 50 points
Part Number: TDA2HG


Hi,

In one production fail at Client, the following errors from GPU was observed :

----------------------------------------------------------------------------------------------------

PVR_K: (FAIL) SGXInit: Unable to validate device DDK version
PVR:(Error): PVRSRVInitSrvDisconnect: KM returned 24 [2638, /bridged_pvr_glue.c]
PVR:(Error): PVRSRVBridgeCall: Failed to access device. Function ID:3223086861 (Bad address). [294, /pvr_bridge_u.c]
PVR:(Error): SrvInit: P[ 9.127164] DMA: Module install successful, device major num = 248
VRSRVInitSrvDisconnect failed (24). See srvkm lo[ 9.137745] DRV: Module install successful
g for details. [135, /srvinit.c]
PVR:(Error): m[ 9.145803] DRV: Module built on Jan 23 2020 19:58:43
ain: SrvInit failed (24) [47, /pvrsrvinit.c]

-------------------------------------------------------------------------------------------------

Please find attached the complete log.

terminalTDA2x@RT.#1.txt

Is this a GPU hw issue ?

Which other hw issues can make the initialization fail ?

How to debug for exact cause?

Thank you.

Best Regards,

Mukund

  • 0
    TI__Mastermind 30480 points

    Hi Mukund,

    The log shows there is some compatibility mismatch between sgx-km and sgx-um. 

    Compiler options used for sgx-km and sgx-um seems different. The dmesg log says sgx-km is in debug mode. As TI releases always release-mode sgx-um binaries this could be the issue for the failure.

    Is the issue observed consistently or sometimes?

    Do you have any idea of commit-id of sgx-km and sgx-um used in the system? Please share the same if you have.

    Thanks

    RamPrasad

  • 0 in reply to Ramprasad
    TI__Prodigy 50 points

    Hi RamPrasad,

    Can you please elaborate on compatibility mismatch between sgx-km and sgx-um. I could not make it out from the log.

    Also How does the Compiler options used for sgx-km and sgx-um seem different?

    Where does the log say sgx-km is in debug mode?

    Thanks 

    Mukund

  • 0 in reply to Mukund Jadhav64
    TI__Mastermind 30480 points

    Hi Mukund,

    Default sgx-us binaries available is built with BUILD=release, but the log you shared has some PVR_K prints in sgx-km which suggests , sgx-kernel modules are built with a different options(BUILD=debug and may be some more).

    Please try to get information on what compiler options are used to build sgx-km.

    Thanks

    RamPrasad