Enabling IKS after boot crashes Android
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Linaro big.LITTLE |
Fix Released
|
High
|
vishal |
Bug Description
If an IKS enabled Android kernel is booted with IKS off and then it is turned on after boot with:
echo 1 >/sys/kernel/
then some seconds later the ActivityManager dies, causing all of Android services to be shutdown and restarted. See attached log. Subsequent toggling of IKS off and on doesn't seem to cause problems again.
I speculate that Android doesn't cope with the change of CPU topology when IKS is first enabled, e.g. the number of cpus goes from 5 to 2 but it could be trying to still get stats for all 5 cpus leading to the array bounds failure in the log.
Observed on the 13.05 release candidate candidate build: https:/
Changed in linaro-big-little-system: | |
importance: | Undecided → High |
status: | New → Confirmed |
Changed in linaro-big-little-system: | |
assignee: | nobody → vishal (vishalbhoj) |
Changed in linaro-big-little-system: | |
status: | Confirmed → Fix Committed |
Changed in linaro-big-little-system: | |
status: | Fix Committed → Fix Released |
root@android:/ # echo 0 > /sys/kernel/ bL_switcher/ active bL_switcher/ active bL_switcher/ active bL_switcher/ active naresh- kamboju@ hackbox: ~$ kamboju@ hackbox: ~$
root@android:/ # echo 1 > /sys/kernel/
root@android:/ # echo 0 > /sys/kernel/
root@android:/ # echo 0 > /sys/kernel/
naresh-