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

@siancu Never mind. From your posts it now reads as if you're on the typical 13A2093 as well.

Hi Guys,

I do not have this problems on my MBP 13" mid 2010. I updated ML to Mavericks from the app store. My build is

13A603.

Maybe we can start a survey of build numbers?

The only time i get the

"The USB device Apple Internal Keyboard / Trackpad may have caused a wake by issuing a remote wakeup (2)"

is when i wakeup the machine.

So as far as i can see the late 13 rMBP's all have a different buildnumber.

Well, no, I don't have yet the rMBP, I wanted to order one today actually :-). But I went through this thread to see if there are any solutions before ordering it.

I have a 2011 MBA which runs Mavericks (the App Store version) without any issues.

Niels P. wrote:

 

Oli.S72 wrote:

 

@mrakers85

Waiting is no problem for me either. What i am scared about is this scenario: one day, an update comes out.
"This fixes the problem of some MBPrs freezing" - and no more words than that.

 

Do i have buggy hardware, or not? Will the problem come back in 4 or 8 or (X) weeks when I plug in this new USB3 device for the first time? Was it a bug in software, or was it a bug in hardware and thy simply made Mavericks more tolerant about buggy hardware? I doubt we will ever know. And by this, I will never know whether I spent huge cash on something that was never the way it is supposed to be.

 

Have a look a Linux sources codes and you'll find drivers are full of work-arounds for buggy hardware. It's really quite common. As long as that fixes the issue and the system as a whole functions as promised that's not really an issue.

 

Keep in mind that hardware is designed to function within certain specifications. There isn't a big difference between something that's just within specs and something that just outside. I don't know about this particular problem but very often it's not a black or white situation.

 

Did Apple drop the ball on quality assurance? Sure. But that doesn't mean they would've rejected the hardware had they noticed the issue themselves. Adjusting the specifications and having the driver guys fix it would've been an option then just as much as it is now.

Very interesting, Niels. Thank you for your comment. I'll give Apple a few more days to fix this.

Oli.S72 wrote:

 

siancu wrote:

 

I've seen some reports earlier in the thread that reinstalling 13A603 from scratch does indeed solve the issue.

I must have missed that. Are you sure about this?

You can not install 13A603 on a rMBP late 2013. You can do a brand new installation but you will end op with the same build on your computer as with which the computer came with. So anyone saying you can must have misunderstood something. This is quite understanding since the length of this discusion.

Hi all

Not had a freeze in a while but as I haven't set that much up on mine yet I'm happy to do a reinstall and see if it fixes it.

My question is, if I do a reinstall I assume I get version 13A2093 again by installing from the recovery drive so how do I select a different build version to install?

I'll do it and post my findings, at least that will answer 100% once and for all if this is software or hardware

I'm pretty sure you end up with the same build only if you use the recovery mode.

You can instead re-download mavericks from the mac app store, choose not to install it when it's done, and then create a bootable install usb key using something like http://liondiskmaker.com (you'll need an empty 8gb flash drive). I've done it and it works fine.

Then you can reboot the machine from the flash drive, format the hard drive using disk utility and install the os from the mac app store (presumably still build a603).

So I would like to hear from somebody who has accomplished this and has currently a603 on his/her new 13" retina. I would do it but mine is still on the way (and sadly also very late so it won't be here for another ten days or so).

I could do a reinstall, too. My MBP has no personal data on it yet. Just installed a bit of my software through App Store.

btw: I did not have a freeze for the last 3 or 4 hours. But as I read, that does not mean a lot.

Nicola S wrote:

 

I'm pretty sure you end up with the same build only if you use the recovery mode.

You can instead re-download mavericks from the mac app store, choose not to install it when it's done, and then create a bootable install usb key using something like http://liondiskmaker.com (you'll need an empty 8gb flash drive). I've done it and it works fine.

 

Then you can reboot the machine from the flash drive, format the hard drive using disk utility and install the os from the mac app store (presumably still build a603).

 

So I would like to hear from somebody who has accomplished this and has currently a603 on his/her new 13" retina. I would do it but mine is still on the way (and sadly also very late so it won't be here for another ten days or so).

Would this process void my warranty in any way? Will I still be able to do updates in the future? Any risk in doing this? If not, I might as well go for it.

I have a mid 2012 15inch Macbook pro Retina which has started hanging frequently after updating to Mavericks build 13A603 (from app store). Extremely annoying, and I really hope Apple will make a quick fix for this.

Isak.B wrote:

 

I have a mid 2012 15inch Macbook pro Retina which has started hanging frequently after updating to Mavericks build 13A603 (from app store). Extremely annoying, and I really hope Apple will make a quick fix for this.

You get the errors about USB in the syslog?
hanging means the same issue as described here? keyboard and touchpad not responding, but otherwise all good?

Would this process void my warranty in any way? Will I still be able to do updates in the future? Any risk in doing this? If not, I might as well go for it.

Well technically you're installing apple software on apple hardware. I wouldn't say it's voiding anything, although by formatting the hard drive you're also erasing the original recovery partition. Another maybe safer option would be to install the mac app store version on an external usb hard drive and boot from that. this way you can check a603 safely without touching the original preinstalled software.

And yes you most definitely would be able to run updates in the future.

Fix it quickly pls , i am worried about  do my word assignments by rmbp

333333wade wrote:

 

Fix it quickly pls , i am worried about  do my word assignments by rmbp

Plug in an USB-Stick or USB-Mouse or something like this. It seems this prevents the MBP from freezing. Also, if it does freeze, close the lid and wait 10 minutes. Then open it and very likely it will be back to normal

Nicola S wrote:

 

Would this process void my warranty in any way? Will I still be able to do updates in the future? Any risk in doing this? If not, I might as well go for it.

 

Well technically you're installing apple software on apple hardware. I wouldn't say it's voiding anything, although by formatting the hard drive you're also erasing the original recovery partition. Another maybe safer option would be to install the mac app store version on an external usb hard drive and boot from that. this way you can check a603 safely without touching the original preinstalled software.

And yes you most definitely would be able to run updates in the future.

alright, I'd love to do this. You have a link or somehting where I can read what exactly to do?