• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [LINARO] AWEstruck v1.04 12/14/14 | [3.4.107] v1.05b6 5/30/15

Having done some reading ... Seems like some ZTE and some other manufacturers don't play well with roms/kernels built with Linaro...just some food for thought.
 
starkraving said:
Not bad at all..
nazyra4e.jpg
Click to expand...

Which benchmarking tool do u use?
 
I've tried both the linaro and Google compiled 1.02 kernels and I get constant reboots even when I'm at stock speeds. I did change the governor to Wheatley and SIO. 1.01a worked great for me. I have one of those phones that would not boot with the oc kernel rbheromax and cooldudezach were working on.
 
androidfanwinner said:
I've tried both the linaro and Google compiled 1.02 kernels and I get constant reboots even when I'm at stock speeds. I did change the governor to Wheatley and SIO. 1.01a worked great for me. I have one of those phones that would not boot with the oc kernel rbheromax and cooldudezach were working on.
Click to expand...

Thanks. I haven't seen any logs of the crash yet. Can you collect a last_kmsg for me?

I'm running Wheatley and sio as well, so it shouldn't be that. My current suspicion is that some phones may be running msm8930aa instead of msm8930. I removed the aa code from compiling in 1.02, it's the only architectural change I made. I'll create another test build tonight with that enabled again.
 
After some gaming at stock clock speed, I also got a random reboot. It then continually rebooted until I turned it off for a while. Here's is my last_kmsg
 

Attachments

AweGuy said:
After some gaming at stock clock speed, I also got a random reboot. It then continually rebooted until I turned it off for a while. Here's is my last_kmsg
Click to expand...

I appreciate the effort, but unfortunately the kernel panic didn't get logged. It must have been overwritten before you could grab it.
 
brittnearl said:
It happened completely random it was actually just after unlocking
Click to expand...
[06-02 23:11:59.130] [0][602: kworker/u:5]cpufreq: cpu1 init at 162000 switching to 384000
[06-02 23:11:59.130] [0][602: kworker/u:5][MPDEC]: CPU[1] off->on | Mask=[1100]
[06-02 23:11:59.410] [1][0: swapper/1]CPU1: msm_pm_power_collapse: idle 0
[06-02 23:11:59.410] [1][0: swapper/1]CPU1: msm_pm_power_collapse: pre power down
[06-02 23:11:59.410] [1][0: swapper/1]CPU1: msm_pm_spm_power_collapse: notify_rpm 1
[06-02 23:11:59.410] [0][601: kworker/u:4][MPDEC]: CPU[1] on->off | Mask=[1000] | time online: 274
[06-02 23:12:00.180] [0][0: swapper/0]Unable to handle kernel NULL pointer dereference at virtual address 00000090

Methinks mpdecision tried to hotplug too fast. Note how in less than a second it turns cpu1 on and then off again. Either needs tweaking, a bug fix, or removal.
 
spock1104 said:
[06-02 23:11:59.130] [0][602: kworker/u:5]cpufreq: cpu1 init at 162000 switching to 384000
[06-02 23:11:59.130] [0][602: kworker/u:5][MPDEC]: CPU[1] off->on | Mask=[1100]
[06-02 23:11:59.410] [1][0: swapper/1]CPU1: msm_pm_power_collapse: idle 0
[06-02 23:11:59.410] [1][0: swapper/1]CPU1: msm_pm_power_collapse: pre power down
[06-02 23:11:59.410] [1][0: swapper/1]CPU1: msm_pm_spm_power_collapse: notify_rpm 1
[06-02 23:11:59.410] [0][601: kworker/u:4][MPDEC]: CPU[1] on->off | Mask=[1000] | time online: 274
[06-02 23:12:00.180] [0][0: swapper/0]Unable to handle kernel NULL pointer dereference at virtual address 00000090

Methinks mpdecision tried to hotplug too fast. Note how in less than a second it turns cpu1 on and then off again. Either needs tweaking, a bug fix, or removal.
Click to expand...

I knew I never liked mpdecision lol
 
Just wanted to say keep up the good work. You are pumping out kernels like crazy man. Good to see someone passionate about development. :P
 
You must log in or register to reply here.
Back
Top Bottom