Prime95 shows strange timings after upgrade to Mavericks
 

So I upgraded my MacBook Pro to Mavericks (OS X 10.9.2) a few days ago. I just came home today to find that Prime95 has generated some strange timestamps:

[QUOTE][May 7 00:34] M69646037 stage 2 is 33.03% complete. Time: 82.513 sec.
[May 7 00:35] M69646037 stage 2 is 33.10% complete. Time: 81.091 sec.
[May 7 00:36] M69646037 stage 2 is 33.16% complete. Time: 79.306 sec.
[May 7 00:38] M69646037 stage 2 is 33.23% complete. Time: 77.664 sec.
[May 7 00:39] M69646037 stage 2 is 33.30% complete. Time: 76.756 sec.
[May 7 02:40] M69646037 stage 2 is 33.37% complete. Time: 7273.391 sec.
[May 7 04:41] M69646037 stage 2 is 33.43% complete. Time: 7264.168 sec.
[May 7 06:42] M69646037 stage 2 is 33.50% complete. Time: 7262.742 sec.
[May 7 08:43] M69646037 stage 2 is 33.57% complete. Time: 7265.107 sec.
[May 7 12:44] M69646037 stage 2 is 33.64% complete. Time: 14465.431 sec.
[May 7 14:45] M69646037 stage 2 is 33.70% complete. Time: 7263.805 sec.
[May 7 16:47] M69646037 stage 2 is 33.77% complete. Time: 7265.411 sec.
[May 7 18:48] M69646037 stage 2 is 33.84% complete. Time: 7264.645 sec.
[May 7 21:01] M69646037 stage 2 is 33.90% complete. Time: 8006.832 sec.
[May 7 21:02] M69646037 stage 2 is 33.97% complete. Time: 76.953 sec.
[May 7 21:04] M69646037 stage 2 is 34.04% complete. Time: 71.421 sec.
[May 7 21:05] M69646037 stage 2 is 34.11% complete. Time: 69.053 sec.[/QUOTE]

It appears as if someone woke my computer up from hibernation every two to four hours. However, I know that was not the case as my laptop had its lid closed the entire time while I was at work. Has anyone else ever seen something like this?

[QUOTE=ixfd64;372928]However, I know that was not the case as my laptop had its lid closed the entire time while I was at work.[/QUOTE]
Are you really certain about that? My kids tend to be curious and would open the lid if they could...

The strange thing is that it continued happening today:

[QUOTE][May 7 23:46] M70993963 stage 1 is 26.40% complete. Time: 60.985 sec.
[May 7 23:47] M70993963 stage 1 is 26.45% complete. Time: 60.883 sec.
[May 7 23:48] M70993963 stage 1 is 26.50% complete. Time: 61.655 sec.
[May 7 23:49] M70993963 stage 1 is 26.55% complete. Time: 90.350 sec.
[May 8 01:50] M70993963 stage 1 is 26.60% complete. Time: 7249.664 sec.
[May 8 03:51] M70993963 stage 1 is 26.65% complete. Time: 7243.015 sec.
[May 8 05:52] M70993963 stage 1 is 26.70% complete. Time: 7242.671 sec.
[May 8 07:52] M70993963 stage 1 is 26.75% complete. Time: 7243.170 sec.
[May 8 07:53] M70993963 stage 1 is 26.80% complete. Time: 44.365 sec.
[May 8 09:54] M70993963 stage 1 is 26.85% complete. Time: 7241.718 sec.
[May 8 11:54] M70993963 stage 1 is 26.90% complete. Time: 7242.820 sec.
[May 8 13:55] M70993963 stage 1 is 26.95% complete. Time: 7243.396 sec.
[May 8 15:56] M70993963 stage 1 is 27.00% complete. Time: 7242.074 sec.
[May 8 15:57] M70993963 stage 1 is 27.05% complete. Time: 44.462 sec.
[May 8 17:57] M70993963 stage 1 is 27.10% complete. Time: 7242.806 sec.[/QUOTE]

Notice how similar the intervals are. It's as if Prime95 was running even when the computer is supposed to be hibernating.

As it takes about 45 seconds for a checkin for P95 (in normal mode), it is very clear for me that your computer does something which takes ~42 seconds every two hours, or something that takes ~21 seconds every hour, or ~10 seconds every 30 minutes, etc (or other combinations). During this time, P95 catch a small slice of time too, progressing in its iteration. When the checkpoint is reached, it writes the log line. Your computer DOES wake up from hibernation in this time (there is no other explanation!) - assuming you are sure you put it in that state. Closing the lid does not mean that the computer went to hibernation. You can set what the computer does when you close the lid, and some programs can change that setting. You better check in the power options of the system, what the computer IS SET to do when the lid is closed.

I have no idea how to deal with a Mac in this situation. For a windoze system, I saw all the scary things in my lifetime, like taking camera snapsots every 5 minutes, encrypting them, and sending them to some IP address (no joke!). For a windoze system, I would start with event viewer, to see if some strange errors pop up periodically. Then, the task scheduler, cron jobs, etc. Most laptops today can wake up periodically by wifi, for example, or by RTC-related stuff, do something like telling "I am here" or "are you there?" to some peripherals, even without accessing the HDD, then go back to deep sleep. Trojans and viruses can do strange things, but many google application can do them too. Check for such unwanted stuff. Again, my Mac knowledge is very limited, can't tell you what to do or what programs to use. Other guys here may tell you much better. I am the windoze guy.

When you goto System Preferences->Energy Saver, is "Wake for network access" checked? If so, try turning it off.
How about "Power nap" feature? That sounds suspicious also.

Thanks for your help; unchecking "Wake for network access" stopped the issue. It wasn't bothering me or anything; I was just wondering why it was happening.

We wonder who/what sent the "[URL="http://en.wikipedia.org/wiki/Wake-on-LAN#Magic_packet"]magic packet[/URL]" that was waking your laptop up?

Or is it possible that the laptop woke up because it needed to access the network, even though it was asleep? (That is hard to imagine!)

Somewhat unrelated: We read that if you need to cart your laptop around it is safer to hibernate it rather than put it to sleep. If it is asleep and awakes, it could overheat in the carrying bag.

[QUOTE=Xyzzy;373146]We wonder who/what sent the "[URL="http://en.wikipedia.org/wiki/Wake-on-LAN#Magic_packet"]magic packet[/URL]" that was waking your laptop up?

Or is it possible that the laptop woke up because it needed to access the network, even though it was asleep? (That is hard to imagine!)

Somewhat unrelated: We read that if you need to cart your laptop around it is safer to hibernate it rather than put it to sleep. If it is asleep and awakes, it could overheat in the carrying bag.[/QUOTE]

I've attached a dump of the pmset command with the "-g log" option. I believe that may yield some clues.

I've also encountered the same overheating issue with the laptop from my previous job. It was scary as heck!