[Nexus One Q&A, Help & Troubleshooting] Huascar82:
Hey all,

So this started one morning when I was using MUIU 9.30. Looked at phone and it would freeze on me. Anything I did, turned screen on and started navigating around for maybe 2 minutes and phone started FCing on Activity, or whatever the app happen to be up at the time. I thought maybe the ROM was all screwey, so I moved back to my cyanogen backup from a couple of days before. Same thing started happening, whether I was using LauncherPro or ADW. I had thought it might have been the MUIU launcher since before I was seeing it a lot while fooling around with icon placements. tried a wipe and reinstall of muiu, kept happening. Thought I'd start again with Cyanogen 6 but it happens on it too. Decided to go to Paul's release of FRG83 full stock with root, happened, same thing when trying FRG83 rooted with busybox. II have no idea where the problem is, I"m just afraid it's the N1 hardware. Captured logcat and this is what it shows.

10-07 14:56:09.078: WARN/SharedBufferStack(263): waitForCondition(LockCondition) timed out (identity=4, status=0). CPU may be pegged. trying again.
10-07 14:56:10.078: WARN/SharedBufferStack(263): waitForCondition(LockCondition) timed out (identity=4, status=0). CPU may be pegged. trying again.
10-07 14:56:10.448: INFO/Process(95): Sending signal. PID: 95 SIG: 3
10-07 14:56:10.459: INFO/dalvikvm(95): threadid=3: reacting to signal 3
10-07 14:56:10.479: INFO/dalvikvm(95): Wrote stack traces to '/data/anr/traces.txt'
10-07 14:56:11.078: WARN/SharedBufferStack(263): waitForCondition(LockCondition) timed out (identity=4, status=0). CPU may be pegged. trying again.
10-07 14:56:12.078: WARN/SharedBufferStack(263): waitForCondition(LockCondition) timed out (identity=4, status=0). CPU may be pegged. trying again.
10-07 14:56:13.078: WARN/SharedBufferStack(263): waitForCondition(LockCondition) timed out (identity=4, status=0). CPU may be pegged. trying again.

10-07 14:56:39.078: WARN/SharedBufferStack(263): waitForCondition(LockCondition) timed out (identity=4, status=0). CPU may be pegged. trying again.
10-07 14:56:40.078: WARN/SharedBufferStack(263): waitForCondition(LockCondition) timed out (identity=4, status=0). CPU may be pegged. trying again.
10-07 14:56:40.478: INFO/Process(95): Sending signal. PID: 95 SIG: 3
10-07 14:56:40.478: INFO/dalvikvm(95): threadid=3: reacting to signal 3
10-07 14:56:40.498: INFO/dalvikvm(95): Wrote stack traces to '/data/anr/traces.txt'
10-07 14:56:40.508: INFO/Process(95): Sending signal. PID: 272 SIG: 3
10-07 14:56:40.508: INFO/dalvikvm(272): threadid=3: reacting to signal 3
10-07 14:56:40.508: INFO/dalvikvm(272): Wrote stack traces to '/data/anr/traces.txt'
10-07 14:56:41.078: WARN/SharedBufferStack(263): waitForCondition(LockCondition) timed out (identity=4, status=0). CPU may be pegged. trying again.
10-07 14:56:42.078: WARN/SharedBufferStack(263): waitForCondition(LockCondition) timed out (identity=4, status=0). CPU may be pegged. trying again.
10-07 14:56:42.508: INFO/Watchdog_N(95): dumpKernelStacks
10-07 14:56:43.078: WARN/SharedBufferStack(263): waitForCondition(LockCondition) timed out (identity=4, status=0). CPU may be pegged. trying again.
10-07 14:56:44.088: WARN/SharedBufferStack(263): waitForCondition(LockCondition) timed out (identity=4, status=0). CPU may be pegged. trying again.

