RK3399 Legacy Multimedia Framework


JMCC

Recommended Posts

I'm trying this on my Helios64 RK3399 system but I'm getting severe glitches and missing 'tiles', many long pauses and freezes in the desktop and a bunch of GPU errors and soft resets in the logs. I actually wanted to run Kodi but upon investigating 3-5 seconds pauses when using the GUI I discovered the desktop is also affected. Interestingly video plays fine in Kodi, it's moving around any menu functions triggers the issue.

 

I installed the Buster legacy 4.4.213-rk3399 image and then the MM Framework with recommended packages and rebooted. There is no HDMI port on the Helios64 board so I'm using a USB-C DP->HDMI adapter which works fine on the basic installation. Trouble started after installing the MM Framework.

 

Syslog has a bunch of errors similar to:

 

[   80.234576] mali ff9a0000.gpu: Unhandled Page fault in AS0 at VA 0x0000008016D17F00
               Reason: Memory is not mapped on the GPU
               raw fault status: 0xF002C0
               decoded fault status: SLAVE FAULT
               exception type 0xC0: TRANSLATION_FAULT
               access type 0x2: READ
               source id 0xF0
               pid: 2412
[   80.234721] mali ff9a0000.gpu: error detected from slot 0, job status 0x00000004 (TERMINATED)
[   80.236756] mali ff9a0000.gpu: t6xx: GPU fault 0x4002 from job slot 0
[   85.344471] mali ff9a0000.gpu: JS: Job Hard-Stopped (took more than 50 ticks at 100 ms/tick)
[   85.844538] mali ff9a0000.gpu: JS: Job has been on the GPU for too long (JS_RESET_TICKS_SS/DUMPING timeout hit). Issueing GPU soft-reset to resolve.
[   85.844578] mali ff9a0000.gpu: Preparing to soft-reset GPU: Waiting (upto 3000 ms) for all jobs to complete soft-stop
[   88.844625] mali ff9a0000.gpu: Resetting GPU (allowing up to 500 ms)
[   88.844647] mali ff9a0000.gpu: Register state:
[   88.844656] mali ff9a0000.gpu:   GPU_IRQ_RAWSTAT=0x00000200 GPU_STATUS=0x00000009
[   88.844665] mali ff9a0000.gpu:   JOB_IRQ_RAWSTAT=0x00000000 JOB_IRQ_JS_STATE=0x00000001
[   88.844673] mali ff9a0000.gpu:   JS0_STATUS=0x00000008      JS0_HEAD_LO=0x96825100
[   88.844682] mali ff9a0000.gpu:   JS1_STATUS=0x00000000      JS1_HEAD_LO=0x9650c100
[   88.844691] mali ff9a0000.gpu:   JS2_STATUS=0x00000000      JS2_HEAD_LO=0x00000000
[   88.844699] mali ff9a0000.gpu:   MMU_IRQ_RAWSTAT=0x00000000 GPU_FAULTSTATUS=0x00000000
[   88.844708] mali ff9a0000.gpu:   GPU_IRQ_MASK=0x00000000    JOB_IRQ_MASK=0x00000000     MMU_IRQ_MASK=0x00000000
[   88.844717] mali ff9a0000.gpu:   PWR_OVERRIDE0=0x00000000   PWR_OVERRIDE1=0x00000000
[   88.844725] mali ff9a0000.gpu:   SHADER_CONFIG=0x00010000   L2_MMU_CONFIG=0x00000000
[   88.844734] mali ff9a0000.gpu:   TILER_CONFIG=0x00000001    JM_CONFIG=0x00000038
[   88.844840] mali ff9a0000.gpu: t6xx: GPU fault 0x4002 from job slot 0
[   88.844854] mali ff9a0000.gpu: Reset complete
[   88.965817] mali ff9a0000.gpu: Unhandled Page fault in AS0 at VA 0x000000800F91C700
               Reason: Memory is not mapped on the GPU
               raw fault status: 0xF002C0
               decoded fault status: SLAVE FAULT
               exception type 0xC0: TRANSLATION_FAULT
               access type 0x2: READ
               source id 0xF0
               pid: 2412

