Sleeping problems and crashes in 10.9

[Mac Hammer Fan]

Since I upgraded to 10.9, it takes a long time before my Mac Pro goes to sleep when I select the "sleep" command in the finder menu. Sometimes, when the computer awakes, it hangs and it is a hard crash, because the only solution is to press the power button. I have never experienced this with 10.6-10.8.
My startup disk is an OWC SSD Mercury Extreme, I have never had problems with it, until now. 10.9.1 didn't solve the problem.
Booting under 10.6.8 under another disk doesn't give this problem.

 

[Mac Hammer Fan]

Some additional info: I have a Calldigit USB3 eSata card installed. However, there are no sleeping problems under 10.6-10.8 with the drivers installed.

 

[Mac Hammer Fan]

Problem still not solved under 10.9.1

I still have frequent hard crashes and it takes many seconds before my mac goes to sleep when I use the command "sleep". I reinstalled the Calldigit USB driver, it seems that the same driver is used under 10.8 and 10.9. The computer is rock stable when I choose a different startup disk with 10.6,7 or 8.

Please help.

 

[old-wiz]

have you tried removing the caldigit driver, just for testing?

And post the crash log; maybe we can see something.

 

[Mac Hammer Fan]

I checked the logs but there are no crashes registered from the past ten days, although I had several fatal lockups. Strange.
I will try uninstalling the Calldigit driver

 

[Mac Hammer Fan]

Uninstalling the driver doesn't solve the problem. Delays in sleeping and lockups remain. But only one time the logs says it is a crash:
Panic (system crashes) log:

Source: /Library/Logs/DiagnosticReports/Kernel_2014-01-10-201958_MacPro.panic
Size: 8 KB (7.692 bytes)
Last Modified: 11/01/14 11:24
Recent Contents: Anonymous UUID: 65667677-F579-95EE-2E6C-96B823FE550F

Fri Jan 10 20:19:58 2014
panic(cpu 0 caller 0xffffff8011adc19e): Kernel trap at 0xffffff7f93e8ebcc, type 14=page fault, registers:
CR0: 0x000000008001003b, CR2: 0xffffff7f93e8ebcc, CR3: 0x0000000014512000, CR4: 0x00000000000206e0
RAX: 0x00000000001f0000, RBX: 0xffffff8051cda600, RCX: 0xffffff8032a38c00, RDX: 0x00000000e0000340
RSP: 0xffffff81e4433c38, RBP: 0xffffff81e4433c90, RSI: 0x0000000000000000, RDI: 0xffffff8055570000
R8: 0xffffff81e4433cd0, R9: 0x0000000000000028, R10: 0xffffff81e4433cf0, R11: 0x0000000000000200
R12: 0x00000000e00002c2, R13: 0x00000000e0000340, R14: 0xffffff8051cda638, R15: 0xffffff8032a38c00
RFL: 0x0000000000010246, RIP: 0xffffff7f93e8ebcc, CS: 0x0000000000000008, SS: 0x0000000000000010
Fault CR2: 0xffffff7f93e8ebcc, Error code: 0x0000000000000010, Fault CPU: 0x0

Backtrace (CPU 0), Frame : Return Address
0xffffff81e44338c0 : 0xffffff8011a22f69
0xffffff81e4433940 : 0xffffff8011adc19e
0xffffff81e4433b10 : 0xffffff8011af3606
0xffffff81e4433b30 : 0xffffff7f93e8ebcc
0xffffff81e4433c90 : 0xffffff8011ea45f1
0xffffff81e4433d40 : 0xffffff8011e8f6d9
0xffffff81e4433d80 : 0xffffff8011ea1ce4
0xffffff81e4433e10 : 0xffffff8011ede48d
0xffffff81e4433e40 : 0xffffff8011e97eac
0xffffff81e4433eb0 : 0xffffff8011ea6ba4
0xffffff81e4433ef0 : 0xffffff8011ea6caf
0xffffff81e4433f30 : 0xffffff8011eac522
0xffffff81e4433f80 : 0xffffff8011eac5f7
0xffffff81e4433fb0 : 0xffffff8011ad6aa7

BSD process name corresponding to current thread: kernel_task

Mac OS version:
13B42

Kernel version:
Darwin Kernel Version 13.0.0: Thu Sep 19 22:22:27 PDT 2013; root:xnu-2422.1.72~6/RELEASE_X86_64
Kernel UUID: 1D9369E3-D0A5-31B6-8D16-BFFBBB390393
Kernel slide: 0x0000000011800000
Kernel text base: 0xffffff8011a00000
System model name: MacPro5,1 (Mac-F221BEC8)

System uptime in nanoseconds: 20042820170752
last loaded kext at 20015412073822: com.apple.driver.AppleUSBCDC 4.2.1b2 (addr 0xffffff7f93e82000, size 20480)
last unloaded kext at 19941437551695: com.apple.driver.AppleUSBCDC 4.2.1b2 (addr 0xffffff7f93e82000, size 16384)
loaded kexts:
com.taoeffect.ispy.kext

 

[Mac Hammer Fan]

I reset the SMC and the problem isn't solved.

 

[Weaselboy]

com.taoeffect.ispy.kext

Get rid of that Espionage app you installed and this kext that comes with it. There have been a few threads about that causing KPs on Mavericks.

 

[Mac Hammer Fan]

I can't find com.taoeffect.ispy.kext even not by making invisible files visible.
I trashed some other files containing the word ispy

 

[Weaselboy]

I can't find com.taoeffect.ispy.kext even not by making invisible files visible.
I trashed some other files containing the word ispy

Try opening Finder then hit shift-command-g (all the keys at once) and paste in the path below then enter. That should bring up a folder with all your kext files.

Mavs does not seem to be searching the main Library folders for some reason.

/System/Library/Extensions

 

[Mac Hammer Fan]

I deleted all ispy files (Espionage). The delay in sleeping when I choose the sleep command in the finder isn't solved. I unchecked wake up for network access in the Energy Saver Control Panel. Fingers crossed....

 

[Weaselboy]

I deleted all ispy files (Espionage). The delay in sleeping when I choose the sleep command in the finder isn't solved. I unchecked wake up for network access in the Energy Saver Control Panel. Fingers crossed....

The sleep issue may be something else, but I bet getting rid of Espionage fixes your crash issue.

Look in Activity Monitor and see what third party process are running there that may be conflicting with Mavs.

Maybe try a safe mode boot by holding the shift key when booting and see how it sleeps from there. A safe mode boot starts without any startup items so that can help tell you if a third party startup or login item is causing troubles.

 

[Mac Hammer Fan]

The Espionage files are all deleted.
I tried to startup in the safe mode, but it doens't work. After Apple logo appears, a rotating wheel keeps spinning. The desktop doens't appear.

 

[MrAtheist]

sorry to hijack this thread... but i dont think the problem has to do with the apps you have, but more of the 'p'OS itself.

my problem with late 2013 rMBP pos is that it becomes unresponsive/crashed in the morning after i put it to sleep the night before. EVERY SINGLE EFFING MORNING.

I guess the pos crashes after a certain duration in sleep. From my day to day use throughout the day the pos wakes up fine from sleep. It only craps out on me when i need to continue my work in the morning and find that the pos is in deep sleep.