10-07 14:57:40.088: WARN/SharedBufferStack(263): waitForCondition(LockCondition) timed out (identity=4, status=0). CPU may be pegged. trying again.
10-07 14:57:40.268: WARN/ActivityManager(95): Activity idle timeout for HistoryRecord{44f93990 com.android.launcher/com.android.launcher2.Launcher}
10-07 14:57:40.268: WARN/ActivityManager(95): Timeout of broadcast BroadcastRecord{4512e048 android.intent.action.SCREEN_ON} - receiver=android.os.BinderProxy@44f37ff0
10-07 14:57:40.268: WARN/ActivityManager(95): Receiver during timeout: BroadcastFilter{44f3ba20 ReceiverList{44f3de78 272 com.android.phone/1001 remote:44f37ff0}}
10-07 14:57:40.278: DEBUG/WindowManager(95): I'm tired mEndcallBehavior=0x2
10-07 14:57:40.378: DEBUG/dalvikvm(95): GC_FOR_MALLOC freed 9697 objects / 410944 bytes in 93ms
10-07 14:57:40.378: INFO/dalvikvm-heap(95): Grow heap (frag case) to 5.278MB for 74655-byte allocation
10-07 14:57:40.458: DEBUG/dalvikvm(95): GC_FOR_MALLOC freed 279 objects / 13520 bytes in 81ms
10-07 14:57:40.458: INFO/Process(95): Sending signal. PID: 272 SIG: 3
10-07 14:57:40.468: INFO/dalvikvm(272): threadid=3: reacting to signal 3
10-07 14:57:40.488: INFO/dalvikvm(272): Wrote stack traces to '/data/anr/traces.txt'
10-07 14:57:40.558: INFO/Process(95): Sending signal. PID: 95 SIG: 3
10-07 14:57:40.558: INFO/dalvikvm(95): threadid=3: reacting to signal 3
10-07 14:57:40.558: DEBUG/dalvikvm(95): GC_FOR_MALLOC freed 183 objects / 6928 bytes in 90ms
10-07 14:57:40.558: INFO/dalvikvm-heap(95): Grow heap (frag case) to 5.403MB for 99532-byte allocation
10-07 14:57:40.658: DEBUG/dalvikvm(95): GC_FOR_MALLOC freed 3 objects / 112 bytes in 76ms
10-07 14:57:40.668: WARN/ActivityManager(95): finishReceiver called but none active
10-07 14:57:40.758: INFO/Process(95): Sending signal. PID: 264 SIG: 3
10-07 14:57:40.758: INFO/dalvikvm(264): threadid=3: reacting to signal 3
10-07 14:57:40.768: DEBUG/dalvikvm(95): GC_FOR_MALLOC freed 157 objects / 105400 bytes in 96ms
10-07 14:57:40.768: INFO/dalvikvm-heap(95): Grow heap (frag case) to 5.545MB for 199048-byte allocation
10-07 14:57:40.788: INFO/dalvikvm(95): Wrote stack traces to '/data/anr/traces.txt'
10-07 14:57:40.818: INFO/dalvikvm(264): Wrote stack traces to '/data/anr/traces.txt'
10-07 14:57:40.858: INFO/Process(95): Sending signal. PID: 263 SIG: 3
10-07 14:57:40.858: INFO/dalvikvm(263): threadid=3: reacting to signal 3
10-07 14:57:40.868: DEBUG/dalvikvm(95): GC_FOR_MALLOC freed 693 objects / 22280 bytes in 95ms
10-07 14:57:40.908: INFO/dalvikvm(263): Wrote stack traces to '/data/anr/traces.txt'
10-07 14:57:40.968: INFO/Process(95): Sending signal. PID: 484 SIG: 3
10-07 14:57:40.978: INFO/dalvikvm(484): threadid=3: reacting to signal 3
10-07 14:57:40.978: DEBUG/dalvikvm(95): GC_FOR_MALLOC freed 74 objects / 276432 bytes in 77ms
10-07 14:57:41.038: DEBUG/dalvikvm(95): GC_FOR_MALLOC freed 32 objects / 202528 bytes in 56ms
10-07 14:57:41.058: INFO/dalvikvm(484): Wrote stack traces to '/data/anr/traces.txt'
10-07 14:57:41.058: INFO/Process(95): Sending signal. PID: 294 SIG: 3
10-07 14:57:41.068: INFO/dalvikvm(294): threadid=3: reacting to signal 3
10-07 14:57:41.098: INFO/Process(95): Sending signal. PID: 95 SIG: 9
10-07 14:57:41.098: WARN/Watchdog(95): *** WATCHDOG KILLING SYSTEM PROCESS: com.android.server.am.ActivityManagerService
10-07 14:57:41.258: INFO/dalvikvm(294): Wrote stack traces to '/data/anr/traces.txt'
10-07 14:57:41.938: WARN/SharedBufferStack(263): waitForCondition(LockCondition) timed out (identity=4, status=0). CPU may be pegged. trying again.

10-07 15:01:43.998: WARN/SharedBufferStack(263): waitForCondition(LockCondition) timed out (identity=4, status=0). CPU may be pegged. trying again.
10-07 15:01:44.998: WARN/SharedBufferStack(263): waitForCondition(LockCondition) timed out (identity=4, status=0). CPU may be pegged. trying again.
10-07 15:01:45.698: INFO/ServiceManager(53): service 'SurfaceFlinger' died
10-07 15:01:45.698: INFO/ServiceManager(53): service 'permission' died

I broke up the Log as I didnt think it was necessary that I post the same SharedBufferStack warning over and over, just image it continuous between the breaks. If you notice the times most of those have at least a full minute of the SharedBufferStack warning, and between the last 2 sections over 3 minutes of nothing but the warning go by and then the phone just gives up and reboots.

Seeing all those SharedBufferStack warning makes me afraid my CPU is failing.

Does anyone have any idea what may be happening to my phone?