Q: New Retina Macbook pro 13 Haswell system hang/unresponsive

They better fix it within the week or I predict quite a few returns

After kb stoped responding system was working fine. I was working on VirtualBox with Windows 7 and it was runing fine. Just KB and touchpad didnt work.

For those of you having the keyboard/trackpad freeze issue, you may not have to do a hard reset (and lose your work). Try this instead:

Close your Macbook (i.e. put it to sleep) and wait 5-10 minutes and wake up the computer again. This may make the keyboard/trackpad come back to life. Most people are not patient and are resetting by holding down the power button.

Same problem. MPR retina 13 inch bought friday, I had this problem twice during two different uses ( web browing and gaming ). Hope it's just software and not hardware too.

Mine is exactly the same...

Any solution?!

Im seeing this issue as well.  13.3 inch Haswell 8gb 256.  The two times it has happened i was using the messages app in fullscreen mode.  Only other software installed is adobe creative cloud, dropbox and filezilla.

I've read conflicting reports on tech sites. Can anyone comment whether it's an issue solely confined to the 13" rMBP or is it affecting also the 15" version?

To be clear, sleep/resume will *sometimes* fix the issue.  It worked in only one of multiple instances of this freeze for me.  Every other time I've had to power off/restart to resolve the issue.

I don't have this issue at all on my new 13" retina with 8 GB and 256GB SSD.

I ran every beta version of Mavericks on my old 13" retina and it doesn't have any issues either.

I do keep my system pretty cleared out by running Cocktail or Clean My Mac regularly.

