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

UPDATE:

Using wireless keyboard and magic mouse, when I go afk for some minutes, then go back, at the first move of my mouse the console show(only one time):

04/11/13 11:06:47,000 kernel[0]: The USB device BRCM20702 Hub (Port 3 of Hub at 0x14000000) may have caused a wake by issuing a remote wakeup (2)

so is this system failure in ur opinion occur because of a harware failure or software issue? I mean we can expect to see those error messages every time we dont touch the keyboard and or trackpad for more than 5 seconds as part of energy saving feature of Mavericks? ????

My replacement Macbook arrived today. Unlike the first one, the trackpad and keyboard both worked fine initially, but both input devices became unresponsive within 20 minutes of using the computer. It happened again about 5 minutes later. Both times closing the lid for a minute resolved the issue. I'm strongly considering returning this machine for a refund until this issue is resolved.

In my opinion, as said a lot of post before...this is software problem

The OS don't work fine in the save-energy tasks, so sometimes trackpad and keyboard go in sleep to try to save energy also when you are using it.

wwiii wrote:

 

My replacement Macbook arrived today. Unlike the first one, the trackpad and keyboard both worked fine initially, but both input devices became unresponsive within 20 minutes of using the computer. It happened again about 5 minutes later. Both times closing the lid for a minute resolved the issue. I'm strongly considering returning this machine for a refund until this issue is resolved.

I still can't believe they are shipping them out, if not purely to reduce growing damage to reputation they should pretend they've sold out and put them on back-order to stop the continuing onslaught of 'new-to-Mac' users from getting a terrible first impression.

Glad I didn't recommend the buying on launch of this late 2013 rMBP 13" to any of my family and friends as their first Mac, I would've felt like a right idiot!

tslight wrote:

 

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....

 

I plugged in a USB last Tuesday.

In the last 6 days, not a single lock up. Prior to that, I had 3 in less than 8 hours.

It works.

Having it happen every 4 or 5 hours doesn't strike me as "rare" in that respect either! And web browsing isn't exactly a specialized circumstance...

Mine froze less then one minute after a cold boot, I opened a terminal and when I tried to type into it - nada - total lock up!

These aren't rare, unusual circumstances, and judging by the length of this thread - this is not rare in any other sense of the word either!

Then again, I suppose without actual data on sales numbers compared to complains, I guess it's impossible to acertain exactly how common it is...

Just to share my thoughts...if it is working fine with a usb plugged in...then it cant be a hardware issue. It should, based on my understanding,  freeze no mater what if it was a hardware issue. I think its all about mavericks energy saving issue.

Indeed it does, mrakers! 

Pop in a USB folks, open a beverage and chill.  I know it's a lot of money and I know they claim to be perfect, thoguh they aren't and never have been.  Yet they do fix their mistakes.  I trust that they are not sitting around doing nothing.  In the end, you'll have a fabulous machine!

Just my 3 cents.

I love it and indeed it is fabulous piece of machine.  I see an update from apple by Wednesday. If not Wednesday then Friday.:)

Truly....remain calm.....ALL IS WELL!

http://www.youtube.com/watch?v=zDAmPIq29ro

Guys, if it was a hardware problem

- windows would crash as well (which was never reported)

- the USB plugging would definitely not solve the problem (how?)

- not every single 13" machine would show up with the same symptoms (at least some devices should work fine)

- some of the 15" models should have the same problem (which are the significant(!) differences in HW?)

- it would not help to close and reopen the lid (after 1 minute)

- it is much more likely that the system would crash pretty early right after booting or first touch of keyboard/trackpad. Anayway, the freezes seem to appear "random" anyway, which indicates that first certain system conditions need to be established "under rare circumstances" to effect the freeze. Bringing a system from one status to another is exactly the SW job.

- the system would not produce kernel messages - it would rather crash due to a faulty hardware

- Apple would NOT use the suggestive term "update" (because there is no "update" for a hardware defect)

- Apple would already know it (of course, they´re not stupid) and stop selling the devices. Otherwise people would simply freak out which nobody wants.

It is a SW issue - very likely a driver problem with that Mavericks build installed on the 13" machines.

Even though I am a brand new Apple user I had done plenty of research and knew I shouldn't be messing with removing a battery. I questioned what she was asking me to do,  and she said it was the macbook airs that you couldn't remove the battery from. !!? Admittedly she did realise her error and gave me another fix ( which didn't work). But I had lost all faith in her by then. Bad first experience with Apple Care.

I recently bought rMBP (late 2013 model) 15", 16/512. In my notebook, the build is 13A3017 and you guys are talking about some other build. Without any third-party software, my notebook didnot hang even a single time since my purchase. I am wondering why there are different builds on 13" and 15" rMBP.

A week ago when this first happened, I talked to an Apple Rep. He told me he would call me tomorrow (11/5) and hopefully have a full solution where I could update my computer and give it a test run.

While I may have misunderstood him, he did say that I will hear from him tomorrow.

I am skeptical that I will be downloading the new software update before others to give it a test on my computer, nonetheless, by tomorrow, Dave from Apple should be calling me. We will see....