FORUMS

Sunday Debate: How Can We Get a No-Compromise Phone?

Join us in a fun Sunday Debate on Compromises. Come with your opinions and … more

PSA: You Can Optimize Your Note 4’s Recents Menu & RAM

The Note 4 never had the fastest Recents Menu, and despite its 3GB of RAM, … more

XDA Picks: Best Apps of the Week (July 25 – Aug 1)

Apps are at the front and center of any smartphone experience, and with over a … more

Voices Of XDA: Orbiting The Earth With Android

Editor’s note: This week’s feature has been written by forum … more

[Q] Help with Random Reboots

91 posts
Thanks Meter: 5
 
By prabs99, Member on 30th April 2014, 01:31 AM
Post Reply Subscribe to Thread Email Thread
I started getting random reboots once or twice a day this last week. I am attaching the latest last_kmsg file. The reason for the reboot is kernel_panic, but I don't know if it is a software problem or hardware problem. Can someone help with this? I am running CM11, nightly (4-27). Also the latest random reboot wiped my sms messages.
Attached Files
File Type: txt last_kmsg_04-29.txt - [Click for QR Code] (227.6 KB, 6 views)
File Type: txt last_kmsg_04-28.txt - [Click for QR Code] (227.6 KB, 4 views)
Last edited by prabs99; 30th April 2014 at 01:41 AM.
 
 
30th April 2014, 03:17 AM |#2  
ldubs's Avatar
Senior Member
Brooklyn, NY
Thanks Meter: 65
 
More
Switch kernels?

sent from my hammerhead
30th April 2014, 03:23 AM |#3  
jd1639's Avatar
XDA: ASSIST
Recognized Contributor
Minnetonka, MN
Thanks Meter: 4,882
 
Donate to Me
More
I'm guessing it's a hardware issue with the cache ram on the cpu. Flash back to stock and sees if the problem persists
The Following User Says Thank You to jd1639 For This Useful Post: [ View ]
1st May 2014, 02:11 AM |#4  
OP Member
West Richland, WA
Thanks Meter: 5
 
More
Quote:
Originally Posted by jd1639

I'm guessing it's a hardware issue with the cache ram on the cpu. Flash back to stock and sees if the problem persists

Thanks. Will try that.
1st May 2014, 03:59 AM |#5  
simms22's Avatar
Recognized Contributor
BROOKLYN!
Thanks Meter: 25,014
 
More
kernel panic is more or less generic name for many many many types of derps that can happen. a rom might cause this, a kernel might cause this, a user started mod could cause this, an app could cause this, a theme can cause this.. really, theres a multitude of reasons for kernel panics. personally, i wouldnt do something as drastic as go back to stock. youre running a nightly, which is EXPECTED to have derps. you can flash tbe next nightly to see if the issue still happens, or the previous nightly, or even a stable build. anyways, ill look at your last_kmsg to see if i can spot whats causing the kernel panics.

---------- Post added at 10:59 PM ---------- Previous post was at 10:51 PM ----------

heres your problem, what caused your kernel panics. looks like a cm rom/kernel issue, not very serious, but will cause random reboots. pass your last_kmsg over to someone who worls on cm, so they can fix it.


[ 1368.559152] Fatal error on the ADSP!
[ 1368.559235] ADSP subsystem failure reason: memheap.c:1091:In task 0x0, Assertion block_ptr->forw_offset != 0 failed
[ 1368.559313] subsys-restart: subsystem_restart_dev(): Restart sequence requested for adsp, restart_level = RELATED.
[ 1368.559671] Unable to handle kernel NULL pointer dereference at virtual address 00000000
The Following 2 Users Say Thank You to simms22 For This Useful Post: [ View ]
1st May 2014, 11:47 AM |#6  
CitizenLee's Avatar
Senior Member
Thanks Meter: 495
 
More
Quote:
Originally Posted by simms22

kernel panic is more or less generic name for many many many types of derps that can happen. a rom might cause this, a kernel might cause this, a user started mod could cause this, an app could cause this, a theme can cause this.. really, theres a multitude of reasons for kernel panics. personally, i wouldnt do something as drastic as go back to stock. youre running a nightly, which is EXPECTED to have derps. you can flash tbe next nightly to see if the issue still happens, or the previous nightly, or even a stable build. anyways, ill look at your last_kmsg to see if i can spot whats causing the kernel panics.

---------- Post added at 10:59 PM ---------- Previous post was at 10:51 PM ----------

heres your problem, what caused your kernel panics. looks like a cm rom/kernel issue, not very serious, but will cause random reboots. pass your last_kmsg over to someone who worls on cm, so they can fix it.


[ 1368.559152] Fatal error on the ADSP!
[ 1368.559235] ADSP subsystem failure reason: memheap.c:1091:In task 0x0, Assertion block_ptr->forw_offset != 0 failed
[ 1368.559313] subsys-restart: subsystem_restart_dev(): Restart sequence requested for adsp, restart_level = RELATED.
[ 1368.559671] Unable to handle kernel NULL pointer dereference at virtual address 00000000

I don't even use CM or have this problem but I've given you a thanks anyway, as that is a first class reply
The Following User Says Thank You to CitizenLee For This Useful Post: [ View ]
3rd May 2014, 01:18 AM |#7  
OP Member
West Richland, WA
Thanks Meter: 5
 
More
Thank you very much. I will post it in the CM11 thread.

Quote:
Originally Posted by simms22

kernel panic is more or less generic name for many many many types of derps that can happen. a rom might cause this, a kernel might cause this, a user started mod could cause this, an app could cause this, a theme can cause this.. really, theres a multitude of reasons for kernel panics. personally, i wouldnt do something as drastic as go back to stock. youre running a nightly, which is EXPECTED to have derps. you can flash tbe next nightly to see if the issue still happens, or the previous nightly, or even a stable build. anyways, ill look at your last_kmsg to see if i can spot whats causing the kernel panics.

---------- Post added at 10:59 PM ---------- Previous post was at 10:51 PM ----------

heres your problem, what caused your kernel panics. looks like a cm rom/kernel issue, not very serious, but will cause random reboots. pass your last_kmsg over to someone who worls on cm, so they can fix it.


[ 1368.559152] Fatal error on the ADSP!
[ 1368.559235] ADSP subsystem failure reason: memheap.c:1091:In task 0x0, Assertion block_ptr->forw_offset != 0 failed
[ 1368.559313] subsys-restart: subsystem_restart_dev(): Restart sequence requested for adsp, restart_level = RELATED.
[ 1368.559671] Unable to handle kernel NULL pointer dereference at virtual address 00000000

Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools
Display Modes