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

I can report the same issue on my 13 inch MBP.

I looked at my console out of interest and I have NOT had a freeze recently. This message is popping up continuously:

30/10/2013 6:29:50.000 am 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)

This is the message people are saying they get after a freeze, right?

Well, I havent had a freeze in the last half hour.

Have I missed something? Is it possible I'm about to get a freeze? I have a late 2013 MBPr 13 with the other common specs BTW.

Received Retina MBP 13" today (config 2.6/16/256). Same issue after about 3-4 hours with the same console message (The USB device Apple Internal Keyboard / Trackpad (Port 5 of Hub at 0x14000000) may have caused a wake by issuing a remote wakeup (2))

same here, please submit bug to apple directly so they are aware if this. Thanks

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

This message occurs continuously when a USB device is NOT plugged in, but it doesn't necessarily indicate a crash or occur at the same time.  So far, plugging in a USB device is preventing both this message and crashing for me.  I've now gone about 9 hours continuous use without a crash (before this never managed more than 2-3 hours).

It is a good news that Apple is working on this issue. Hope they can find the solution so that I need not to return my rMBP 13.

May you provide a link or something where I can find the statement apple made? I just read that they suggest solutions that do not help like SMC reset etc. Thanks.

I have the same problem and really annoying to deal with after spending so much money. Mine freezes randomly and frequently. Hope Apple fixes this ASAP

This issue seems to relates to new power saving features in mavericks for Adobe flash content.

Uninstall adobe flash, do not install flash plug-in should solve this issue

Hey ihanbn, where did you get this info from?

I'm asking because it kinda' makes in my case.

My keyboard and trackpad aren't freezing every couple of hours like for many of us here, but each time it did freeze, I was on heavy flash-content websites.

I would hate to speculate here, but it makes a lot of sense in my case.

I'm joining the club here.  First week with the new Macbook Pro, 13" with 8mb ram, Retina display.

Being a new user to the Mac, I thought maybe I had done something incorrectly.  It's obviously a larger problem.  The keyboard did become unresponsive and the trackpad would not accept input.  Cursor still appeared onscreen.  Performed a hard shutdown with the powerbutton and everything appears to be OK.  It has happened twice.

Not a great fix though...I need to use flash content sites for an online course.......

I seem to be lucky? Just received mine today and been working on it non-stop (mainly IntelliJ) and checking some features out. I've also installed the flash plug-in etc but I haven't had the error.

To be honest I was a bit worried about ordering one since I checked the forums several times if this issue was acknowledged by Apple to be a software issue or whetever it was a hardware issue.

I'm still hoping for others (and maybe myself in the future?) that this is indeed a software issue and that Apple fixes this.

All the above I'm talking about has to do with the freeze. I am experiencing the hickups and the lags.

sorry guys, my macbook pro is brand new, no flash installed and it freezes

No, there is no error or problem so far in my "old" machines. I have upgraded macbook5,1 (late 2008) and mackbookpro9,2 (mid 2012) model to Mav OSX. I feel both units faster, more fun to use and have longer battery life. Both of them are running without any problem. I noticed that the battery life is increased by 1-hr to 90 minute longer, that is very impressive. Mid 2012 non retina model (with SSD upgrade) now shows over 9-hr "time remaining" at 100% charge. I am using these machines heavily for last 8-10 days, and have encountered no freeze or sluggish issue as it is  reported for the newest Haswell units.

----

Anyone with an "old" machine having this problem after updating to Mavericks can confirm that thay also have this error?