New Retina Macbook pro 13 Haswell system hang/unresponsive

Has anyone tried installing OS Mountain Lion on the new rMBP to check if this is a problem only with Mavericks.

I am currently running a Late 2010 MacBook Pro with i7 and I am having this issue after installing Mavericks. Seems the only way to get it back is to do a hard reset.

8GB/256GB SDD here. Same issues. Began last night.

Contacted and talked to a senior advisor. Reset SMC and PRAM then ran in safe mode for a couple of hours. Refroze after booting up normally.

I responded and added my number to the hundreds of others on the Google form.

I spoke on chat with support and made them aware. I sent a feedback report linking here, as well as a copy of the USB error in my console.

Also emailed a second senior advisor that I was able to speak with with all the information as well.

Chat support is going to have a THIRD senior advisor call me. They are supposed to check with Apple Engineering to give an update. Will post back when I hear.

Hi!

I don't have the rMBP 13". I have installed Mavericks on my mid-2010 MBP 15" and no issues so far. However, I understand and support all of you who are currently experiencing issues and invite you to contact Apple (report to Apple support, Apple Stores, Tim Cook, etc.). I have already sent emails to some of the execs in the probably vain hope that an answer will come soon.

I am holding the purchase of my late 2013 15" rMBP until some sort of resolution comes through!

Got my brand new Macbook Pro today and had a freeze at setting up my Macbook. But can't find anything in the kernellog (var/log/asl). I also had an update of Mavericks (MacBook Pro (Retina, 13-inch, Late 2013) Software Update, Version 1.0)

Just returned my rMBP 13' 8gb/256gb to apple until I hear that they've resolved this issue. So disappointed I had to do this!!!

And it's time for the community issue update!

So far this is affecting everyone. There is no permanent fix. People have "temporary" fixes, but it's just a matter of time.

I will no longer do the community poll results here. If you still wish to submit, please list your issue, please do so here.

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

To see the results. Click here.

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

Why? Well, we have 192 votes (at time of writing), and it is clear that everyone has the issue. I don't think knowing how much/many people have the issue with said configurations.

The poll will be up. It will not be taken down until this issue is resolved.

What can you do to make sure that you don't lose work?

• Save work often
• Carry a wired mouse in case
• IF AT ALL POSSIBLE, avoid OSX Mavericks for now
• Install Windows (Seriously, Windows doesn't have siad issue - OSX Mavericks Bug)

What have we learned so far? A temporary fix if Lockup Happens

• Put computer to sleep, Wake up after 5-15 minutes
• Plug in iPhone (Worked for some people)
• Plug in a Wired mouse and save work
• Set up Fast User Switching and switch users in the event of a lockup
• Reset SMC (can be a 'temporary band aid' - problem will still come back)
• Reset the PRAM (NVRAM) (Again, temporary, if works)
• Index your hard drive manually with Finder

Please let me know if in the above I have missed something! I was going to do a "Comminity issue update to the survey", but after 192 responses, we are basically nowhere.These responses tell us the following:Error happens:

• Regardless of RAM (4/8/16GB)
• Regardless of CPU (2.4/2.6/2.8 i5/i7)
• Regardless of weather you purchased it online or in store
• SSD Size (128/256/512GB and 1TB)

I have a 15" / Air from 20xx and I got a lockup

• Reading the comminity feedback has proven that:
  • a) 15" MacBooks from 20XX are not exempt from this issue!
  • While the cases of failure are less, they are still there
  • This leads us to belive that it has something to do with the controller of the touchpad/keyboard
  • May happen on all configurations
• Macbook Air 2012

  Has had this issue as well.

Windows doesn’t' crash?

Well it does, but not the issue we are having right now.

However, there is another issue with regards to installing Windows on the Late 2013 Haswell MacBook pros as outlined by MacRumors. The Forums link is here: https://discussions.apple.com/thread/5474320?start=0&tstart=0

I am not advocating Windows over OSX, as I am indifferent and not biased, but I would recommend, that if, a) returning is not an option or b) you do not wish to return the MacBook, but still want to stay productive, that you highly consider installing Windows on the MBPr for the time being.

Follow this tutorial for how-to on installing Windows on a Mac

http://support.apple.com/kb/ht1461

So, to sum it up....

This is a software issue! do not fear, Apple will fix it soon!

And remember, the community poll is in my signature (below!) remember to also submit a report to Apple with the appropriate link!

Thanks to all the members and community for helping us get this far!

And remember...

View results of issue specs:

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

Submit your issue to the comminity here:

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

And don't forget!

Report your issue to Apple directly!

https://www.apple.com/feedback/macbookpro.html

Remember, the more active this thread is, the better chance we have to get noticed!

A BIG Thanks to everyone who is contributing here!

Same issue for me.

I bought it on Friday and it happens 5 times on Saturday.

Then I go back to Apple Store and they give me another.

Unfortunately, it happens again for the second one.

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

when it lock the keyboard and the trackpad.

Also, I find if you leave your hand away from the keyboard and trackpad, then after a few seconds, you touch again, it will show the same log in the console.

It may be something wrong with the power saving?

I hope it is something wrong with the software or OS not something wrong with the hardware.

Because I do not want to go back to Apple Store again and install everything again and again.

Very upset for the first laptop from apple.😟

Just got mine late 2013 13" macbook, i have now followed how my console acts and it appears that "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)" error appears also to me. No freezes yet, but what i discovered is that if i keep pressing my keyboard or using my trackpad the error wont show. If i stop using those, it will almost immediately (prox. 10sec) appear to console.

Perhaps someone could submit this story to slashdot? Might get some attention and acknowledgement from Apple.

Also experiencing this issue. Hoping for a speedy response from Apple.

good idea.... I am not using slashdot. Anybody ???

Listen guys,I dont think this log 'The USB device Apple Internal Keyboard / Trackpad (Port 5 of Hub at 0x14000000) may have caused a wake by issuing a remote wakeup' has anything to do with freezing. I have been getting these messages in my console but no actual freezes. I got one 'freezing' for few mins yesterday when my battery went down to 12%. Cheers.

I get my mbp with retina 2013 next week, it's ordered (before I learned about this problems) and on the way to me ... I'm wondering if there are also users which DONT HAVE this issue?

Apple is aware of the problem.

I just spoke with Senior Advisor number 3. He and I talked through the issues, I referred him to the page.

He said the 8GB//256GB SSD was the one everyone ordered, so that being the big response is going to be no surprise.

They are working for a new software update. I am sending him a screen shot of my console. He is also aware that inserting a thumb drive has interrupted the error message we are all receiving.

Again, be patient. Apple has some of the best customer service in the world. New computers/hardware/OS are going to have issues. Why they weren't resolved before release - no one knows. But, a solution is on its way.

I am scheduled to be contacted within the next week by the Sr. Advisor and will reply back when I get info.