Missing syscalls 278 and 384?

[Quallenauge]

From @vladimiroltean on February 17, 2018 0:16

Dmesg is full of messages such as this one:

[ 3482.569025] ChromiumNet[5641]: syscall 384
[ 3482.569037] Code: e1a01002 e1a02003 e89c0078 ef000000 (e8bd00f0) 
[ 3482.569045] CPU: 1 PID: 5641 Comm: ChromiumNet Tainted: G        W    3.10.84-perf-g963993a-00043-g4fe9981-dirty #1
[ 3482.569052] task: ffffffc04aa369c0 ti: ffffffc087870000 task.ti: ffffffc087870000
[ 3482.569058] PC is at 0xe774f4ec
[ 3482.569062] LR is at 0xc944f643
[ 3482.569066] pc : [<00000000e774f4ec>] lr : [<00000000c944f643>] pstate: 20070010
[ 3482.569070] sp : 00000000c8fc0f08
[ 3482.569073] x12: 00000000c8fc0f18 
[ 3482.569077] x11: 00000000c950b5e4 x10: 0000000000000000 
[ 3482.569082] x9 : 00000000ffffffff x8 : 0000000000000001 
[ 3482.569087] x7 : 0000000000000180 x6 : 00000000c95cfb88 
[ 3482.569092] x5 : 0000000000000010 x4 : 0000000000000001 
[ 3482.569096] x3 : 0000000000000000 x2 : 0000000000000001 
[ 3482.569101] x1 : 0000000000000001 x0 : 00000000c8fc0f1f

What do they mean? Is there any performance/functionality impact?

Copied from original issue: Quallenauge/Yoga-Tab-3-Plus-Issue-Tracker#10

[Quallenauge]

From @Gabriel85 on February 17, 2018 0:29

Is that with Oreo? Doesn't seem to use the proper kernel, at least..

On 17 February 2018 01:16:58 CET, Vladimir Oltean notifications@github.com wrote:

Dmesg is full of messages such as this one:

[ 3482.569025] ChromiumNet[5641]: syscall 384
[ 3482.569037] Code: e1a01002 e1a02003 e89c0078 ef000000 (e8bd00f0) 
[ 3482.569045] CPU: 1 PID: 5641 Comm: ChromiumNet Tainted: G        W  
3.10.84-perf-g963993a-00043-g4fe9981-dirty #1
[ 3482.569052] task: ffffffc04aa369c0 ti: ffffffc087870000 task.ti:
ffffffc087870000
[ 3482.569058] PC is at 0xe774f4ec
[ 3482.569062] LR is at 0xc944f643
[ 3482.569066] pc : [<00000000e774f4ec>] lr : [<00000000c944f643>]
pstate: 20070010
[ 3482.569070] sp : 00000000c8fc0f08
[ 3482.569073] x12: 00000000c8fc0f18 
[ 3482.569077] x11: 00000000c950b5e4 x10: 0000000000000000 
[ 3482.569082] x9 : 00000000ffffffff x8 : 0000000000000001 
[ 3482.569087] x7 : 0000000000000180 x6 : 00000000c95cfb88 
[ 3482.569092] x5 : 0000000000000010 x4 : 0000000000000001 
[ 3482.569096] x3 : 0000000000000000 x2 : 0000000000000001 
[ 3482.569101] x1 : 0000000000000001 x0 : 00000000c8fc0f1f

What do they mean? Is there any performance/functionality impact?

-- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/Quallenauge/Yoga-Tab-3-Plus-Issue-Tracker/issues/10

[Quallenauge]

From @vladimiroltean on February 17, 2018 0:37

cm-14.1-caf-LA.BR.1.3.6-04510-8976.0. Nougat.

[Quallenauge]

From @Gabriel85 on February 17, 2018 0:42

We are only doing Oreo development here. Also there will be a new kernel, which is based on your original idea, upstream fixes, and a lot less Lenovo crap. Just got delayed forever because of that endless cam problems..

On 17 February 2018 01:37:18 CET, Vladimir Oltean notifications@github.com wrote:

cm-14.1-caf-LA.BR.1.3.6-04510-8976.0. Nougat.

-- You are receiving this because you commented. Reply to this email directly or view it on GitHub: https://github.com/Quallenauge/Yoga-Tab-3-Plus-Issue-Tracker/issues/10#issuecomment-366398279

[Quallenauge]

I also see this logs on oreo. Thought it is not finished yet, but it seems a generic problem!?

[Quallenauge]

From @Gabriel85 on February 17, 2018 9:22

What is that? Probably Webview? I don't see that on mine, but I don't have Webview installed.. Anyways, yes I think it is a generic problem with LOS. Maybe somebody could check that with another device with LOS..

On 17 February 2018 09:52:16 CET, Quallenauge notifications@github.com wrote:

I also see this logs on oreo. Thought it is not finished yet, but it seems a generic problem!?

-- You are receiving this because you commented. Reply to this email directly or view it on GitHub: https://github.com/Quallenauge/Yoga-Tab-3-Plus-Issue-Tracker/issues/10#issuecomment-366427385

[Quallenauge]

Not only restricted to chromium, but also to dex2oat,...

