Closed rinigus closed 1 year ago
I wonder whether it is possible to disable fast frequency switching for power-efficient CPUs.
I was able to trigger crashes with 100% "success" rates on AOSP as follows:
Test 1
In this case, fast switching is disabled on policy0 CPUs, but not on policy4 (observing dmesg).
Example of pstore record after crash using AOSP10:
[ 128.106507] water_detection soc:somc_water_detection: wdet_check_water_work:set powerrole fail
[ 128.425742] dsi-ctrl:[dsi_ctrl_handle_error_status] tx timeout error: 0x40
[ 130.226086] BUG: scheduling while atomic: kworker/3:2/856/0x00000004
[ 130.226402] ------------[ cut here ]------------
[ 130.226528] WARNING: CPU: 3 PID: 856 at /awork/android/R_MR1/kernel/sony/msm-4.14/kernel/kernel/rcu/tree_plugin.h:329 rcu_note_context_switch+0x468/0x50c
[ 130.226894] ---[ end trace 417e3f5e72d734d7 ]---
Test 2
Crash can be triggered by first switching to schedutil on policy4 and then policy0. In this case, dmesg points to disabling fast switching on policy4, but not policy0
Conclusion
As is, schedutil cannot be used on AOSP10
Discontinued Android version
Platform: Tama Device: Akari Kernel version: 4.14.232-gd88c66b3138a Android version: android-10.0.0_r41 - Sailfish 4.1.0.24 Software binaries version: SW_binaries_for_Xperia_Android_10.0.7.1_r1_v12a_tama
Previously working on
No idea
Description
First observed on SFOS port, but have been able to reproduce on AOSP10 as well. Looks like crash is reproducible for
When switching
/sys/devices/system/cpu/cpufreq/policy0
toschedutil
, phone sometimes crashes. It is almost always on SFOS, on AOSP10 I managed to hit it once. It does look to correlate with dmesg messageWhen fast frequency is not enabled, phone stays stable. Without it, it crashes.
How to reproduce
Crash logs
From AOSP
pstore
after crash:Bit more in SFOS journal: