Friday, 28 February 2014

Hmmm, Mac OS X, one problem fixed, another one pops up ?

So, a few days ago, I posted this: -

about a problem that I was seeing with kernel_task taking >80% CPU on my Mac, whilst running OS X 10.9.1.

For me, quitting iTunes appeared to resolve the problem.

Then, earlier this week, Apple released OS X 10.9.2 to resolve a problem with the so-called Goto Fail bug.

This was also supposed to resolve the problem with kernel_task, and, I must admit, I've not seen that since.

However, I have seen a few issues with the Mac failing to properly resume from suspend ( in other words, wake up when I open the lid ).

Well, the Mac Crash Reporter did pop up earlier today, with this: -

Date/Time:       2014-02-28 06:18:01 +0000
OS Version:      10.9.2 (Build 13C64)
Architecture:    x86_64
Report Version:  18

Event:           Sleep Wake Failure
Steps:           0

Hardware model:  MacBookPro10,1
Active cpus:     8

Code: 0x13006c00�                                                                                  
Model: MacBookPro10,1, BootROM MBP101.00EE.B02, 4 processors, Intel Core i7, 2.3 GHz, 16 GB, SMC 2.3f36
Graphics: Intel HD Graphics 4000, Intel HD Graphics 4000, Built-In, 1024 MB
Graphics: NVIDIA GeForce GT 650M, NVIDIA GeForce GT 650M, PCIe, 1024 MB
Memory Module: BANK 0/DIMM0, 8 GB, DDR3, 1600 MHz, 0x80AD, 0x484D5434314753364D465238432D50422020
Memory Module: BANK 1/DIMM0, 8 GB, DDR3, 1600 MHz, 0x80AD, 0x484D5434314753364D465238432D50422020
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0xEF), Broadcom BCM43xx 1.0 (
Bluetooth: Version 4.2.3f10 13477, 3 services, 15 devices, 1 incoming serial ports
Network Service: Wi-Fi, AirPort, en0
Serial ATA Device: APPLE SSD SM256E, 251 GB
USB Device: Hub
USB Device: FaceTime HD Camera (Built-in)
USB Device: Hub
USB Device: Hub
USB Device: Apple Internal Keyboard / Trackpad
USB Device: BRCM20702 Hub
USB Device: Bluetooth USB Host Controller
Thunderbolt Bus: MacBook Pro, Apple Inc., 23.4

This came up after I'd had to power on the Mac, as it was failing to awaken ( I didn't try and kiss it; perhaps I should've done so ?? )

I've sent the report off to Apple, let's see what happens :-)


Unfed said...

Same thing with my mid 2012 retina MBP. I leave the system on at my desk most of the time and have it automatically sleep. Most days since I installed 10.9.2, upon returning I find the system has crashed with a Sleep Wake Fault.

Dave Hay said...

Interesting, I've only had it happen once - thus far :-)

Unfed said...

It's getting a little old having to move windows around every morning, so I've just turned off automatic sleep when connected to a power supply, which is most of the time for me. Sure enough, every morning since 10.9.2 I've walked into my office to find a system that crashed; I suspect disabling sleep will "fix" the problem for now.

Dave Hay said...

@Unfed, so I've still got Power Nap enabled, but haven't seen any problems since the original post. Will continue to monitor .....

David Cuthbert said...

Interesting... seeing this same error on my late 2013 retina MBP (11,3), too. For me, it's a few times/week, but doesn't correlate to being plugged in vs on battery; happens on both power sources.

Dave Hay said...

@David - I assume you're at the latest level of OS X 10.9.2 ?

David Cuthbert said...

Yep, though this was happening on 10.9.1 as well. Given the lack of widespread impact, I wonder if this is driver related; you're not, perchance, also running VMware Fusion or the Cisco AnyConnect VPN, are you?

Dave Hay said...

@David - I do run VMware Fusion, but no longer run Cisco AnyConnect, cheers, Dave

Grokking grep

A colleague was tinkering with grep  and, thanks to him, I discovered a bit more about the trusty little utility. I had not really explored ...