AML-grabber floods system journal.

vevs · 19. Juni 2017

Hello! I use Hyperion on several S905(x) boxes with different versions of LibreElec installed, and i've faced the problem: with amlgrabber enabled there is enourmous amount of messages appears in the log during the video playback, and systemd-journal process consumes even more CPU's time than hyperiond itself. Please, could you help me solve this?

penfold42 · 19. Juni 2017

Got a sample of the logs ?

vevs · 19. Juni 2017

Oh, certainly! Sorry

"system log with amlgrabber enabled"

[ 1013.760868@2] codec:****************Into VIDTYPE_VIU_NV21******************
[ 1013.760878@2] codec:RGB_phy_addr:68200000
[ 1013.760887@2] codec:RGB_addr:ffffffc068200000
[ 1013.760912@2] codec:y_index=[0x60] u_index=[0x61] cur_index:626160
[ 1013.760924@2] codec:w=640-height=384 cur_index:626160
[ 1013.760933@2] codec:cd.addr:68200000
[ 1013.761864@2] codec:amvideocap_capture_one_frame: capture ok priv->want.fmt=16777728
[ 1013.761877@2] codec:amvideocap_capture_one_frame priv->state=300
[ 1013.761886@2] codec:amvideocap_capture_one_frame_wait ret=0
[ 1013.761898@2] codec:amvideocap_read=0,priv->state=300,priv->vaddr=ffffffc068200000
[ 1013.761917@2] codec:priv->out_width=160 priv->out_height=160
[ 1013.761927@2] codec: priv->outfmt_byteppix=3, size=76800
[ 1013.800317@2] codec:start amvideocap_read waitdelay=1000
[ 1013.800342@2] codec:amvideocap_capture_one_frame:start vf= (null),index=0
[ 1013.800356@2] codec:amvideocap_capture_one_frame: get vf type=9000
[ 1013.800369@2] codec:****************Into VIDTYPE_VIU_NV21******************
[ 1013.800379@2] codec:RGB_phy_addr:68200000
[ 1013.800387@2] codec:RGB_addr:ffffffc068200000
[ 1013.800406@2] codec:y_index=[0x10] u_index=[0x11] cur_index:121110
[ 1013.800424@2] codec:w=640-height=384 cur_index:121110
[ 1013.800434@2] codec:cd.addr:68200000
[ 1013.801157@2] codec:amvideocap_capture_one_frame: capture ok priv->want.fmt=16777728
[ 1013.801199@2] codec:amvideocap_capture_one_frame priv->state=300
[ 1013.801208@2] codec:amvideocap_capture_one_frame_wait ret=0
[ 1013.801220@2] codec:amvideocap_read=0,priv->state=300,priv->vaddr=ffffffc068200000
[ 1013.801230@2] codec:priv->out_width=160 priv->out_height=160
[ 1013.801239@2] codec: priv->outfmt_byteppix=3, size=76800
[ 1013.840106@2] codec:start amvideocap_read waitdelay=1000
[ 1013.840132@2] codec:amvideocap_capture_one_frame:start vf= (null),index=0
[ 1013.840145@2] codec:amvideocap_capture_one_frame: get vf type=9000
[ 1013.840158@2] codec:****************Into VIDTYPE_VIU_NV21******************
[ 1013.840177@2] codec:RGB_phy_addr:68200000
[ 1013.840186@2] codec:RGB_addr:ffffffc068200000
[ 1013.840204@2] codec:y_index=[0x60] u_index=[0x61] cur_index:626160
[ 1013.840216@2] codec:w=640-height=384 cur_index:626160
[ 1013.840225@2] codec:cd.addr:68200000
[ 1013.840951@2] codec:amvideocap_capture_one_frame: capture ok priv->want.fmt=16777728
[ 1013.840963@2] codec:amvideocap_capture_one_frame priv->state=300
[ 1013.840972@2] codec:amvideocap_capture_one_frame_wait ret=0
[ 1013.840984@2] codec:amvideocap_read=0,priv->state=300,priv->vaddr=ffffffc068200000
[ 1013.840995@2] codec:priv->out_width=160 priv->out_height=160
[ 1013.841004@2] codec: priv->outfmt_byteppix=3, size=76800
[ 1013.880744@2] codec:start amvideocap_read waitdelay=1000
[ 1013.880760@2] codec:amvideocap_capture_one_frame:start vf= (null),index=0
[ 1013.880767@2] codec:amvideocap_capture_one_frame: get vf type=9000

vevs · 5. Juli 2017

Seems like a kernel-related problem. Sorry for disturbing

danielfmo · 17. November 2017

Hi,

Just to let you know that this issue is fixed on latest commit to kernel used by libreelec : https://github.com/LibreELEC/l…779c15327b1c93ed4a2b48702

Jetzt mitmachen!