[chasg]

Hi All,

My early 2008 Mac Pro crashes/freezes at some point while sleeping. An upgrade from 10.8 to 10.9 didn't change the behaviour (I haven't tried a fresh install yet).

What did solve the problem is setting the Energy Saver setting to not sleep the computer or hard disks.

So, it's something happening when it is asleep, going to sleep, or perhaps at the moment I try to wake it up.

Is there some way for me to find out what was running just before it crashes? I've taken a look at the various logs in the Console, and I can't see an obvious culprit (but then I'm not an expert on unix processes).

Many thanks in advance for any help.

Chas

[jmiddel]

I remember this being and issue with past MBs and MBPs, which is why I never put them to sleep. You could post the console output, maybe someone can sort it out.

Have you run Apple's diagnostics?

Using Apple Hardware Test

And have you checked Disk Utility to see if the disk needs (software) repairs? I would run those tests.

I had a similar issue with a Macbook and there turned out to be an issue with the hard drive.

[chasg]

Originally Posted by jmiddel 

I remember this being and issue with past MBs and MBPs, which is why I never put them to sleep. You could post the console output, maybe someone can sort it out.

Thanks for the reply. I'm going to try the Apple Hardware Test (as mentioned below) before posting the Console output.

This Mac, by the way, has spent literally years on, with occasional restarts. This crash-while-sleeping problem has only been a problem for a few months.

Thanks again!

Chas

[chasg]

Originally Posted by And.reg 

Have you run Apple's diagnostics?

Using Apple Hardware Test

And have you checked Disk Utility to see if the disk needs (software) repairs? I would run those tests.

I had a similar issue with a Macbook and there turned out to be an issue with the hard drive.

Thanks for the reply, very much appreciated.

Disk Utility was my first stop, no problems with any of the disks in the machine, or attached to the machine.

I can't believe I forgot about the Apple Hardware Test app! I should've thought of that myself. One small problem: I have zero idea where any of the original discs are. Mine is an early 2008 Mac pro that shipped with early 10.5.x, and according to this page you sent me to, I have to boot from an original install disc to run the software. A quick search hasn't found a place from which to download a disk image, before I break out the deeper google-fu, do you happen know of a direct download location?

Thanks again, I really appreciate the tip.

Cheers!

Chas

[Ω]

Best thing to do is post the crash logs. I have it infrequently and it can be either FF or the screensaver going awol for me.

[chasg]

"Omega", I like that :-)

I'll turn on computer sleep and drive sleep tonight and let it crash and then post the logs. All of them, or a subset?