[  113.438992] mali ff9a0000.gpu: JS: Job Hard-Stopped (took more than 50 ticks at 100 ms/tick)
[  113.939036] mali ff9a0000.gpu: JS: Job has been on the GPU for too long (JS_RESET_TICKS_SS/DUMPING timeout hit). Issueing GPU soft-reset to resolve.
[  113.939078] mali ff9a0000.gpu: Preparing to soft-reset GPU: Waiting (upto 3000 ms) for all jobs to complete soft-stop
[  116.939136] mali ff9a0000.gpu: Resetting GPU (allowing up to 500 ms)
[  116.939157] mali ff9a0000.gpu: Register state:
[  116.939166] mali ff9a0000.gpu:   GPU_IRQ_RAWSTAT=0x00000200 GPU_STATUS=0x00000009
[  116.939175] mali ff9a0000.gpu:   JOB_IRQ_RAWSTAT=0x00000000 JOB_IRQ_JS_STATE=0x00000003
[  116.939183] mali ff9a0000.gpu:   JS0_STATUS=0x00000008      JS0_HEAD_LO=0x9c05e240
[  116.939192] mali ff9a0000.gpu:   JS1_STATUS=0x00000008      JS1_HEAD_LO=0x9c3c2100
[  116.939201] mali ff9a0000.gpu:   JS2_STATUS=0x00000000      JS2_HEAD_LO=0x00000000
[  116.939209] mali ff9a0000.gpu:   MMU_IRQ_RAWSTAT=0x00000000 GPU_FAULTSTATUS=0x00000000
[  116.939218] mali ff9a0000.gpu:   GPU_IRQ_MASK=0x00000000    JOB_IRQ_MASK=0x00000000     MMU_IRQ_MASK=0x00000000
[  116.939226] mali ff9a0000.gpu:   PWR_OVERRIDE0=0x00000000   PWR_OVERRIDE1=0x00000000
[  116.939235] mali ff9a0000.gpu:   SHADER_CONFIG=0x00010000   L2_MMU_CONFIG=0x00000000
[  116.939243] mali ff9a0000.gpu:   TILER_CONFIG=0x00000001    JM_CONFIG=0x00000038
[  116.939299] mali ff9a0000.gpu: t6xx: GPU fault 0x4002 from job slot 0
[  116.939370] mali ff9a0000.gpu: t6xx: GPU fault 0x4002 from job slot 1
[  116.939453] mali ff9a0000.gpu: Reset complete
[  116.939641] mali ff9a0000.gpu: t6xx: GPU fault 0x4002 from job slot 0

 

 

I'm not sure where to go next so looking for the clue bus...

 

Link to post
Share on other sites
Armbian is a community driven open source project. Do you like to contribute your code?

16 hours ago, TheGuv said:

which works fine on the basic installation. Trouble started after installing the MM Framework.

Please "armbianmonitor -u" of the basic installation and also after installing the multimedia integration

Link to post
Share on other sites
04.01.2021 в 12:18, JMCC сказал:

What are the steps you follow in Libreelec to enable that feature?  Can you do the same in our Kodi?

LE uses its own settings management system (including audio), which consists of many different additional components (these are not components of KODI itself). For Armbian + mediascript, you must first set the necessary settings in the system (if the system supports them, not all settings are possible in Armbian) and then switch to KODI. In Armbian, the KODI application is limited in setting different hardware settings, it uses system settings.

Link to post
Share on other sites
1 hour ago, balbes150 said:

LE uses its own settings management system

Yes, that was my guess. But I wanted the user to do some homework and check it for himself. I personally don't own any surround audio equipment, so if he cares for the feature, he will need to contribute some effort. Otherwise, I won't care either to implement it.

Link to post
Share on other sites
22 hours ago, JMCC said:

I tried to reproduce on my NanoPC-t4, but USB-C DP out does not work out of the box, at least with my adapter. I'll need to debug and fix that before getting into the mali issue.

 

OK, that's unlucky. I bought two and only one worked. Good luck and let me know if I can help in any way.

Link to post
Share on other sites
17 hours ago, Dee Cheung said:

My Helios64 have the same issue, I use Google USB Type-C to HDMI Adapter.

Sorry, my USB-C to DP/HDMI converter is broken, and I have no plans to make room in my budget for a new one, at least for now. So I cannot debug or fix this problem.

 

TBH, I am very surprised there is people using the Helios64 as a desktop device, I always considered it a NAS :)

Link to post
Share on other sites
1 hour ago, JMCC said:

Sorry, my USB-C to DP/HDMI converter is broken, and I have no plans to make room in my budget for a new one, at least for now. So I cannot debug or fix this problem.

 

TBH, I am very surprised there is people using the Helios64 as a desktop device, I always considered it a NAS :)

Not only as a NAS, but also as a media server.:P

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...