View Single Post
  #547 (permalink)  
Old 03-22-2011, 05:14 PM
arrrghhh's Avatar
arrrghhh
Testing Extraordinaire
Offline
Threadstarter
 
Join Date: Mar 2007
Posts: 3,604
Reputation: 7360
arrrghhh is a trusted member of the communityarrrghhh is a trusted member of the communityarrrghhh is a trusted member of the communityarrrghhh is a trusted member of the communityarrrghhh is a trusted member of the communityarrrghhh is a trusted member of the communityarrrghhh is a trusted member of the communityarrrghhh is a trusted member of the communityarrrghhh is a trusted member of the communityarrrghhh is a trusted member of the communityarrrghhh is a trusted member of the community
Mentioned: 7 Post(s)
Tagged: 0 Thread(s)
Re: [TESTING] Updated 3/11/11 New Kernel - TONS of changes!!

Quote:
Originally Posted by fishingmedic View Post
Arrrghhh, here's the dmesg and logcat from my freeze earlier today. As you know, it wasn't a SOD because stuff was still going on behind the scenes, more of a failed wake, was originally kinda frozen screen w/ orange led, screen lit up, I hit back on the hard keys and it went to blinking green LED and from the bottom of the logcat file, you can see what I was still receiving texts but couldn't look at them.
Hrm... interesting. I'm certainly no expert, but these logs show some serious issue. I just wish I knew what the issue was .

Logcat seems to show that the CPU is pegged, and can't do anything. I also see where the kernel tanked, probably the reason for the SoD. Interesting that adb worked - I don't think this condition was created from poor signal.

Edit - I suck at following logs . What were you doing right before it started acting haywire? I see a bunch of stuff like a task killer running, twitdroid, some SMS messages...

No matter how you slice it, in your logcat there's a TON of "CPU pegged" messages, blocking stuff&things from happening .

Last edited by arrrghhh; 03-22-2011 at 05:25 PM.
Reply With Quote
This post has been thanked 1 times.