Strange after-sleep problem

MBP penryn
leo 10.5.2
happened two times
i close the lid and the laptop goes to sleep
i close it in the middle of work (was listening to music, writing email and so on, so all my applications are opened), so i close the lid, it goes to sleep, after a while (doesnt matter how much time, really) i open it and see this:
http://img102.imageshack.us/img102/4509/p1140091vi3.jpg
(mirror: http://maccentre.ru/board/files/p114009111_142.jpg )
obviously i need to force restart (shut down) the laptop
is it because any the of programms that i have ? cause that's what i've been told but to be honest i have no idea what kind of soft might be causing it..
any help please ?

I have the same problem.
See:
http://forums.macgeneration.com/vbulletin/attachment.php?attachmentid=17106&d=12 10368537
GC

Similar Messages

Were any reboot after sleep problems NOT fixed by the EFI firmware update?

The subject says it all. I wanted to get a read on whether this EFI update really did solve the reboot after sleep problem for all 2008 Mac Pros. If have an early '08 Pro that had the problem before the update and it didn't go away after the update (and it's not due to some other problem like kernel panics, etc.), then please post details in this thread. thanks!

We have 4 total systems (all had the issue, all slightly different configurations) and the reboot-on-wake issue has disappeared on all 4 of them.
Looks like a definitive fix to me.

PB 15" screen backlight after sleep problem

I have an intermittent problem wherein my display backlight will not light sometimes upon waking up my PB from sleep. The backlight is totally out when this happens, not just dimmed. The laptop is on and the display itself is functioning (I can barely see the images on the dark screen) but the backlight is out. I have to press the power button for a second to get the "shut down" box, shut down the PB and restart it. During the boot process the screen backlight eventually relights. Anyone else having this problem?
MB 17in, PB G4 15in, PB G4 12in, iMac G3, iBook G3, PB 1400c, PB 5300 Mac OS X (10.4.6) Loyal to Apple since the Apple //+

Try to replace inverter board.
http://www.ifixit.com/cart/customer/product.php?productid=746&cat=&page=1
Really easy to replace if yours is still under warranty then bring to nearest AASP or Apple store, If not then to replace inverter board you neew to use allen key to open 2 screws in the display open your display as wide as possible more than 90 degree and try to take the screws out.
Then use plastic stick/nylon sticj to pry open the display along the light and dark grey plastic and after you open the display bezel you will see the inverter board located in the bottom of your display.
Hope this help
Flippo
PS: I'm not responsible if you break anything during take apart. Just be carefull and take your time.

T440 fn ctrl reverting after sleep problem

Hi,
I have a T440, and I've set in BIOS to swap places for fn and ctrl. This works great until the machine goes to sleep or similar. After awakening the machine the keys are back to their original setting, with fn being fn, and ctrl being ctrl.
I havent explored this in detail but just found the machine sporadically losing the setting, but never while I'm working on it. So either from sleep or from locked screen.
I always use FnLk as well and that is also lost when this happens. I have to restart to get back the setting for fn-ctrl swap, but FnLk i can just enable,
Anyone else have this issue, any ideas how to fix?
I run Windows 8.1 on my T440.
Solved!
Go to Solution.

Looks like the recent BIOS update did not resolve this issue. The BIOS version on my ThinkPad X240 is 2.21.1.12.
P.S. I just realized this thread is about ThinkPad T440, so I started a new thread in the respective section for X240 to ensure the same issue is acknowledged and fixed for the different model.

Crashing at start up...then after sleep, two problems, same reason?

new macbookpro 2.2. Since purchase it has been crashing at first start up every morning -long lines with pixels and smal squares with piwels in the background- Once it starts the 2nd time works wonderfully until I put it to sleep. Then wakes up normally and a few minutes later (it varies) it freezes totally again -small squares, pointer spinning- and I have too shut down with power button (force quit never works in this situations).
I reinstalled Leopard 3 times by now without success, then took it to the official service. They run tests and the new HD gave a problem under the SMART protocol. I told them I replaced the original 120gb for a 250gb Samsung, but the problem existed from the very beginning, still under the situation I opted for a new 250gb hard drive which they installed. They also installed a fresh leopard and told me the MBP worked fine.
Took it home and migrated from time machine again, the problem persisted.It crashes first thing in the morning and again when after sleep.
I also noticed that any applications may start-crash the first time I try. The second time is generally fine and works well.
I am thinking to take it back to the shop but believe they only will run standardized test and nothing will happen.
It could be something I do when migrating from time machine?
It could be some hardware (graphic card GeForce 8600M GT)?
I had reseted PRAM, run test with techtool (the only problem that shows is when tests the video card), run test with cocktail.
I never used the console but I am willing to start doing it.
Anybody has a clue?
Thanks!
here is the last application crash from this morning,
The freezes I don't know if they get registered anywhere.
Mail2008-02-20-075948macbook-pro-de-javier-gomez.crash
Process: Mail [912]
Path: /Applications/Mail.app/Contents/MacOS/Mail
Identifier: com.apple.mail
Version: 3.2 (919)
Build Info: Mail-9190000~3
Code Type: X86 (Native)
Parent Process: launchd [136]
Date/Time: 2008-02-20 07:59:48.762 +0100
OS Version: Mac OS X 10.5.2 (9C31)
Report Version: 6
Exception Type: EXCBADACCESS (SIGBUS)
Exception Codes: KERNPROTECTIONFAILURE at 0x00000000967b4b28
Crashed Thread: 22
Application Specific Information:
-[MessageRouter routeQueuedMessages]
-[POPAccount fetchSynchronously]
-[POPAccount fetchSynchronously]
-[MailApp _synchronouslyTellSyncServicesToRegisterAndSync]
Thread 0:
0 libSystem.B.dylib 0x9678debc OSAtomicCompareAndSwapPtrBarrier + 0
1 ...ple.CoreServices.CarbonCore 0x924ff71f TSAcquireReader + 101
2 ...ple.CoreServices.CarbonCore 0x92506e2a AllocateHandleFromPool + 32
3 ...ple.CoreServices.CarbonCore 0x92509c59 CSMemNewHandle + 16
4 ...ple.CoreServices.CarbonCore 0x9252943f RegisterComponentResourcePtr + 491
5 ...ple.CoreServices.CarbonCore 0x92527a4d registerSystemComponents + 317
6 ...ple.CoreServices.CarbonCore 0x925276b5 FindNextComponentInternal(ComponentRecord*, ComponentDescription*) + 95
7 ...ple.CoreServices.CarbonCore 0x9252763f FindNextComponent + 53
8 com.apple.AppKit 0x9414809e _initializeCA + 991
9 com.apple.AppKit 0x94147bea -[NSSound _postInitialization] + 348
10 com.apple.AppKit 0x941479d9 -[NSSound initWithContentsOfURL:byReference:] + 269
11 com.apple.MessageFramework 0x003c02f7 +[NSSound(MessageAdditions) _playNextSound] + 454
12 com.apple.Foundation 0x922bdfce __NSFireDelayedPerform + 382
13 com.apple.CoreFoundation 0x91a07b5e CFRunLoopRunSpecific + 4494
14 com.apple.CoreFoundation 0x91a07d18 CFRunLoopRunInMode + 88
15 com.apple.HIToolbox 0x929e66a0 RunCurrentEventLoopInMode + 283
16 com.apple.HIToolbox 0x929e64b9 ReceiveNextEventCommon + 374
17 com.apple.HIToolbox 0x929e632d BlockUntilNextEventMatchingListInMode + 106
18 com.apple.AppKit 0x93f497d9 _DPSNextEvent + 657
19 com.apple.AppKit 0x93f4908e -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 128
20 com.apple.AppKit 0x93f420c5 -[NSApplication run] + 795
21 com.apple.AppKit 0x93f0f30a NSApplicationMain + 574
22 com.apple.mail 0x000fa206 0x1000 + 1020422
Thread 1:
0 libSystem.B.dylib 0x967839e6 machmsgtrap + 10
1 libSystem.B.dylib 0x9678b1dc mach_msg + 72
2 com.apple.CoreFoundation 0x91a070de CFRunLoopRunSpecific + 1806
3 com.apple.CoreFoundation 0x91a07d18 CFRunLoopRunInMode + 88
4 com.apple.Foundation 0x922bdb15 -[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 213
5 com.apple.Foundation 0x922c9c34 -[NSRunLoop(NSRunLoop) run] + 84
6 com.apple.MessageFramework 0x0047e0a0 -[RSSInterchange _runManager] + 2140
7 com.apple.Foundation 0x922895ad -[NSThread main] + 45
8 com.apple.Foundation 0x92289154 _NSThread__main_ + 308
9 libSystem.B.dylib 0x967b4c55 pthreadstart + 321
10 libSystem.B.dylib 0x967b4b12 thread_start + 34
Thread 2:
0 libSystem.B.dylib 0x967ed5c6 _workqops + 10
1 libSystem.B.dylib 0x967ed5f6 start_wqthread + 30
Thread 3:
Thread 4:
0 libSystem.B.dylib 0x96783a46 semaphoretimedwait_signaltrap + 10
1 libSystem.B.dylib 0x967b5daf pthread_condwait + 1244
2 libSystem.B.dylib 0x967b7633 pthreadcond_timedwait_relativenp + 47
3 com.apple.Foundation 0x922cf4fc -[NSCondition waitUntilDate:] + 236
4 com.apple.Foundation 0x922cf310 -[NSConditionLock lockWhenCondition:beforeDate:] + 144
5 com.apple.MessageFramework 0x00480154 -[InvocationQueue _drainQueue] + 317
6 com.apple.Foundation 0x922895ad -[NSThread main] + 45
7 com.apple.Foundation 0x92289154 _NSThread__main_ + 308
8 libSystem.B.dylib 0x967b4c55 pthreadstart + 321
9 libSystem.B.dylib 0x967b4b12 thread_start + 34
Thread 5:
0 libSystem.B.dylib 0x9678abce _semwaitsignal + 10
1 libSystem.B.dylib 0x967b58cd pthreadcondwait$UNIX2003 + 73
2 com.apple.QuartzCore 0x96188121 fefragmentthread + 54
3 libSystem.B.dylib 0x967b4c55 pthreadstart + 321
4 libSystem.B.dylib 0x967b4b12 thread_start + 34
Thread 6:
0 libSystem.B.dylib 0x96783a46 semaphoretimedwait_signaltrap + 10
1 libSystem.B.dylib 0x967b5daf pthread_condwait + 1244
2 libSystem.B.dylib 0x967b7633 pthreadcond_timedwait_relativenp + 47
3 com.apple.Foundation 0x922cf4fc -[NSCondition waitUntilDate:] + 236
4 com.apple.Foundation 0x922cf310 -[NSConditionLock lockWhenCondition:beforeDate:] + 144
5 com.apple.MessageFramework 0x00480154 -[InvocationQueue _drainQueue] + 317
6 com.apple.Foundation 0x922895ad -[NSThread main] + 45
7 com.apple.Foundation 0x92289154 _NSThread__main_ + 308
8 libSystem.B.dylib 0x967b4c55 pthreadstart + 321
9 libSystem.B.dylib 0x967b4b12 thread_start + 34
Thread 7:
0 libSystem.B.dylib 0x96783a46 semaphoretimedwait_signaltrap + 10
1 libSystem.B.dylib 0x967b5daf pthread_condwait + 1244
2 libSystem.B.dylib 0x967b7633 pthreadcond_timedwait_relativenp + 47
3 com.apple.Foundation 0x922cf4fc -[NSCondition waitUntilDate:] + 236
4 com.apple.Foundation 0x922cf310 -[NSConditionLock lockWhenCondition:beforeDate:] + 144
5 com.apple.MessageFramework 0x00480154 -[InvocationQueue _drainQueue] + 317
6 com.apple.Foundation 0x922895ad -[NSThread main] + 45
7 com.apple.Foundation 0x92289154 _NSThread__main_ + 308
8 libSystem.B.dylib 0x967b4c55 pthreadstart + 321
9 libSystem.B.dylib 0x967b4b12 thread_start + 34
Thread 8:
0 libSystem.B.dylib 0x96783a46 semaphoretimedwait_signaltrap + 10
1 libSystem.B.dylib 0x967b5daf pthread_condwait + 1244
2 libSystem.B.dylib 0x967b7633 pthreadcond_timedwait_relativenp + 47
3 com.apple.Foundation 0x922cf4fc -[NSCondition waitUntilDate:] + 236
4 com.apple.Foundation 0x922cf310 -[NSConditionLock lockWhenCondition:beforeDate:] + 144
5 com.apple.MessageFramework 0x00480154 -[InvocationQueue _drainQueue] + 317
6 com.apple.Foundation 0x922895ad -[NSThread main] + 45
7 com.apple.Foundation 0x92289154 _NSThread__main_ + 308
8 libSystem.B.dylib 0x967b4c55 pthreadstart + 321
9 libSystem.B.dylib 0x967b4b12 thread_start + 34
Thread 9:
0 libSystem.B.dylib 0x96783a46 semaphoretimedwait_signaltrap + 10
1 libSystem.B.dylib 0x967b5daf pthread_condwait + 1244
2 libSystem.B.dylib 0x967b7633 pthreadcond_timedwait_relativenp + 47
3 com.apple.Foundation 0x922cf4fc -[NSCondition waitUntilDate:] + 236
4 com.apple.Foundation 0x922cf310 -[NSConditionLock lockWhenCondition:beforeDate:] + 144
5 com.apple.MessageFramework 0x00480154 -[InvocationQueue _drainQueue] + 317
6 com.apple.Foundation 0x922895ad -[NSThread main] + 45
7 com.apple.Foundation 0x92289154 _NSThread__main_ + 308
8 libSystem.B.dylib 0x967b4c55 pthreadstart + 321
9 libSystem.B.dylib 0x967b4b12 thread_start + 34
Thread 10:
0 libSystem.B.dylib 0x967839e6 machmsgtrap + 10
1 libSystem.B.dylib 0x9678b1dc mach_msg + 72
2 com.apple.CoreFoundation 0x91a070de CFRunLoopRunSpecific + 1806
3 com.apple.CoreFoundation 0x91a07d18 CFRunLoopRunInMode + 88
4 com.apple.CFNetwork 0x9328b6cc CFURLCacheWorkerThread(void*) + 396
5 libSystem.B.dylib 0x967b4c55 pthreadstart + 321
6 libSystem.B.dylib 0x967b4b12 thread_start + 34
Thread 11:
0 libSystem.B.dylib 0x967839e6 machmsgtrap + 10
1 libSystem.B.dylib 0x9678b1dc mach_msg + 72
2 com.apple.CoreFoundation 0x91a070de CFRunLoopRunSpecific + 1806
3 com.apple.CoreFoundation 0x91a07d18 CFRunLoopRunInMode + 88
4 com.apple.Foundation 0x922ecac0 +[NSURLConnection(NSURLConnectionReallyInternal) _resourceLoadLoop:] + 320
5 com.apple.Foundation 0x922895ad -[NSThread main] + 45
6 com.apple.Foundation 0x92289154 _NSThread__main_ + 308
7 libSystem.B.dylib 0x967b4c55 pthreadstart + 321
8 libSystem.B.dylib 0x967b4b12 thread_start + 34
Thread 12:
0 libSystem.B.dylib 0x96783a46 semaphoretimedwait_signaltrap + 10
1 libSystem.B.dylib 0x967b5daf pthread_condwait + 1244
2 libSystem.B.dylib 0x967b7633 pthreadcond_timedwait_relativenp + 47
3 ...apple.AddressBook.framework 0x96d96ab5 -[ABRemoteImageLoader workLoop] + 193
4 com.apple.Foundation 0x922895ad -[NSThread main] + 45
5 com.apple.Foundation 0x92289154 _NSThread__main_ + 308
6 libSystem.B.dylib 0x967b4c55 pthreadstart + 321
7 libSystem.B.dylib 0x967b4b12 thread_start + 34
Thread 13:
0 libSystem.B.dylib 0x967d3b3a select$DARWIN_EXTSN + 10
1 libSystem.B.dylib 0x967b4c55 pthreadstart + 321
2 libSystem.B.dylib 0x967b4b12 thread_start + 34
Thread 14:
0 libSystem.B.dylib 0x96783a2e semaphorewait_signaltrap + 10
1 libSystem.B.dylib 0x9678b505 pthreadmutexlock + 569
2 libobjc.A.dylib 0x9366d688 cachefill + 65
3 libobjc.A.dylib 0x9366bba0 logand_fillcache + 141
4 libobjc.A.dylib 0x9366c576 classlookupMethodAndLoadCache + 206
5 libobjc.A.dylib 0x9367c736 objc_msgSend + 102
6 com.apple.MessageFramework 0x004e5351 -[POPAccount fetchSynchronously] + 337
7 com.apple.CoreFoundation 0x91a86b7d _invoking__ + 29
8 com.apple.CoreFoundation 0x91a86568 -[NSInvocation invoke] + 136
9 com.apple.MessageFramework 0x00480739 -[MonitoredInvocation invoke] + 409
10 com.apple.MessageFramework 0x0048031b -[InvocationQueue _drainQueue] + 772
11 com.apple.Foundation 0x922895ad -[NSThread main] + 45
12 com.apple.Foundation 0x92289154 _NSThread__main_ + 308
13 libSystem.B.dylib 0x967b4c55 pthreadstart + 321
14 libSystem.B.dylib 0x967b4b12 thread_start + 34
Thread 15:
0 libSystem.B.dylib 0x967839e6 machmsgtrap + 10
1 libSystem.B.dylib 0x9678b1dc mach_msg + 72
2 com.apple.CoreFoundation 0x91a070de CFRunLoopRunSpecific + 1806
3 com.apple.CoreFoundation 0x91a07d18 CFRunLoopRunInMode + 88
4 com.apple.MessageFramework 0x003a7a6a _handleRequestWithTimeout + 2163
5 com.apple.MessageFramework 0x003ac32d -[_NSSocket readBytes:length:error:] + 154
6 com.apple.MessageFramework 0x003abeb7 -[Connection _readBytesFromSocketIntoBuffer:amount:requireAllBytes:error:] + 89
7 com.apple.MessageFramework 0x003abd72 -[Connection _fillBuffer:] + 853
8 com.apple.MessageFramework 0x003ab938 -[Connection _readLineIntoData:error:] + 70
9 com.apple.MessageFramework 0x004b1196 -[POP3Connection(PrivateCommands) _readMultilineResponseWithMaxSize:intoMutableData:informDelegate:] + 542
10 com.apple.MessageFramework 0x004b033a -[POP3Connection _retrieveMessage:ofSize:informDelegate:] + 327
11 com.apple.MessageFramework 0x004b0428 -[POP3Connection retr:] + 174
12 com.apple.MessageFramework 0x004b0c3c -[POP3Connection fetchMessages:] + 342
13 com.apple.MessageFramework 0x004b42f3 -[POP3FetchStore fetchSynchronously] + 3406
14 com.apple.MessageFramework 0x004e5351 -[POPAccount fetchSynchronously] + 337
15 com.apple.CoreFoundation 0x91a86b7d _invoking__ + 29
16 com.apple.CoreFoundation 0x91a86568 -[NSInvocation invoke] + 136
17 com.apple.MessageFramework 0x00480739 -[MonitoredInvocation invoke] + 409
18 com.apple.MessageFramework 0x0048031b -[InvocationQueue _drainQueue] + 772
19 com.apple.Foundation 0x922895ad -[NSThread main] + 45
20 com.apple.Foundation 0x92289154 _NSThread__main_ + 308
21 libSystem.B.dylib 0x967b4c55 pthreadstart + 321
22 libSystem.B.dylib 0x967b4b12 thread_start + 34
Thread 16:
0 libSystem.B.dylib 0x967839e6 machmsgtrap + 10
1 libSystem.B.dylib 0x9678b1dc mach_msg + 72
2 com.apple.CoreFoundation 0x91a070de CFRunLoopRunSpecific + 1806
3 com.apple.CoreFoundation 0x91a07d18 CFRunLoopRunInMode + 88
4 com.apple.Foundation 0x922bdb15 -[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 213
5 com.apple.Foundation 0x922c9c34 -[NSRunLoop(NSRunLoop) run] + 84
6 com.apple.MessageFramework 0x003a4871 +[_NSSocket _runIOThread] + 98
7 com.apple.Foundation 0x922895ad -[NSThread main] + 45
8 com.apple.Foundation 0x92289154 _NSThread__main_ + 308
9 libSystem.B.dylib 0x967b4c55 pthreadstart + 321
10 libSystem.B.dylib 0x967b4b12 thread_start + 34
Thread 17:
0 libSystem.B.dylib 0x967839e6 machmsgtrap + 10
1 libSystem.B.dylib 0x9678b1dc mach_msg + 72
2 com.apple.CoreFoundation 0x91a070de CFRunLoopRunSpecific + 1806
3 com.apple.CoreFoundation 0x91a07d18 CFRunLoopRunInMode + 88
4 com.apple.Foundation 0x922bdb15 -[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 213
5 com.apple.syncservices 0x96cb1d8c -[ISyncConcreteSession _waitForTransitionFromPhase:untilDate:] + 527
6 com.apple.syncservices 0x96caff1a +[ISyncSession _sessionWithClient:entityNames:beforeDate:clientHasTruthForEntityNames:quietlyP ushTruth:target:selector:anchors:] + 1695
7 com.apple.syncservices 0x96caf872 +[ISyncSession beginSessionWithClient:entityNames:beforeDate:] + 95
8 com.apple.syncservices 0x96caf740 -[ISyncConcreteSessionDriver _beginSyncSession:] + 1251
9 com.apple.syncservices 0x96cac631 -[ISyncConcreteSessionDriver _preSync] + 95
10 com.apple.syncservices 0x96d44b2b -[ISyncConcreteSessionDriver startAsynchronousSync:] + 273
11 com.apple.Mail.Syncer 0x10f14acc 0x10f00000 + 84684
12 com.apple.Mail.Syncer 0x10f13c6d 0x10f00000 + 81005
13 com.apple.mail 0x00037fbd 0x1000 + 225213
14 com.apple.CoreFoundation 0x91a86b7d _invoking__ + 29
15 com.apple.CoreFoundation 0x91a86568 -[NSInvocation invoke] + 136
16 com.apple.MessageFramework 0x00480739 -[MonitoredInvocation invoke] + 409
17 com.apple.MessageFramework 0x004815fb +[WorkerThread _execute:] + 144
18 com.apple.Foundation 0x922895ad -[NSThread main] + 45
19 com.apple.Foundation 0x92289154 _NSThread__main_ + 308
20 libSystem.B.dylib 0x967b4c55 pthreadstart + 321
21 libSystem.B.dylib 0x967b4b12 thread_start + 34
Thread 18:
0 libSystem.B.dylib 0x9678abce _semwaitsignal + 10
1 libSystem.B.dylib 0x9678a996 usleep$UNIX2003 + 61
2 com.apple.AppKit 0x93fafcf9 -[NSUIHeartBeat _heartBeatThread:] + 2042
3 com.apple.Foundation 0x922895ad -[NSThread main] + 45
4 com.apple.Foundation 0x92289154 _NSThread__main_ + 308
5 libSystem.B.dylib 0x967b4c55 pthreadstart + 321
6 libSystem.B.dylib 0x967b4b12 thread_start + 34
Thread 19:
0 libSystem.B.dylib 0x967839e6 machmsgtrap + 10
1 libSystem.B.dylib 0x9678b1dc mach_msg + 72
2 com.apple.CoreFoundation 0x91a070de CFRunLoopRunSpecific + 1806
3 com.apple.CoreFoundation 0x91a07d18 CFRunLoopRunInMode + 88
4 com.apple.Foundation 0x922bdb15 -[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 213
5 com.apple.syncservices 0x96cb1d8c -[ISyncConcreteSession _waitForTransitionFromPhase:untilDate:] + 527
6 com.apple.syncservices 0x96cc07c9 -[ISyncConcreteSession prepareToPullChangesForEntityNames:beforeDate:] + 99
7 com.apple.syncservices 0x96cbfc3b -[ISyncConcreteSessionDriver _pullPhaseOfSession] + 1755
8 com.apple.syncservices 0x96cac2fb -[ISyncConcreteSessionDriver _sync:] + 223
9 com.apple.syncservices 0x96d449cd -[ISyncConcreteSessionDriver _startAsynchronousSyncWorker] + 425
10 com.apple.Foundation 0x922895ad -[NSThread main] + 45
11 com.apple.Foundation 0x92289154 _NSThread__main_ + 308
12 libSystem.B.dylib 0x967b4c55 pthreadstart + 321
13 libSystem.B.dylib 0x967b4b12 thread_start + 34
Thread 20:
0 libSystem.B.dylib 0x967839e6 machmsgtrap + 10
1 libSystem.B.dylib 0x9678b1dc mach_msg + 72
2 libSystem.B.dylib 0x967b8464 threadgetstate + 173
3 libobjc.A.dylib 0x9366d467 cache_collectfree + 334
4 libobjc.A.dylib 0x9366d829 cachefill + 482
5 libobjc.A.dylib 0x9366bba0 logand_fillcache + 141
6 libobjc.A.dylib 0x9366c576 classlookupMethodAndLoadCache + 206
7 libobjc.A.dylib 0x9367c736 objc_msgSend + 102
8 com.apple.Foundation 0x922d9134 -[NSUndoManager removeAllActionsWithTarget:] + 52
9 com.apple.CoreData 0x91d0bbe2 -[NSManagedObjectContext(_NSInternalNotificationHandling) _stopObservingUndoManagerNotifications] + 114
10 com.apple.CoreData 0x91d5ca24 -[NSManagedObjectContext(_NSInternalNotificationHandling) _unregisterForNotifications] + 68
11 com.apple.CoreData 0x91d5c8b5 -[NSManagedObjectContext dealloc] + 69
12 com.apple.Foundation 0x92284d9f NSPopAutoreleasePool + 431
13 com.apple.MessageFramework 0x0049d931 -[MessageRouter routeQueuedMessages] + 1081
14 com.apple.CoreFoundation 0x91a86b7d _invoking__ + 29
15 com.apple.CoreFoundation 0x91a86568 -[NSInvocation invoke] + 136
16 com.apple.MessageFramework 0x00480739 -[MonitoredInvocation invoke] + 409
17 com.apple.MessageFramework 0x004815fb +[WorkerThread _execute:] + 144
18 com.apple.Foundation 0x922895ad -[NSThread main] + 45
19 com.apple.Foundation 0x92289154 _NSThread__main_ + 308
20 libSystem.B.dylib 0x967b4c55 pthreadstart + 321
21 libSystem.B.dylib 0x967b4b12 thread_start + 34
Thread 21:
0 libSystem.B.dylib 0x96783a46 semaphoretimedwait_signaltrap + 10
1 libSystem.B.dylib 0x967b5daf pthread_condwait + 1244
2 libSystem.B.dylib 0x967b7633 pthreadcond_timedwait_relativenp + 47
3 com.apple.Foundation 0x922cf4fc -[NSCondition waitUntilDate:] + 236
4 com.apple.Foundation 0x922cf310 -[NSConditionLock lockWhenCondition:beforeDate:] + 144
5 com.apple.MessageFramework 0x00480154 -[InvocationQueue _drainQueue] + 317
6 com.apple.Foundation 0x922895ad -[NSThread main] + 45
7 com.apple.Foundation 0x92289154 _NSThread__main_ + 308
8 libSystem.B.dylib 0x967b4c55 pthreadstart + 321
9 libSystem.B.dylib 0x967b4b12 thread_start + 34
Thread 22 Crashed:
0 ??? 0x117eec0d 0 + 293530637
1 libSystem.B.dylib 0x967b4c55 pthreadstart + 321
2 libSystem.B.dylib 0x967b4b12 thread_start + 34
Thread 22 crashed with X86 Thread State (32-bit):
eax: 0x00000000 ebx: 0x967b4b28 ecx: 0xb09dee9c edx: 0x96783b06
edi: 0x00000000 esi: 0xb09df000 ebp: 0xb09def78 esp: 0xb09def40
ss: 0x0000001f efl: 0x00010282 eip: 0x117eec0d cs: 0x00000017
ds: 0x0000001f es: 0x0000001f fs: 0x0000001f gs: 0x00000037
cr2: 0x967b4b28

No one had this problem or similar that could hint a different solution that to take the machine to the shop? Does it look like hardware?
Thanks again

Safari 2.0.4 problems after sleep

I've searched a bit for problems with Safari 2.0.4 after sleep and can't find much that relates to my specific problems so I'll ask for your help. On my Powerbook G4 15" when Safari is running and it goes into sleep mode I get the following problems:
1. After heavy sleep, when I awaken the computer Safari says that the application has quit.
2. After a short time away from the computer Safari is unresponsive with a spinning beachball and a lot of disk activity. After 3-5 minutes it seems to return to normal.
Is this a known or common problem? Are there any fixes? The issue has been going on for many months, but I thought I might see if there's a cure. Resetting Safari and clearing cache don't appear to help out.
Thanks for your help.

No, everything else appears to work fine. When there is this beachball activity there's a lot of hard disk activity taking place. I have 1.5GB of RAM, but this happens when I have 2 applications open or 5. It just appears that when I leave the computer unattended for 5 minutes or so some sort off background activity is taking place.

Yosemite upgrade: function keys no longer work, no keyboard lights and have to sign in twice after sleep mode. Anybody else having these problems?

Hi,
Since I did the Yosemite 'upgrade' last week I have been having problems with my MacBook Pro that never happened before. The most frustrating problems involve my keyboard which doesn't light up (checked my settings and they are correct) and the top row of function keys don't do anything so I can't adjust the volume, brightness, etc. Then if my screen goes into sleep mode, when I wake it back up I have to sign back in twice - I never had to sign in at all after sleep mode before.
I'm finding that in order to get it working properly I am having to completely shut down and start up again but when the keyboard problems are happening I can't get anything on the apple dropdown to work either (i.e. shut down, restart, etc) so I can only shut down by pressing and holding the on/off button.
I've never had problems with my Macbook before and feel like Apple have completely ruined it in one update! I've had a look through other posts on here but can't find anybody else having these problems so I would be really grateful if anyone could help me and offer me some advice on how to sort it out.
Thanks!

Reset PRAM. http://support.apple.com/kb/PH18761
Reset SMC. http://support.apple.com/kb/HT3964
Choose the method for:
"Resetting SMC on portables with a battery you should not remove on your own".
Best.

Pismo Sound Problems after Sleep in Tiger

Hi all. New to the forums and returning to Macs after years of cursing Bill Gates. Picked up a Powerbook Pismo from a friend and have been having some fun with it, but I have one problem I can't solve. I replaced the hard drive (saved the old one) and installed Tiger and 1GB of memory on the machine. All seemed well until I noticed that the sound would not work sometimes after sleeping. The sound will usually return with a reboot, but sometimes I'll have to actually turn the machine off, and clear the PRAM to get the sound to come back. Sometimes, the volume and screen controls will both not work at all (pop up doesn't even appear when the keys are pressed), sometimes it's just that the sound doesn't work, but everything looks right on the screen. I've also had the sound and screen buttons not work only to have pop ups suddenly appear and the adjustments happen several minutes after I pressed the keys. So far I've tried:
Clearing the PRAM
Checked the Pram Battery (ok)
Reinstalled Tiger (Still loses sound)
Downgraded to 10.3 (problem persists, and seems worse)
In system information on Tiger it says "there was an error when retrieving that information" when you click on the sound hardware.
The machine is a 500mhz Pismo with a 48gig drive and 1 gig of Memory (133mhz, would that cause this sort of problem?)
I have not tried going back to OS9 to see if the disappearing sound resolves as I don't currently have an OS9 disk.
This sure seems like a software problem, but I'm starting to wonder. I really like this machine and want to get it to work! Help!

Maxstang, welcome to Apple Discussions.
Did you repair permissions after you installed Tiger? Have you updated Tiger to 10.4.11?
Here's the Sound troubleshooting info in the Pismo Service Manual.
No sound from speaker(s)
1. Verify mute mode is not enabled (F6 on the keyboard).
2. Check the volume setting in the Sound control panel.
3. Verify no external speakers or headphones are plugged in.
4. Reset PRAM.
5. Make sure speaker cable is plugged into sound card.
6. Replace sound card.
7. Replace speakers (part of the top case).
8. Replace I/O logic board
Startup sound is heard, then no sound from speaker(s)
1. Remove sound preferences from System Folder, reset PRAM,
then restart.
2. Perform clean installation of system software.
Had the Pismo previously had OS X installed. There's a firmware update (Boot ROM version 4.1.8) that should be installed prior to installing OS X. However, when I got my Pismo with Tiger installed, the firmware was not updated (have since updated). However, I don't think this could be the cause of your problem, since I had no sound problems when the update was not installed.
The PC133 RAM (which runs at 100MHz) should not be the problem. I have PC133 RAM in my Pismo.
Since you replaced the HD, could you have disturbed the connection to the Sound Card. The Sound Card is located to the upper-right of the HD. Here's a helpful laptop site.
Fix It Guides for Mac Laptops & Mini
http://www.ifixit.com/Guide/
The guides can be viewed on-line or you can download a PDF file.
 Cheers, Tom
(='.'=)
(")_(")

Problems auto-connecting after sleep & startup (Changed from WPA to WEP)

Okay, I know there have been several issues similar to this, but after two days of sifting through posts, I still can't resolve this.
A few days ago I switched my AirPort network security from WPA to WEP-128. This was required to allow my Nintendo DS to connect to the netwrok, by the way. After the change, two similar, but slightly different problems started:
My 15" PowerBook G4 no longer auto-connects to the network at startup. The network is listed in the drop-down, and connects with no problem when I choose it manually. The computer seems to have no problem re-connecting after waking from sleep, which is odd because...
My other PowerBook, a 12" G4, won't auto-connect at startup AND won't re-connect after sleep. As above, it has no problem connecting using the Keychain once the network is selected from the drop-down.
So far I have tried, on both machines:
- trashing the system airport prefs
- deleting and resetting the network's keychain entry
- repairing the keychain (no errors found)
- turning off some unneeded power mgt options
- disconnecting USB peripherals
I have also reloaded the software on both my AirPort Extreme base and my AirPort Express hub, as well as restarting both hubs. I've also made sure that AirPort is at the top of the network connection list.
Both laptops are running 10.4.3 and have all the latest software updates installed.
What am I missing?
Thanks.

Both of these replies are helpful, in that they help confirm something I figured out this morning, almost accidentally.
One thing I didn't mention was that during the change from WPA to WEP I changed the network password. Now, I assumed that since the Keychain seemed to be working and I could get on the network manually without needing to enter the password each time, that meant the new password had correctly propagated throughout the system.
So, this morning I go into the Network settings, switch from Automatic to Preferred, select my network, look at the properties, and notice that somehow it has way too many bullets for that to be the correct password. I re-entered the password and that seems to have solved the problem. The new password I had entered somehow didn't make it into this setting. I guess trashing the network prefs, or renaming the network would have had the same effect.

Still problems with external harddrive after sleep although 10.8.5 supplemental update is installed

I am on an iMac 24" late 2007. The external drive is a Hitachi (HGST) Touro 1TB (other drives are fine and never had a problem not even before the supplemental update). Disk utility finds no problems with the HD (had volume repaired never the less).
Is this just my iMac or are others here also still confronted with hd sleep problems after the supplemental update?
Thanks for your input.

I'm not having those same problems, but my USB3 external drives attached via a USB3 hub still are ejected improperly when the machine goes to sleep. Also, I've had aliases on the desktop disappear for no reason. I regret updating to 10.8.5 due to all the weird problems, and the supplemental update fixed a few things but it's still buggy... Fortunately, no data corruption from this. I keep my fingers crossed.
Since desktop sales represent 15% of Apple's revenues (and dropping), it's just a matter of time before they dump desktops all together. I see no reason why Apple would care if the desktop OS is buggy.

Mail login problems after sleep (lion/MBP)

Sometimes after sleep, Mail will not load passwords from the keychain. I have to force quit Mail and restart it once or twice -- then it functions normally again. So, I know that the passwords are indeed saved and accessible, it's just that Mail doesn't find them after sleep. Any ideas?? I have an active internet connection at these times, as I start up Safari first which loads any page just fine. Thanks in advance for any input! (This problem started with a new MBP & Lion.

Hello,
I share the same problems as you do with my MacBook Pro Late 2011.
For me this has happened only since I have upgraded to Mac OS X 10.8
I must say it has got a little better and does now go online fine after coming out of sleep once I applied the 10.8.2 update the other day.
I wonder if this is a bug relating to the different account types. I have a few email accounts running and like you these are, POP, IMAP and MS Exchange. Maybe if it had one account it's fine and that is the reason why not many people have complained about it?

Problems after sleep modus

hello everybody
my iMac G5 does not refresh, after sleep modus!? the system clock and safari are hanging and I have to refresh them manually. the problem occurs, since I've got the logicboard replaced... any idea?
kind regards!
iMac G5 Mac OS X (10.4.10)

Hi BettyBlue-
Greetings and welcome to the Apple boards.
It sounds like it could be a bad battery on the logicboard. However, in light of the fact that it has been happening since it was repaired why not take it back and insist that it is repaired correctly?
Make sure to start it up and make sure it works at the service facility before accepting that it is repaired.
Luck-
-DaddyPaycheck

Mail connection problems after sleep

Hi, since upgrading to new retina macbook pro my mail works although not well, most times it will not connect after sleeping, I need to close mail, sometime it will not close and requires a force close, and sometime not all acounts come back on line and I may need to shut down a second time to achieve this.
I do run 5 different email accounts, POP, IMAP and exchange and have a large amount of mail.
Hope someone can help, thank you..

Hello,
I share the same problems as you do with my MacBook Pro Late 2011.
For me this has happened only since I have upgraded to Mac OS X 10.8
I must say it has got a little better and does now go online fine after coming out of sleep once I applied the 10.8.2 update the other day.
I wonder if this is a bug relating to the different account types. I have a few email accounts running and like you these are, POP, IMAP and MS Exchange. Maybe if it had one account it's fine and that is the reason why not many people have complained about it?

Problems waking up after sleep since 10.8.3 update

A couple of weeks ago, I updated to 10.8.3. Since then, I have been having difficulty waking the machine after sleep. I get the constant beach ball. On a forced restart, I will get the spinning gear followed by the prohibitory sign, like it can't find the OS. I have tried rebooting in safe mode, resetting PRAM/NVRAM, repaired disk and disk permissions with disk utility, checked the status of hardware with (AHT), reinstalled OS X (twice), but the problem persists. I'm at a loss and have no idea what else to do.
I'm seriously regretting upgrading from Snow Leopard at all.
I've been trying to run time machine to back everything up, but my external USB backup disks keeps randomly unmounting, so I can't even get a solid backup now.
Please help.

No, it has nothing to do with being Friends or not.
There are more and more security issues with java, Oracle comes with updates almost every few weeks. Until lately Apple had it in theuir distribution system, but because of the security issues decided that it was not good business to distribute automatically this leaky system. So with new system updates the Java is removed to make sure the customers reinstall the latest version. You can download from both Oracle and Apple, but don't download from any other source.
Luckily I do not need it anymore and have not installed Java since a few months.

Leopard sleep problem which seems related to Entourage 2008...

Hi all,
I have a MBP (3,1) running 10.5.2 and I noticed about 3 months ago that if I left the lid open the energy saver triggered sleep wouldn't kick in (very hot laptop next morning syndrome).
I've read a number of other threads on Leopard auto-sleep problems (which pointed to the HP AIO frameworks) but this doesn't appear to be the same issue I have...
If I quit Entourage 2008 then the computer will sleep after the correct period of time - and that's with no other changes to my normal use. Of course I'd like to not have to worry about quitting Entourage each time I might, maybe, just possibly not be back at the computer for a while.
Now in the system log I do keep getting the following strange entries:
/Applications/Microsoft Office 2008/Microsoft Entourage.app/Contents/MacOS/Microsoft Entourage[914]: Warning: accessing obsolete X509Anchors.
I have no idea what this really does and I do appear to have such a file in the system called X509Anchors...
If I switch Entourage to Offline mode then the entries don't appear in the system log anymore but... the unit still won't sleep. It requires Entourage not to be running it seems.
Having not seen anything else on the discussions forum relating to Entourage 2008 preventing auto-sleep I'm beginning to wonder whether it's just me?!?
Anyone else seeing this effect? And most importantly, does anyone know of a fix?
I have tried the NMS sleep utility stuff and although it worked perfectly whilst I was testing it using Energy saver timings of 1 minute... as soon as I upped the time back to my usual 30 minutes for CPU sleep it failed to work again.
Any help much appreciated.

Ok two things based on the crash report and the steps you took right before the crash:
# Try to disable scrolling acceleration and restart Firefox. Does it continue to crash?
# Try Safe Mode and do the same task as above with email and the pdf [[Troubleshoot Firefox issues using Safe Mode]]
# Also pdf.js may be helpful to read pdfs in the meantime. You can change the default reader in the Preferences/Options > Application menu of Firefox.
# Try to clear out the downloads folder and update flash to version 14 (that should do it)
IF it crashes again please also provide the new crash signatures and we can take a look :-) Sorry for the crashing :-(

Strange after-sleep problem

Similar Messages

Maybe you are looking for