9

Development - [Kernel][03.05.2023][Android 13.0.0]Kirisakura 1.0.4_Raviantah for...

 1 year ago
source link: https://forum.xda-developers.com/t/kernel-03-05-2023-android-13-0-0-kirisakura-1-0-4_raviantah-for-pixel-6-pro-aka-raviole.4358435/page-146#post-88493319
Go to the source link to view the article. You can view the picture content, updated content and better typesetting reading experience. If the link is broken, please click the button below to view the snapshot at that time.
neoserver,ios ssh client

Development [Kernel][03.05.2023][Android 13.0.0]Kirisakura 1.0.4_Raviantah for Pixel 6/Pro aka "RAVIOLE"

knopie

Member
Can I use the version 1.03_1 with the May update?

Psfanboy88

Senior Member
Can I use the version 1.03_1 with the May update?

Using it since yesterday. No problems so far.

Reactions: Admiral2145

Freak07

Recognized Developer / Recognized Contributor
First of all, big thanks for taking the time to run all those kernel and provide the logs!
Still seeing this same reboot with the newest 1.0.3_1

That´s another issue that´s not kernel related. system_server asked the phone to reboot and it did.

Code: 
[159797.496289][  T398] init: Received sys.powerctl='reboot,' from pid: 17399 (system_server)
Unrelated to the kernel, but there are a few interesting things in the log.
com.github.catfriend1.syncthingandroid

This app gets blocked by selinux from trying to do something:
com.github.catfriend1.syncthingandroid

I don´t know if that hinders functionality of the app, but it might be worth reporting to the developer.
Code: 
[158294.144307][  T484] type=1400 audit(1682893329.755:131121): avc: denied { bind } for comm="libsyncthingnat" scontext=u:r:untrusted_app:s0:c119,c257,c512,c768 tcontext=u:r:untrusted_app:s0:c119,c257,c512,c768 tclass=netlink_route_socket permissive=0 bug=b/155595000 app=com.github.catfriend1.syncthingandroid
[158294.144477][  T484] type=1400 audit(1682893329.755:131122): avc: denied { bind } for comm="libsyncthingnat" scontext=u:r:untrusted_app:s0:c119,c257,c512,c768 tcontext=u:r:untrusted_app:s0:c119,c257,c512,c768 tclass=netlink_route_socket permissive=0 bug=b/155595000 app=com.github.catfriend1.syncthingandroid
[158294.146105][  T484] type=1400 audit(1682893329.759:131123): avc: denied { bind } for comm="libsyncthingnat" scontext=u:r:untrusted_app:s0:c119,c257,c512,c768 tcontext=u:r:untrusted_app:s0:c119,c257,c512,c768 tclass=netlink_route_socket permissive=0 bug=b/155595000 app=com.github.catfriend1.syncthingandroid
[158294.146404][  T484] type=1400 audit(1682893329.759:131124): avc: denied { bind } for comm="libsyncthingnat" scontext=u:r:untrusted_app:s0:c119,c257,c512,c768 tcontext=u:r:untrusted_app:s0:c119,c257,c512,c768 tclass=netlink_route_socket permissive=0 bug=b/155595000 app=com.github.catfriend1.syncthingandroid
[158294.147839][  T484] type=1400 audit(1682893329.759:131125): avc: denied { bind } for comm="libsyncthingnat" scontext=u:r:untrusted_app:s0:c119,c257,c512,c768 tcontext=u:r:untrusted_app:s0:c119,c257,c512,c768 tclass=netlink_route_socket permissive=0 bug=b/155595000 app=com.github.catfriend1.syncthingandroid
Just before system_server asked the phone to reboot, selinux denials like the following started spamming:
Code: 
[159614.745699][  T398] init: Unable to set property 'persist.vendor.shutdown.voltage_avg' from uid:1000 gid:1000 pid:1045: SELinux permission check failed
[159614.753898][  T398] init: Unable to set property 'persist.vendor.shutdown.voltage_avg' from uid:1000 gid:1000 pid:1045: SELinux permission check failed
Strikes me as odd, but I´ll investigate because it makes me curious.
Another crash. This time pretty much immediately after booting up.

Hm, not directly after booting though. Happened at timestamp

[ 2021.018661][T18540] Unable to handle kernel paging request at virtual address fffffffffbeffffe

and again throughout the entire log I can see

Code: 
[   30.357401][  T389] init: Unable to set property 'persist.vendor.shutdown.voltage_avg' from uid:1000 gid:1000 pid:1050: SELinux permission check failed
[   30.381491][  T389] init: Unable to set property 'persist.vendor.shutdown.voltage_avg' from uid:1000 gid:1000 pid:1050: SELinux permission check failed
Code: 
[   30.338863][  T477] type=1107 audit(1683072813.530:440): uid=0 auid=4294967295 ses=4294967295 subj=u:r:init:s0 msg='avc: denied { set } for property=persist.vendor.shutdown.voltage_avg pid=1050 uid=1000 gid=1000 scontext=u:r:hal_health_default:s0 tcontext=u:object_r:vendor_default_prop:s0 tclass=property_service permissive=0'
Just before the reboot your phone was thermally throttled
Code: 
[ 2005.186887][  T209] ppm/mpmm thermal throttling enable!
[ 2005.186900][  T209] Set ppm throttle to 0x66
[ 2005.186902][  T209] Set mpmm throttle to 0x10
[ 2005.186909][  T210] BIG: enable hard limit
[ 2005.186940][  T210] BIG: thermal-cpufreq-2 set cur_state to hardlimit cooling state 16, is_hardlimited = 1, pid swithed_on = 1
[ 2005.199524][  T209] ppm/mpmm thermal throttling disable!
[ 2005.199550][  T209] Set ppm throttle to 0x0
[ 2005.199557][  T209] Set mpmm throttle to 0x1a
[ 2005.199608][  T210] BIG: clear hard limit, is_hardlimited = 0, pid swithed_on = 1
Again this strikes me as odd, there are loads of other errors that I don´t see on my logs at all.

Is your phone hot? Did it do any very expensive task?
Do you use any mods that modify thermal limits?

It's really strange you're getting the issue extremely frequently. So I'm beginning to suspect it happens when something is already not running well and when the device is under stress that particular issue seems to happen more likely.
Of course nothing should crash the kernel even if things are borked from framework/userspace/apps etc, that's why I spend so much time around the issue.


So a few questions:

Are you running stock firmware from google or a custom rom?
Are you using any mods? If so, which mods magisk modules or other things do you use?
Which charger do you have connected on both logs? Is it just connected to your PC?

report

Recommend

About Joyk


Aggregate valuable and interesting links.
Joyk means Joy of geeK