View Single Post
  #548 (permalink)  
Old 03-22-2011, 05:58 PM
orangekid's Avatar
orangekid
Awesomenss :)
Offline
 
Join Date: Apr 2009
Posts: 6,973
Reputation: 7530
orangekid is a trusted member of the communityorangekid is a trusted member of the communityorangekid is a trusted member of the communityorangekid is a trusted member of the communityorangekid is a trusted member of the communityorangekid is a trusted member of the communityorangekid is a trusted member of the communityorangekid is a trusted member of the communityorangekid is a trusted member of the communityorangekid is a trusted member of the communityorangekid is a trusted member of the community
Mentioned: 34 Post(s)
Tagged: 0 Thread(s)
Send a message via AIM to orangekid Send a message via MSN to orangekid Send a message via Yahoo to orangekid
Re: [TESTING] Updated 3/11/11 New Kernel - TONS of changes!!

Quote:
Originally Posted by arrrghhh View Post
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 .
what governor are you using?


I know from doing this on HD2 that the radio makes a BIG difference in things like SOD and freezes, have you guys tried flashing different radios and noting logcat differences in the cpu as well as SOD?
Reply With Quote
This post has been thanked 1 times.