➜  lenovo  adb shell dmesg | grep syscall
[   14.839569] app_process32[395]: syscall 384
[   15.431165] app_process32[395]: syscall 384
[   15.532207] android.hardwar[442]: syscall 384
[   15.533319] android.hardwar[444]: syscall 384
[   15.537397] android.hardwar[446]: syscall 384
[   15.684311] android.hardwar[444]: syscall 384
[   15.728111] android.hardwar[446]: syscall 384
[   15.733936] android.hardwar[442]: syscall 384
[   16.186481] audioserver[505]: syscall 384
[   16.186618] cameraserver[506]: syscall 384
[   16.187401] android.hardwar[516]: syscall 384
[   16.188429] mediaserver[513]: syscall 384
[   16.193644] drmserver[507]: syscall 384
[   16.198229] mediadrmserver[510]: syscall 384
[   16.258922] mm-qcamera-daem[524]: syscall 384
[   16.399459] mediadrmserver[510]: syscall 384
[   16.419984] android.hardwar[516]: syscall 384
[   16.706263] drmserver[507]: syscall 384
[   21.474188] do_ni_syscall: 4 callbacks suppressed
[   21.481236] main[395]: syscall 384
[   22.821093] webview_zygote3[3134]: syscall 384
[   22.824466] der-armeabi-v7a[3106]: syscall 384
[   22.826533] der-armeabi-v7a[3106]: syscall 384
[   23.191343] webview_zygote3[3134]: syscall 384
[   37.383616] android.vending[4311]: syscall 384
[   41.025811] dex2oat[5068]: syscall 384
[   41.036382] ChromiumNet[4345]: syscall 384
[   41.119202] dex2oat[5068]: syscall 384
[   41.362620] dex2oat[5136]: syscall 384
[   41.382341] dex2oat[5136]: syscall 384
[   41.809123] .android.videos[5226]: syscall 384
[   42.225447] tunein.player[5289]: syscall 384
[  176.857586] dex2oat[5827]: syscall 384
[  176.874417] dex2oat[5827]: syscall 384
[  181.427969] t_app_installer[5862]: syscall 384

[Quallenauge]

From @Gabriel85 on February 17, 2018 10:33

OK, found the problem: it happens when apps want to access a function called "getrandom()", which is only implemented since kernel version 3.17. Not critical since, there is a alternative function available. Syscall 278 is also not supported on 3.10. Can be closed.

On 17 February 2018 10:35:12 CET, Quallenauge notifications@github.com wrote:

Not only restricted to chromium, but also to dex2oat,...

➜  lenovo  adb shell dmesg | grep syscall
[   14.839569] app_process32[395]: syscall 384
[   15.431165] app_process32[395]: syscall 384
[   15.532207] android.hardwar[442]: syscall 384
[   15.533319] android.hardwar[444]: syscall 384
[   15.537397] android.hardwar[446]: syscall 384
[   15.684311] android.hardwar[444]: syscall 384
[   15.728111] android.hardwar[446]: syscall 384
[   15.733936] android.hardwar[442]: syscall 384
[   16.186481] audioserver[505]: syscall 384
[   16.186618] cameraserver[506]: syscall 384
[   16.187401] android.hardwar[516]: syscall 384
[   16.188429] mediaserver[513]: syscall 384
[   16.193644] drmserver[507]: syscall 384
[   16.198229] mediadrmserver[510]: syscall 384
[   16.258922] mm-qcamera-daem[524]: syscall 384
[   16.399459] mediadrmserver[510]: syscall 384
[   16.419984] android.hardwar[516]: syscall 384
[   16.706263] drmserver[507]: syscall 384
[   21.474188] do_ni_syscall: 4 callbacks suppressed
[   21.481236] main[395]: syscall 384
[   22.821093] webview_zygote3[3134]: syscall 384
[   22.824466] der-armeabi-v7a[3106]: syscall 384
[   22.826533] der-armeabi-v7a[3106]: syscall 384
[   23.191343] webview_zygote3[3134]: syscall 384
[   37.383616] android.vending[4311]: syscall 384
[   41.025811] dex2oat[5068]: syscall 384
[   41.036382] ChromiumNet[4345]: syscall 384
[   41.119202] dex2oat[5068]: syscall 384
[   41.362620] dex2oat[5136]: syscall 384
[   41.382341] dex2oat[5136]: syscall 384
[   41.809123] .android.videos[5226]: syscall 384
[   42.225447] tunein.player[5289]: syscall 384
[  176.857586] dex2oat[5827]: syscall 384
[  176.874417] dex2oat[5827]: syscall 384
[  181.427969] t_app_installer[5862]: syscall 384

-- You are receiving this because you commented. Reply to this email directly or view it on GitHub: https://github.com/Quallenauge/Yoga-Tab-3-Plus-Issue-Tracker/issues/10#issuecomment-366429397

[Quallenauge]

What can be done, to resonable silence these messages? They spamming the dmesg buffer....

[Quallenauge]

From @Gabriel85 on February 18, 2018 17:35

Mhh only at boot I think. But I can remove them if you want? Already did that with some other nasty ones.

On 18 February 2018 18:25:58 CET, Quallenauge notifications@github.com wrote:

What can be done, to resonable silence these messages? They spamming the dmesg buffer....

-- You are receiving this because you commented. Reply to this email directly or view it on GitHub: https://github.com/Quallenauge/Yoga-Tab-3-Plus-Issue-Tracker/issues/10#issuecomment-366531853

[Quallenauge]

From @Gabriel85 on July 9, 2018 7:1

fixed with new kernel..