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

So what is every one doing about this? Waiting for an update (hopefully) or taking it in to the Apple Store? I'm in two minds about it. If anyone has taken theirs in, what has been the response?

I have had several lockups with Mavericks but have not seen the problem when using Windows 7 on the 13" Haswell.

bstpm wrote:

 

I have had several lockups with Mavericks but have not seen the problem when using Windows 7 on the 13" Haswell.

Thanks, this helps a lot

This indicates that it is a software problem for sure and will be fixed in the next mavericks update

bstpm wrote:

 

I have had several lockups with Mavericks but have not seen the problem when using Windows 7 on the 13" Haswell.

Could you please try to run 3Dmark 2011 if it will not freeze the whole thing as on my machine with Windows 8.1?

Thank you

I've been following this thread since it had 14 pages and now it's ballooned.

Some people have mentioned that installing the 13A603 GM build has eliminated the freezing problem but has anyone else who has been following this thread resorted to doing a clean build with 13A603? If so what were the results?

I'm waiting on a solution by Apple before making my purchase but I'm getting a little impatient. I've been considering buying the laptop and then immediately doing a whipe and then a fresh install of 13A603.

My main concern is that this is a hardware issue - though if so Apple may issue a software/driver update to fix it. However the case, a hardware issue is a hardware issue to me so I would like to know for sure that there is no hardware defect regardless of the type of fix Apple rolls out.

just received my replace macbook 13 haswell...no freeze (just too early...) but console still show the same error log. Waiting for update.

Not convinced it's a software issue.

I had my rMBP 13" 8gb/256ssd for one week, and CONSISTENTLY, about every hour or two, the trackpad and keyboard would freeze.

This unit also would power down randomly, and require multiple long pushes of the power button to revive it (not a common complaint in this forum discussing the freezing trackpad/keyboard).

The keyboard/trackpad DID NOT FREEZE as long as I had a USB flashdrive in one of the USB ports.

Well, I had had enough of both issues, so I exchanged my unit for the exact same one two days ago (same memory/ssd specs) and have had neither problem since (no USB flashdrive in use).

Although Apple says it is working on a fix, it's not clear to me that this will end up being a software fix.

Having said that, you can wait to exchange it for a new unit if it is indeed a hardware issue, but if you're in your 14 day exchange period from having just purchased it, I'd exchange it now rather than wait.

The stock at my local store has been a bit spotty for my unit (though the 4gb/128ssd seems to be well stocked).

Good luck everyone!

shadowku wrote:

 

I've been following this thread since it had 14 pages and now it's ballooned.

 

Some people have mentioned that installing the 13A603 GM build has eliminated the freezing problem but has anyone else who has been following this thread resorted to doing a clean build with 13A603? If so what were the results?

 

I'm waiting on a solution by Apple before making my purchase but I'm getting a little impatient. I've been considering buying the laptop and then immediately doing a whipe and then a fresh install of 13A603.

 

My main concern is that this is a hardware issue - though if so Apple may issue a software/driver update to fix it. However the case, a hardware issue is a hardware issue to me so I would like to know for sure that there is no hardware defect regardless of the type of fix Apple rolls out.

No one could have made such a statement. Try yourself and see what happens. You cannot install 13A603 on a 13" late 2013rMBP. You will end up with 13A2093. The software built is machine specific.

Mine only froze twice so far.  And I got a customized mac so if I want to exchange it I will have to wait much longer.  I hope they fix this quickly.

i reinstalled Maverick but it is 13A2093, you cannot install 13A603...

and i don't think that it is an Hardware problem

Another interesting thing (maybe already said): i'm using the apple wireless keyboard + magic mouse and the console stop to show the error, also when i've disconnected the 2 input devices...sound a lot strange.

Anyway, do you know what log are those?

04/11/13 10:31:43,000 kernel[0]: en0: BSSID changed to 00:1d:6a:b0:b8:48

Just wanted to say me too!

I unboxed and set up my brand new 13" rMBP 8GB/512GB and experienced the freeze about 1 minute after my first reboot.

Closing the display revived the trackpad/keyboard & I have found the same consistent kernel log msg that others have refered to showing up in the console:

The USB device Apple Internal Keyboard / Trackpad (Port 5 of Hub at 0x14000000) may have caused a wake by issuing a remote wakeup (2)

As others have mentioned, plugging in a USB stops the message, but it's too soon, in my case, to say whether that will prevent another lock up....

Seeing as Apple states this is a "rare" issue, I'm inclined to RMA the machine and try my luck with a new one, although the fact that this thread is as big as it is makes me think that it's more common than Apple would like to acknowledge...

Very disapointing.

I think they mean "rare" as in it only happens in certain circumstance, not that few machines are affected. I haven't returned mine because it only happens maybe every four or five hours of web surfing and a quick lid close/open fixes it. I do hope they release a patch for it soon though.

I have noticed that after mine froze i closed the lid, opned it 10 seconds later and started typing my password to log in but it didn't display.  I closed my lid again and reopened it a minute later and found that those characters i typed in for my password were now registering on the login page.  So it is weird.  After you reopen it prematurely it does take the input but doesn't display it on the screen.  I am thinking it is a software issue.