And am I risking revealing anything personal in these logs? (besides what daemons I'm running, which is ok). I've just had a quick look through, doesn't seem to be anything sensitive in there, but there are a lot of lines...

Thanks for the help!

Chas

[P]

Try rebooting while holding D. If it works, you get straight to the tester - if it doesn't, you have to find the discs, but you haven't lost anything while trying.

[chasg]

Thanks P, no joy with "D", unfortunately.

I never throw things like discs away, they must be around here somewhere!

[chasg]

Sorry this took so long.

Can't find original discs to run AHT :-(

I've confirmed that it's something to to with sleep, as I've prevented this machine from sleeping for a week, and it's been fine, 24/7 (both machine and HDs prevented from sleeping). I let it sleep last night, and crash-o-rama. Below is the log from Console. Some info though:

iTeleport is a VNC server (server runs on the Mac, iOS devices can see and control the Mac).
My address book won't sync, ever (incredibly annoying and inconvenient)

05/04/2014 00:00:24.384 AddressBookManager[1358]: Validate metadata timed out, cancelling
05/04/2014 00:00:27.128 xpcproxy[1365]: assertion failed: 13C64: xpcproxy + 3438 [D559FC96-E6B1-363A-B850-C7AC9734F210]: 0x2
05/04/2014 00:02:04.353 AddressBookManager[1369]: Validate metadata timed out, cancelling
05/04/2014 00:02:47.085 syncdefaultsd[1367]: **** globally delaying apps from syncing, next sync will be in 31s
05/04/2014 00:02:53.647 syncdefaultsd[1367]: **** globally delaying apps from syncing, next sync will be in 25s
05/04/2014 00:03:05.482 syncdefaultsd[1367]: **** globally delaying apps from syncing, next sync will be in 13s
05/04/2014 00:03:12.818 syncdefaultsd[1367]: **** globally delaying apps from syncing, next sync will be in 6s
05/04/2014 00:03:18.819 syncdefaultsd[1367]: **** globally delaying apps from syncing, next sync will be in 1s
05/04/2014 00:03:22.962 syncdefaultsd[1367]: **** globally delaying apps from syncing, next sync will be in 4s
05/04/2014 00:03:24.289 syncdefaultsd[1367]: **** globally delaying apps from syncing, next sync will be in 2s
05/04/2014 00:03:27.176 syncdefaultsd[1367]: **** globally delaying apps from syncing, next sync will be in 8s
05/04/2014 00:03:38.310 syncdefaultsd[1367]: **** globally delaying apps from syncing, next sync will be in 1s
05/04/2014 00:03:51.036 syncdefaultsd[1367]: **** globally delaying apps from syncing, next sync will be in 18s
05/04/2014 00:04:03.163 WindowServer[159]: device_generate_desktop_screenshot: authw 0x0(0), shield 0x7f833d921420(2001)
05/04/2014 00:04:03.194 WindowServer[159]: device_generate_lock_screen_screenshot: authw 0x0(0), shield 0x7f833d921420(2001)
05/04/2014 00:04:03.195 WindowServer[159]: device_generate_desktop_screenshot: authw 0x0(0), shield 0x7f833d921420(2001)
05/04/2014 00:04:09.393 syncdefaultsd[1367]: **** globally delaying apps from syncing, next sync will be in 2s
05/04/2014 00:04:11.955 syncdefaultsd[1367]: **** globally delaying apps from syncing, next sync will be in 1s
05/04/2014 00:04:21.542 syncdefaultsd[1367]: **** globally delaying apps from syncing, next sync will be in 27s
05/04/2014 00:04:28.787 syncdefaultsd[1367]: **** globally delaying apps from syncing, next sync will be in 20s
05/04/2014 00:04:32.781 iTeleport Connect[392]: INFO: Computer will sleep
05/04/2014 00:04:32.781 iTeleport Connect[392]: INFO: Disconnecting...
05/04/2014 00:04:32.781 iTeleport Connect[392]: INFO: Logging out
05/04/2014 00:04:42.801 iTeleport Connect[392]: INFO: OS still not asleep after 10 seconds
05/04/2014 00:04:49.206 syncdefaultsd[1367]: **** globally delaying apps from syncing, next sync will be in 1s
05/04/2014 00:04:52.541 AddressBookManager[1376]: Validate metadata timed out, cancelling
05/04/2014 00:04:52.815 iTeleport Connect[392]: INFO: OS still not asleep after 20 seconds
05/04/2014 00:04:53.000 kernel[0]: **** [IOBluetoothHostControllerUSBTransport][SuspendDevice] -- Suspend -- suspendDeviceCallResult = 0x0000 (kIOReturnSuccess) -- 0xf800 ****
05/04/2014 01:19:21.000 kernel[0]: Wake reason: RTC (Alarm)
05/04/2014 01:19:21.000 kernel[0]: RTC: Maintenance 2014/4/5 00:19:19, sleep 2014/4/4 23:04:53
05/04/2014 01:19:21.000 kernel[0]: RTC: PowerByCalendarDate setting ignored
05/04/2014 01:19:21.000 kernel[0]: RTC: PowerByCalendarDate setting ignored
05/04/2014 01:19:21.000 kernel[0]: Previous Sleep Cause: 5
05/04/2014 01:19:21.523 iTeleport Connect[392]: INFO: Computer awake from sleep
05/04/2014 01:19:21.523 iTeleport Connect[392]: INFO: Connecting after wake from sleep...
05/04/2014 01:19:21.523 iTeleport Connect[392]: INFO: Validating credentials.
05/04/2014 01:19:22.000 kernel[0]: **** [IOBluetoothHostControllerUSBTransport][SuspendDevice] -- Resume -- suspendDeviceCallResult = 0x0000 (kIOReturnSuccess) -- 0xf800 ****
05/04/2014 01:19:22.000 kernel[0]: **** [IOBluetoothHostControllerUSBTransport][SuspendDevice] -- Resume -- suspendDeviceCallResult = 0x0000 (kIOReturnSuccess) -- 0xf800 ****
05/04/2014 01:19:22.715 hidd[139]: MultitouchHID: device bootloaded
05/04/2014 01:19:23.000 kernel[0]: Ethernet [Intel8254x]: Link up on en1, 1-Gigabit, Full-duplex, Symmetric flow-control, Debug [792d,af48,0de1,0e00,cde1,3c00]
05/04/2014 01:19:23.583 configd[18]: LINKLOCAL en1: parent has no IP
05/04/2014 01:19:26.526 iTeleport Connect[392]: INFO: Launching VNCProbe for localhost:5900
05/04/2014 01:19:30.203 iTeleport Connect[392]: INFO: Logging in
05/04/2014 01:19:30.203 iTeleport Connect[392]: INFO: Can login, setting credentials and login target
05/04/2014 01:19:30.204 iTeleport Connect[392]: INFO: Host ID = 7664EDDD647FAF6D3AE5C55DD66DAA13
05/04/2014 01:19:30.204 iTeleport Connect[392]: INFO: Host ID = 7664EDDD647FAF6D3AE5C55DD66DAA13
05/04/2014 01:19:30.523 iTeleport Connect[392]: INFO: Signed in.
05/04/2014 01:19:30.806 apsd[98]: Unrecognized leaf certificate
05/04/2014 01:19:31.904 ntpd[112]: ntpd: wake time set +0.706843 s
05/04/2014 01:19:31.944 com.apple.time[209]: Interval maximum value is 946100000 seconds (specified value: 9223372036854775807).
05/04/2014 01:19:31.948 com.apple.time[209]: Interval maximum value is 946100000 seconds (specified value: 9223372036854775807).
05/04/2014 01:19:40.876 AirPlayUIAgent[333]: 2014-04-05 01:19:40.875851 AM [AirPlayUIAgent] Changed PIN pairing: no
05/04/2014 01:19:40.904 AirPlayUIAgent[333]: 2014-04-05 01:19:40.903775 AM [AirPlayUIAgent] Changed PIN pairing: no
05/04/2014 01:20:04.847 spindump[1389]: Saved diag report for powerstats version com.apple.SystemStats.Daily to /Library/Logs/DiagnosticReports/powerstats_2014-04-05-012004_G8.diag

And just in case the spindump in the last entry above is relevant, here is a bunch of it (sorry, I don't know how far to go back, there are thousands of lines):

Powerstats for: launchdadd
Microstackshots: 1 samples
Primary state: 1 samples state 0x10
Binary Images:
launchdadd (44.1.2) <6E304427-FDCA-315F-B84A-F366B9192F49> /usr/libexec/launchdadd
com.apple.CoreFoundation 6.9 (855.14) <617B8A7B-FAB2-3271-A09B-C542E351C532> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
libdyld.dylib (239.4) <CF03004F-58E4-3BB6-B3FD-BE4E05F128A0> /usr/lib/system/libdyld.dylib

1 CF03004F-58E4-3BB6-B3FD-BE4E05F128A0 + 13821
1 6E304427-FDCA-315F-B84A-F366B9192F49 + 29941
1 617B8A7B-FAB2-3271-A09B-C542E351C532 + 1202193
1 617B8A7B-FAB2-3271-A09B-C542E351C532 + 458933
1 617B8A7B-FAB2-3271-A09B-C542E351C532 + 461334
1 617B8A7B-FAB2-3271-A09B-C542E351C532 + 522526
1 617B8A7B-FAB2-3271-A09B-C542E351C532 + 522665
1 617B8A7B-FAB2-3271-A09B-C542E351C532 + 523076
1 6E304427-FDCA-315F-B84A-F366B9192F49 + 28290
1 6E304427-FDCA-315F-B84A-F366B9192F49 + 6911
1 6E304427-FDCA-315F-B84A-F366B9192F49 + 6495
1 6E304427-FDCA-315F-B84A-F366B9192F49 + 26042
1 617B8A7B-FAB2-3271-A09B-C542E351C532 + 395704
1 617B8A7B-FAB2-3271-A09B-C542E351C532 + 397789
1 617B8A7B-FAB2-3271-A09B-C542E351C532 + 399798
1 617B8A7B-FAB2-3271-A09B-C542E351C532 + 400540
1 617B8A7B-FAB2-3271-A09B-C542E351C532 + 404489
1 617B8A7B-FAB2-3271-A09B-C542E351C532 + 404657
1 617B8A7B-FAB2-3271-A09B-C542E351C532 + 248953
1 617B8A7B-FAB2-3271-A09B-C542E351C532 + 404931


Powerstats for: defaults
Microstackshots: 1 samples
Primary state: 1 samples state 0x90
Binary Images:
<15A7F842-3801-3E4E-8CDF-BEB793E83B04>
libsystem_kernel.dylib (2422.90.20) <20E00C54-9222-359F-BD98-CB79ABED769A> /usr/lib/system/libsystem_kernel.dylib
com.apple.CoreFoundation 6.9 (855.14) <617B8A7B-FAB2-3271-A09B-C542E351C532> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
libdyld.dylib (239.4) <CF03004F-58E4-3BB6-B3FD-BE4E05F128A0> /usr/lib/system/libdyld.dylib
libsystem_c.dylib (997.90.3) <6FD3A400-4BB2-3B95-B90C-BE6E9D0D78FA> /usr/lib/system/libsystem_c.dylib

1 CF03004F-58E4-3BB6-B3FD-BE4E05F128A0 + 13821
1 15A7F842-3801-3E4E-8CDF-BEB793E83B04 + 9348
1 15A7F842-3801-3E4E-8CDF-BEB793E83B04 + 11805
1 617B8A7B-FAB2-3271-A09B-C542E351C532 + 1376657
1 617B8A7B-FAB2-3271-A09B-C542E351C532 + 1375576
1 617B8A7B-FAB2-3271-A09B-C542E351C532 + 1008955
1 617B8A7B-FAB2-3271-A09B-C542E351C532 + 150814
1 617B8A7B-FAB2-3271-A09B-C542E351C532 + 264097
1 617B8A7B-FAB2-3271-A09B-C542E351C532 + 264546
1 617B8A7B-FAB2-3271-A09B-C542E351C532 + 835884
1 6FD3A400-4BB2-3B95-B90C-BE6E9D0D78FA + 185967
1 20E00C54-9222-359F-BD98-CB79ABED769A + 86210


Powerstats for: eacore
Microstackshots: 1 samples
Primary state: 1 samples state 0x90
Binary Images:
com.eizo.eacore 1.0.0 (1) <8C2B7F0F-D03D-A98F-A4C3-C5507101E384> /Library/Application Support/EIZO/*/cn6_eacore.app/Contents/MacOS/eacore
libsystem_kernel.dylib (2422.90.20) <C823B3BD-F818-3D7A-9FB7-9BDE00E2BEA1> /usr/lib/system/libsystem_kernel.dylib
libsystem_pthread.dylib (53.1.4) <8B1B7B84-1B5D-32A8-AC0D-1E689E5C8A4C> /usr/lib/system/libsystem_pthread.dylib

1 8B1B7B84-1B5D-32A8-AC0D-1E689E5C8A4C + 27854
1 8B1B7B84-1B5D-32A8-AC0D-1E689E5C8A4C + 11736
1 C823B3BD-F818-3D7A-9FB7-9BDE00E2BEA1 + 93934


Powerstats for: com.apple.CodeSi
Microstackshots: 1 samples
Primary state: 1 samples state 0x94
Binary Images:
com.apple.CodeSigningHelper 1.0 (1) <D14E30CD-D4F6-3B12-B6FF-8AF50484A95B> /System/Library/Frameworks/Security.framework/Versions/A/XPCServices/com.apple.CodeSigningHelper.xpc/Contents/MacOS/com.apple.CodeSigningHelper
libsystem_pthread.dylib (53.1.4) <AB498556-B555-310E-9041-F67EC9E00E2C> /usr/lib/system/libsystem_pthread.dylib
libxpc.dylib (300.90.2) <AB40CD57-F454-3FD4-B415-63B3C0D5C624> /usr/lib/system/libxpc.dylib
libsystem_kernel.dylib (2422.90.20) <20E00C54-9222-359F-BD98-CB79ABED769A> /usr/lib/system/libsystem_kernel.dylib
libdispatch.dylib (339.90.1) <F3CBFE1B-FCE8-3F33-A53D-9092AB382DBB> /usr/lib/system/libdispatch.dylib

1 AB498556-B555-310E-9041-F67EC9E00E2C + 24505
1 AB498556-B555-310E-9041-F67EC9E00E2C + 12024
1 F3CBFE1B-FCE8-3F33-A53D-9092AB382DBB + 16787
1 F3CBFE1B-FCE8-3F33-A53D-9092AB382DBB + 12195
1 F3CBFE1B-FCE8-3F33-A53D-9092AB382DBB + 18078
1 F3CBFE1B-FCE8-3F33-A53D-9092AB382DBB + 13875
1 F3CBFE1B-FCE8-3F33-A53D-9092AB382DBB + 21432
1 F3CBFE1B-FCE8-3F33-A53D-9092AB382DBB + 19198
1 AB40CD57-F454-3FD4-B415-63B3C0D5C624 + 41169
1 F3CBFE1B-FCE8-3F33-A53D-9092AB382DBB + 11169
1 20E00C54-9222-359F-BD98-CB79ABED769A + 89706


Powerstats for: revisiond
Microstackshots: 1 samples
Primary state: 1 samples state 0x15
Binary Images:
revisiond (160.2) <CC1179EC-BDCC-3062-AE83-90662E809333> /System/Library/PrivateFrameworks/GenerationalStorage.framework/Versions/A/Support/revisiond
libsystem_pthread.dylib (53.1.4) <AB498556-B555-310E-9041-F67EC9E00E2C> /usr/lib/system/libsystem_pthread.dylib
libsystem_platform.dylib (24.90.1) <3C3D3DA8-32B9-3243-98EC-D89B9A1670B3> /usr/lib/system/libsystem_platform.dylib

1 AB498556-B555-310E-9041-F67EC9E00E2C + 24505
1 AB498556-B555-310E-9041-F67EC9E00E2C + 12050
1 3C3D3DA8-32B9-3243-98EC-D89B9A1670B3 + 11841


Powerstats for: kdc
Microstackshots: 1 samples
Primary state: 1 samples state 0x14
Binary Images:
kdc (323.15) <0DDEA91B-2A3A-322A-A43A-F509064BA78B> /System/Library/PrivateFrameworks/Heimdal.framework/Helpers/kdc
libsystem_kernel.dylib (2422.90.20) <20E00C54-9222-359F-BD98-CB79ABED769A> /usr/lib/system/libsystem_kernel.dylib
libdispatch.dylib (339.90.1) <F3CBFE1B-FCE8-3F33-A53D-9092AB382DBB> /usr/lib/system/libdispatch.dylib

1 F3CBFE1B-FCE8-3F33-A53D-9092AB382DBB + 12626
1 F3CBFE1B-FCE8-3F33-A53D-9092AB382DBB + 13227
1 F3CBFE1B-FCE8-3F33-A53D-9092AB382DBB + 35256
1 F3CBFE1B-FCE8-3F33-A53D-9092AB382DBB + 28946
1 20E00C54-9222-359F-BD98-CB79ABED769A + 72624


Powerstats for: com.apple.ShareK
Microstackshots: 1 samples
Primary state: 1 samples state 0x94
Binary Images:
com.apple.ShareKitHelper 1.0 (185) <F3555027-01B2-30CF-B446-E9F96CB814BC> /System/Library/PrivateFrameworks/ShareKit.framework/Versions/A/XPCServices/com.apple.ShareKitHelper.xpc/Contents/MacOS/com.apple.ShareKitHelper
libsystem_pthread.dylib (53.1.4) <AB498556-B555-310E-9041-F67EC9E00E2C> /usr/lib/system/libsystem_pthread.dylib
libsystem_kernel.dylib (2422.90.20) <20E00C54-9222-359F-BD98-CB79ABED769A> /usr/lib/system/libsystem_kernel.dylib

1 AB498556-B555-310E-9041-F67EC9E00E2C + 24505
1 AB498556-B555-310E-9041-F67EC9E00E2C + 12050
1 AB498556-B555-310E-9041-F67EC9E00E2C + 9583
1 20E00C54-9222-359F-BD98-CB79ABED769A + 72921
1 20E00C54-9222-359F-BD98-CB79ABED769A + 72086


Powerstats for: sh
Microstackshots: 1 samples
Primary state: 1 samples state 0x94
Binary Images:
<F24FF69C-03B2-3999-9881-8CCA1C440F06>
libdyld.dylib (239.4) <CF03004F-58E4-3BB6-B3FD-BE4E05F128A0> /usr/lib/system/libdyld.dylib

1 CF03004F-58E4-3BB6-B3FD-BE4E05F128A0 + 13821
1 F24FF69C-03B2-3999-9881-8CCA1C440F06 + 424488


Powerstats for: NotificationCent
Microstackshots: 1 samples
Primary state: 1 samples state 0x94
Binary Images:
com.apple.notificationcenterui 1.0 (222.5) <ED2FC78D-FDFB-37D7-8DD3-1D3938E983DF> /System/Library/CoreServices/NotificationCenter.app/Contents/MacOS/NotificationCenter
libsystem_pthread.dylib (53.1.4) <AB498556-B555-310E-9041-F67EC9E00E2C> /usr/lib/system/libsystem_pthread.dylib
libsystem_kernel.dylib (2422.90.20) <20E00C54-9222-359F-BD98-CB79ABED769A> /usr/lib/system/libsystem_kernel.dylib

1 AB498556-B555-310E-9041-F67EC9E00E2C + 24505
1 AB498556-B555-310E-9041-F67EC9E00E2C + 12050
1 AB498556-B555-310E-9041-F67EC9E00E2C + 9583
1 20E00C54-9222-359F-BD98-CB79ABED769A + 72921
1 20E00C54-9222-359F-BD98-CB79ABED769A + 72086


Powerstats for: airportd
Microstackshots: 1 samples
Primary state: 1 samples state 0x95
Binary Images:
airportd (931.58) <D2D103C7-91C2-3DA0-89B3-91D2E11F261A> /usr/libexec/airportd
libsystem_kernel.dylib (2422.90.20) <20E00C54-9222-359F-BD98-CB79ABED769A> /usr/lib/system/libsystem_kernel.dylib
libdispatch.dylib (339.90.1) <F3CBFE1B-FCE8-3F33-A53D-9092AB382DBB> /usr/lib/system/libdispatch.dylib

1 F3CBFE1B-FCE8-3F33-A53D-9092AB382DBB + 12626
1 F3CBFE1B-FCE8-3F33-A53D-9092AB382DBB + 13227
1 F3CBFE1B-FCE8-3F33-A53D-9092AB382DBB + 35555
1 F3CBFE1B-FCE8-3F33-A53D-9092AB382DBB + 8727
1 F3CBFE1B-FCE8-3F33-A53D-9092AB382DBB + 10152
1 F3CBFE1B-FCE8-3F33-A53D-9092AB382DBB + 8727
1 F3CBFE1B-FCE8-3F33-A53D-9092AB382DBB + 11169
1 20E00C54-9222-359F-BD98-CB79ABED769A + 89706


Powerstats for: sandboxd
Microstackshots: 1 samples
Primary state: 1 samples state 0x94
Binary Images:
sandboxd (278.11) <929584FC-DC25-399C-B07B-D320BDDBA329> /usr/libexec/sandboxd
libsystem_kernel.dylib (2422.90.20) <20E00C54-9222-359F-BD98-CB79ABED769A> /usr/lib/system/libsystem_kernel.dylib
libdispatch.dylib (339.90.1) <F3CBFE1B-FCE8-3F33-A53D-9092AB382DBB> /usr/lib/system/libdispatch.dylib

1 F3CBFE1B-FCE8-3F33-A53D-9092AB382DBB + 12626
1 F3CBFE1B-FCE8-3F33-A53D-9092AB382DBB + 13227
1 F3CBFE1B-FCE8-3F33-A53D-9092AB382DBB + 35555
1 F3CBFE1B-FCE8-3F33-A53D-9092AB382DBB + 8727
1 F3CBFE1B-FCE8-3F33-A53D-9092AB382DBB + 10152
1 F3CBFE1B-FCE8-3F33-A53D-9092AB382DBB + 8727
1 F3CBFE1B-FCE8-3F33-A53D-9092AB382DBB + 11169
1 20E00C54-9222-359F-BD98-CB79ABED769A + 89706


Powerstats for: suhelperd
Microstackshots: 1 samples
Primary state: 1 samples state 0x95
Binary Images:
suhelperd (574.2) <9A1D2241-ED69-36FB-B9A6-BBE62EF37E09> /System/Library/PrivateFrameworks/SoftwareUpdate.framework/Resources/suhelperd
libsystem_kernel.dylib (2422.90.20) <20E00C54-9222-359F-BD98-CB79ABED769A> /usr/lib/system/libsystem_kernel.dylib
libdispatch.dylib (339.90.1) <F3CBFE1B-FCE8-3F33-A53D-9092AB382DBB> /usr/lib/system/libdispatch.dylib

1 F3CBFE1B-FCE8-3F33-A53D-9092AB382DBB + 12626
1 20E00C54-9222-359F-BD98-CB79ABED769A + 91746


Powerstats for: TabletDriver
Microstackshots: 1 samples
Primary state: 1 samples state 0x94
Binary Images:
com.wacom.TabletDriver (6.3.7f3) <DFF4E5CE-978E-375C-8686-60246F245AFD> /Library/Application Support/Tablet/WacomTabletDriver.app/Contents/Resources/TabletDriver.app/Contents/MacOS/TabletDriver
libsystem_pthread.dylib (53.1.4) <AB498556-B555-310E-9041-F67EC9E00E2C> /usr/lib/system/libsystem_pthread.dylib
libsystem_kernel.dylib (2422.90.20) <20E00C54-9222-359F-BD98-CB79ABED769A> /usr/lib/system/libsystem_kernel.dylib

1 AB498556-B555-310E-9041-F67EC9E00E2C + 24505
1 AB498556-B555-310E-9041-F67EC9E00E2C + 12050
1 AB498556-B555-310E-9041-F67EC9E00E2C + 9583
1 20E00C54-9222-359F-BD98-CB79ABED769A + 72921
1 20E00C54-9222-359F-BD98-CB79ABED769A + 72086

Any insights anyone?

Thanks in advance!

Chas

[Spheric Harlot]

Are the Wacom drivers and iteleport updated to the latest versions?

[chasg]

Good question, I'll check, gimmie 5 mins...

[chasg]

Yep, both are the latest versions.

Rats, I was hoping it was that easy!

[Spheric Harlot]

So was I.

[chasg]

:-)

[reader50]

The panic log may be more useful. Console may show it in /Library/Logs/PanicReporter, labelled by date. Choose the latest.

If we can't work it out via the logs, you could diagnose it the old-fashioned way. Disconnect one peripheral, PCIe card, or drive at a time. Sleep (maybe overnight), see if it crashes on wake.

[chasg]

Hi, thanks for helping.

No panic log in Console, and a search of both my user Library and the system's Library found no panic logs. I know that there have been panics in the past (it's a 2008 machine, after all), but none since I upgraded to Mavericks (a month or so ago).

It's unlikely it's a hardware issue, but good 'ole Sherlock was right about impossible vs. improbable, so I thank you for the advice. By the way, have you been around long enough to have needed to diagnose a problem with extensions in System 9? Best way was to disable half, and then half of those etc. Much faster than one at a time.

Thanks again!

Chas

[reader50]

Actually I have. But since it's a working machine, it was less disruptive to you to remove one hardware suspect at a time.

Any time your Mac boots up without having shut down properly, a panic log should be written out from nvram. The log should be somewhere, unless the system crashed before the kernel could get going again. Which would indicate a hardware cause. So either there's a log, or disconnecting suspects will eventually find it.

[chasg]

I thought you might have (no disparagement implied :-) What was that application that did it automatically? Man, I really loved that program.

I have a lull in work for a few days, so I'm going to disconnect everything at first. If "everything out" solves the problem, then I'll immediately know if it's a hardware issue (man, I hope it's not, I need everything that's installed).

I've done a full search looking for panic logs. I found the "reportpanic" app and all the html and xml files, but no actual logs. Is that a bit strange? There should be at least one, as I had to force-restart the machine this morning.

[reader50]

In Console, you have to toggle down the PanicReporter category. Or you could check the physical location:

Mac HD/Library/Logs/PanicReporter/

Caution: I'm still on 10.5.8, and Apple has moved the panic log(s) at least once. I don't have a recent system to verify that location.

Conflict Catcher. Though I never got it for some reason. If you rule out the peripherals and PCIe cards, don't forget the drives (including optical) and RAM sticks. And it might turn out to be a cable rather than the peripheral itself.

[chasg]

Conflict Catcher, that was it! Thanks, it was just starting to niggle in the back of my brain :-)

RAM and cables? Ok, you're much more thorough than I am. Can do.

No "PanicReporter" in the Logs folder (and just to be clear, I'm looking in the system Library, not the user Library). I've looked around, can't find a directory with that name anywhere. In Console, a search on "panic" gave no results, and I just manually looked through every log, nothing.

A quick google on "panicreporter" did find this very interesting thread at the Apple Support Communities:

https://discussions.apple.com/thread/5573663?tstart=0

Are you familiar with the "Etrecheck" application that was suggested?

[reader50]

I'd never heard of Etrecheck before. And apparently Apple moved the panic logs again in 10.6:

Mac HD/Library/Logs/DiagnosticReports/

[chasg]

Just ran Etrecheck, very nice, and thorough, summary of, well, tons of stuff.

Found the logs, thanks for the pointer. Nothing with "panic" in the name, could they have renamed the panic logs as well as have moved them?

I really appreciate all the time you're taking, but if it's too much, let me know.

[Spheric Harlot]

"DiagnosticReports" is the new crash log name.

The logs available in the diagnosticReports folder should also show up in console under that heading.

[chasg]

Got it! What I see in there in Console matches what I see in the Finder.

In Console, "DiagnosticReports" is a drop down, with various logs inside, it's not a log in and of itself. Of all the logs in there, the only one that seems relevant is named: "Finder,iStatServerDaemo,launchd,locationd,mDNSRes ponder,mds_2014-04-05-123730_G8.shutdownStall", what do you think? ("iStatServer" is a remote diagnostic app that I've just de-installed).

[Spheric Harlot]

Did you deinstall iStat BEFORE the machine crashed, or since?

If you deinstalled it before April 5th, then you didn't do it properly.

[chasg]

I installed it quite a while ago (long before this crash problem began? I couldn't tell you).

It has a nice "uninstall" command, I ran it just before telling you that I uninstalled it. I didn't try to uninstall it before that (I mention it to you because it was in the name of that log). fyi: I only uninstalled it because etrecheck pointed out that it was using 1% of CPU. I originally installed it to be able to check out the various temperature readings in the machine while away from my studio. I only looked a few times, and then forgot about the daemon. Oops, should've uninstalled it ages ago.

[Spheric Harlot]

iStatMenu has been associated with crashes in the past.

[chasg]

Well, that's good to know. I'll see how the machine behaves tonight when sleeping. Fingers crossed! (I really don't want to unplug everything...)

[chasg]

Well, I can at least confirm that removing istat and associated files isn't the solution (machine still failed while asleep). One variable down, an unknown number left to go! :-)

[D R Turbo]

If I were you I wouldn't even bother spending any more time trying to troubleshoot it because it's an OS bug. We use Scannerz (Scannerz and Scannerz Lite - Hard Drive and System Test Tools for Mac OS X) to test our stuff and ran into the exact same problem. We'd boot from a Firewire external drive with Mavericks on it and it would work fine. Once we let it go to sleep, on waking it up we got the spinning beach ball and a locked up system. I contacted SCSC who makes Scannerz and they said it was an OS bug. They had to put a "disable drives from falling asleep" option into their program to prevent drives from falling asleep.

They told us we could file a bug with Apple at:

http://bugreport.apple.com

but I kind of got the impression you have to be a registered Apple developer to use it.

[Spheric Harlot]

What triggers it? I haven't seen it, and my OS is set to let drives go to sleep.

[D R Turbo]

Sorry it took me so long to get back.

In my case disabling the "Put hard disks to sleep when possible" option under System Preferences -> Energy Saver options stopped it. They told me to try it and it did. But that was back in version 10.9.0 if I recall correctly. I'm running 10.9.2 now and now it's not a problem. There are a lot of problems being reported with Mavericks and drives, particularly external drives. Seems some people have various problems with the OS, others don't.

[chasg]

And I'd be one of those with problems :-)

Thanks for the followup.

[donaldkepler]

Have you checked the disk permissions and updated drivers status? May be it's due to any Script running behind any applications.

[Chongo]

I'm having the same issues with my mid 2007 20" iMac. I set no sleep on everything, including the screensaver and it is still freezing. On one restart I got the dreaded flashing folder. The iMac started up after being powered down for a night, but froze up again. Time for a new iMac?.

[P]

That sounds like an overheating issue. Have you tried cleaning out the vents?

Could also be that a capacitor has boiled over and is now dying, in which case yes, time for a new Mac. Not worth it to repair a seven year old Mac.

[Chongo]

Thanks. I'm looking at the 27" iMac. I like to shoot video for family/friends and create DVD. (will have to buy an external Blu-ray/DVD burner) Upgrading to the 4GB video card is a no brainer. Is it worth it to upgrade to the i7 from the i5, and 3TB or 3TB Fusion drive?

If clearing the vents fixes the problem, I'll send the 20" down to my mom's. Her windoze 7 machine keeps blue screening, and playing FB games is real slow.

[P]

Upgrading to a Fusion Drive or just an SSD is absolutely worth it. It is the single biggest upgrade you can make.

I paid for the upgrade to an i7 back when I bought my quadcore iMac. I did it because I wanted VT-d (if you don't know what that is, you don't need it...) but HT was a sweetener. In retrospect, it was absolutely a waste of money. HT only ever works if you have more threads than actual cores that need running at the same time, and in practice you very rarely have more than 4 threads working. The one case when it does help me is when I'm pegging all 4 cores doing something intensive - in my case re-encoding video using Handbrake - and want to keep working. In that case HT makes the other task a little more responsive.

The graphics card update is mainly if you want to game on it. The base 775M is a fine card as well, but of course 780M is stronger.

All in all, I suspect that there is an iMac update not too far away. nVidia has launched the low-end version of the next-gen GPU Maxwell (GM107, which replaces the GK107 in e.g. the base 27" iMac and the top 15" MBP), and given that it's a large performance boost and better battery life, I expect Apple will want to make an update that uses it before back to school-season. The top iMacs are unlikely to get a very big boost, though.

[akent35]

Originally Posted by Chongo 

Is it worth it to upgrade to the i7 from the i5, and 3TB or 3TB Fusion drive?

The i7 is a "decent" upgrade, but as P just said above, the Fusion, and even better SSD, upgrade is well worth it. My Mac Mini has an i7 processor, along with 4 gig of RAM. It initially came with a slow, 5400 rpm 1 TB drive, but I replaced it with a fast 256 Gig Samsung 840 Pro SSD, and installed the 1 TB drive in a nice, slim external case. Am I glad I did! The difference in speed is amazing, and I feel so much more productive with the upgrade.

I'm not sure if you can do an SSD upgrade yourself on an iMac, but I was able to do it with my Mac Mini. Not really difficult at all.

From another perspective, my Mac Book Air has an i5 Haswell processor, and it came with a 256 gig SSD. Again, it is fast enough for me. And, if I need to store large files, I can use the 5400 rpm drive from the Mac Mini in the external case, and attach it to the Air. Such was the case when my wife and I traveled to London last December, and to Florida in late January (I'm in Seattle). I placed quite a few movies and videos on that external drive, and we were able to watch them on the Mac Book Air. We'll do the same thing when we go to Iceland in late July.

[P]

Originally Posted by akent35 

I'm not sure if you can do an SSD upgrade yourself on an iMac, but I was able to do it with my Mac Mini. Not really difficult at all.

On a recent iMac, it is very difficult. Possible, but IMO not worth it. I have done it on a 2009 iMac, and I would have bought an SSD pre-installed if that had been an option at the time.

[akent35]

Originally Posted by P 

On a recent iMac, it is very difficult. Possible, but IMO not worth it. I have done it on a 2009 iMac, and I would have bought an SSD pre-installed if that had been an option at the time.

That's what I suspected.

If it were me, I'd go with just an SSD upgrade (256 gig should be plenty, at least for me), and then purchase an external drive, and attach it to the iMac.

[Chongo]

I have an EPP store through Freescale. The 1TB SSD is $940 so that is out of the question. The 1TB Fusion is $188, the 3TB is $329, 256GB flash $188 It sounds like the i5 is more than capable of handling iMovie. The i7 would be needed if I wanted to run Final Cut Pro or Adobe CS? I'm still using iDVD, perhaps I need to get newer burner software also.

[P]

The i7 gives you the following:

* Hyperthreading, which means that 1 core can act like 2 weaker cores, essentially. This makes some sense if you only have 1 or 2 cores to begin with, but with 4, the usage is limited
* 2 megs more L3 cache, from 6 to 8. Never hurt, but I've never seen that it makes a big difference either.
* 100 Mhz higher clockspeed - or 2.5% at max turbo

Honestly, don't bother.

[Chongo]

Thanks. I think the overheating could be caused by a fan going out. I have not heard it since I powered it up today. I'm going to run the Hardware test from my Tiger disk.

[akent35]

Originally Posted by Chongo 

I have an EPP store through Freescale. The 1TB SSD is $940 so that is out of the question. The 1TB Fusion is $188, the 3TB is $329, 256GB flash $188.

A 1 TB SSD is definitely overkill (and is EXTREMELY expensive!), unless you absolutely have to access real large files quickly. To me, the optimum option would be a 256 Gig Flash Storage, and a large capacity external drive. As long as you do not need too much space for applications on the Flash Storage, 256 gig should be enough. It is a BTO that does adds $200 (same for the 1 TB Fusion Drive) to the base cost of the i5 27" iMac. The size of the external drive is driven by your needs, although the price difference between 1 TB, 2 TB, and 3 TB is not that much. The external drive could be "speedier"if it has USB 3.0 ports and/or a Thunderbolt port. USB 3.0 is probably not too much more expensive than USB 2.0, but a drive with a Thunderbolt port would be. Another option would be to get a drive with a Firewire 800 port, and then you could purchase an Apple Thunderbolt-to-Firewire 800 adapter (about $49). I have an older external Seagate drive in a case, and it has 2 Firewire 800 ports, and one USB 2.0 port. I use the Firewire 800 port with the adapter whenever I need to connect the drive to my Mac Book Air. It is fast enough, at least for me.

Additionally, if you purchase another machine, or need to share/swap files with others, having the external drive (with USB connectivity) makes it much, much easier. And, of course, the external drive would be portable.

From what I understand, a 1 TB Fusion Drive in the iMac 27" combines a 1 TB Hard Disk drive with NAND Flash Storage (128 gig SSD) and presents it as a single Core Storage managed local volume with the space of both drives combined. Maybe someone else has information as to which setup would be faster: 1 TB Fusion drive, or a 256 gig SSD with a 1 TB External drive. I myself am quite pleased with just having a 256 gig SSD inside each of my machines.

[Chongo]

Originally Posted by Chongo 

Thanks. I think the overheating could be caused by a fan going out. I have not heard it since I powered it up today. I'm going to run the Hardware test from my Tiger disk.

No issues found.

[akent35]

Chongo,

Here is a link (one of them) from a google search I just did "Fusion Drive vs. SSD Drive and External Drive":

Fusion, or pure SSD? - Ars Technica OpenForum

I have not read all of it, but it seems informative.

To me, the deciding factor (if it's important to you) would be the portability of an external drive. As I mentioned above, that works great for me.

[Chongo]

Choices choices. My current iMac has 320GB and I have 92Gb available, so I'd have to go 512Gb($470). The 3TB Fusion looks like abetter option for me. ($329). Maxing the RAM@ 32GB will also help loads.

[Spheric Harlot]

Originally Posted by akent35 

A 1 TB SSD is definitely overkill (and is EXTREMELY expensive!), unless you absolutely have to access real large files quickly.

I got my 960 GB Crucial m500 SSD for about 360€ plus taxes.

That is absolutely not "EXTREMELY" expensive. It was well budgetable within a month or so, and the benefits have been SO worth it.

It's considerably more than a spinny disk, of course, but this thing just put an extra year of life in my MacBook Pro and made it feasible for stage use (which it wasn't before: I don't trust rotating disks with vibration).
Each of those alone would have made the purchase worth it.