Has anyone tried using Caffeine (or similar apps) to prevent it from sleeping? I stopped using Caffeine to see if the new hardware and Mavericks would alleviate some of the quirks I had with my old Mac (they weren't bugs, just personal preferences). I've turned it back on and hopefully, if this issue has to do with sleeping, it will serve as a temporary fix until Apple resolves it. I'll write back in a day or two.

Another thought.  I note that my new 13" rMBP shipped with Mavericks build 13A2093 on it.  The release version of Mavericks is 13A603.  13A603 on my 15" rMBP does *NOT* exhibit this issue.

Has anyone tried force installing 13A603 over the shipped version on the new machines?  May try it myself shortly.

That's not a solution, that's a forced time-out.

@tomwynne

I can confirm that, my new MBP retina has the same build.

Also for the people who post on this page, please submit your issue here (credits belong to binbashdevnull):

https://docs.google.com/forms/d/1QBSLV-bEuxyBUNtFmzDbTWl2Tu3EFU4IPNNvobhKdPA/vie wform

My rMBP have the some problem. It happend 5 times in 2 days.

Processor  2.4 GHz Intel Core i5

Memory  8 GB 1600 MHz DDR3

Graphics  Intel Iris 1024 MB

Software  OS X 10.9 (13A2093)

Logs:

2013-10-28 21:40:17 +0800 kernel[0]: The USB device Apple Internal Keyboard / Trackpad (Port 5 of Hub at 0x14000000) may have caused a wake by issuing a remote wakeup (2)

2013-10-28 21:40:38 +0800 kernel[0]: The USB device Apple Internal Keyboard / Trackpad (Port 5 of Hub at 0x14000000) may have caused a wake by issuing a remote wakeup (2)

2013-10-28 21:41:30 +0800 mds[61]: (Normal) Volume: volume:0x7fdf3a83b200 ********** Bootstrapped Creating a default store:0 SpotLoc:(null) SpotVerLoc:(null) occlude:0 /Volumes/firmwaresyncd.j9PSjl

2013-10-28 21:41:59 +0800 WindowServer[89]: _CGXSetWindowBackgroundBlurRadius: Invalid window 0xffffffff

2013-10-28 21:41:59 +0800 loginwindow[65]: find_shared_window: WID -1

2013-10-28 21:41:59 +0800 loginwindow[65]: CGSGetWindowTags: Invalid window 0xffffffff

2013-10-28 21:41:59 +0800 loginwindow[65]: find_shared_window: WID -1

2013-10-28 21:41:59 +0800 loginwindow[65]: CGSSetWindowTags: Invalid window 0xffffffff

2013-10-28 21:41:59 +0800 kernel[0]: The USB device Apple Internal Keyboard / Trackpad (Port 5 of Hub at 0x14000000) may have caused a wake by issuing a remote wakeup (2)

2013-10-28 21:41:59 +0800 kernel[0]: AppleCamIn::systemWakeCall - messageType = 0xE0000340

2013-10-28 21:41:59 +0800 kernel[0]: AppleCamIn::systemWakeCall - messageType = 0xE0000340

2013-10-28 21:41:59 +0800 kernel[0]: IOPMrootDomain: idle cancel, state 1

2013-10-28 21:41:59 +0800 kernel[0]: AppleCamIn::systemWakeCall - messageType = 0xE0000290

2013-10-28 21:41:59 +0800 WindowServer[89]: device_generate_desktop_screenshot: authw 0x7f88bac5fa20(2000), shield 0x7f88bad0cab0(2001)

2013-10-28 21:41:59 +0800 WindowServer[89]: device_generate_lock_screen_screenshot: authw 0x7f88bac5fa20(2000), shield 0x7f88bad0cab0(2001)

2013-10-28 21:42:00 +0800 loginwindow[65]: ERROR | -[LWBuiltInScreenLockAuthLion closeAuthAndReset:] | Attempted to remove an observer when not observing

2013-10-28 21:42:00 +0800 com.apple.launchd.peruser.501[168]: The following job tried to hijack the service "com.apple.tsm.uiserver" from this job: 0x7f9e21c04430.anonymous.loginwindow

2013-10-28 21:42:19 +0800 kernel[0]: AppleCamIn::systemWakeCall - messageType = 0xE0000280

2013-10-28 21:42:19 +0800 kernel[0]: ARPT: 295.689358: AirPort_Brcm43xx::powerChange: System Sleep

2013-10-28 21:42:19 +0800 kernel[0]: ARPT: 295.689365: wl0: powerChange: *** BONJOUR/MDNS OFFLOADS ARE NOT RUNNING.

2013-10-28 21:42:19 +0800 kernel[0]: AppleCamIn::systemWakeCall - messageType = 0xE0000340

2013-10-28 21:42:20 +0800 kernel[0]: en0: BSSID changed to ec:17:2f:ca:48:00

2013-10-28 21:42:20 +0800 kernel[0]: ARPT: 296.182566: scanparams:

2013-10-28 21:42:20 +0800 kernel[0]: ARPT: 296.182568:   flags 0

2013-10-28 21:42:20 +0800 kernel[0]: ARPT: 296.182570:   active_time 0, passive_time 0

2013-10-28 21:42:20 +0800 kernel[0]: ARPT: 296.182572:   scan_start_delay 0

2013-10-28 21:42:20 +0800 kernel[0]: ARPT: 296.182574:   scan_cycle_idle_rest_time 0, scan_cycle_idle_rest_time_multiplier 0

2013-10-28 21:42:20 +0800 kernel[0]: ARPT: 296.182576:   max_scan_cycles 0, max_rest_time 0

2013-10-28 21:42:20 +0800 kernel[0]: ARPT: 296.182578: Scan Channels (0): None

2013-10-28 21:42:20 +0800 kernel[0]: ARPT: 296.182579: SSID (0): None

2013-10-28 21:42:20 +0800 kernel[0]: ARPT: 296.182581: SSID count = 0

2013-10-28 21:42:20 +0800 kernel[0]: ARPT: 296.182583: wl0: leaveModulePoweredForOffloads: Wi-Fi will turn off.

2013-10-28 21:42:20 +0800 kernel[0]: AppleThunderboltNHI::prePCIWake - power up complete - took 1332 us

2013-10-28 21:42:20 +0800 kernel[0]: AppleThunderboltHAL::earlyWake - complete - took 0 milliseconds

2013-10-28 21:42:20 +0800 kernel[0]: wlEvent: en0 en0 Link DOWN virtIf = 0

2013-10-28 21:42:20 +0800 kernel[0]: AirPort: Link Down on en0. Reason 8 (Disassociated because station leaving).

2013-10-28 21:42:20 +0800 kernel[0]: IOThunderboltSwitch<0xffffff802c76b800>(0x0)::listenerCallback - Thunderbolt HPD packet for route = 0x0 port = 11 unplug = 0

2013-10-28 21:42:21 +0800 kernel[0]: AppleCamIn::systemWakeCall - messageType = 0xE0000340

2013-10-28 21:42:21 +0800 kernel[0]: AppleThunderboltNHIType2::waitForOk2Go2Sx - retries = 8

2013-10-28 21:42:21 +0800 kernel[0]: AppleThunderboltNHI::prePCIWake - power up complete - took 0 us

2013-10-28 22:05:53 +0800 kernel[0]: Wake reason: EC.LidOpen (User)

2013-10-28 22:05:53 +0800 kernel[0]: AppleCamIn::systemWakeCall - messageType = 0xE0000320

2013-10-28 22:05:53 +0800 kernel[0]: AppleCamIn::systemWakeCall - messageType = 0xE0000340

2013-10-28 22:05:53 +0800 kernel[0]: AppleCamIn::wakeEventHandlerThr

So much for the idea of installing 13A603.  The installer won't run on my new machine.  Guessing it thinks the shipped/pre-installed version is newer.  Grrrr.

Another mainstream tech reviewer reporting on the issue;

http://www.techradar.com/news/mobile-computing/laptops/haswell-powered-macbook-p ro-retina-models-reportedly-freezing-mavericks-to-blame--1194127

The more media coverage the better