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

No more console message.. fixed!

 

apple has released a new EFI update that claim to resolve this issue, after the update... what happen? the eror message still keep coming up in the log!!!! OMG!

 

What error message are you talking about? There is no error message. There is a kernel log message stating that a device issued a remote wakeup. Where is the error?

Paapaa wrote:

 

 

apple has released a new EFI update that claim to resolve this issue, after the update... what happen? the eror message still keep coming up in the log!!!! OMG!

 

 

What error message are you talking about? There is no error message. There is a kernel log message stating that a device issued a remote wakeup. Where is the error?

Correct, completely agree !!

LOL story of my life

I just returned my first unit mainly because the employees at Best Buy told me it would reset the 14 day grace period and I figured it would buy me a couple weeks. So, the update comes out it looks like while I was at the store .

Oh well will update the new unit now! If Apple had given us any kind of timeframe they would have had one less return.

It's not an error message, if you actually bother to read it

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

That's not an error. It's a log message telling you the trackpad has gone to sleep and has been woken up (i.e touched by someone)

Ok guys, it's time to start enjoying our beautiful machines instead of fretting about what might be wrong with them and complaining about "hardware problems" that don't exist. :)

Bobs22 that is actually the error everyone was mentioning. Just copy paste it into google and all threads related to a rMBP late 2013 will show up. For a brief moment I thought it stopped but even after installing it the messages still keep appearing in my console so I'm not feeling to relieved to be honest.

I have a mid 2012 MacBook Air 13 inch, and I have the same keyboard and touchpad freezing issue in mavericks (everything was fine in mountain lion). I took it to the apple store, reinstalled mavericks (not wipe and reinstall, just reinstall). Now my laptop seems to be fine, but when I connect it to a monitor through the thunderbolt port, the keyboard and trackpad still freeze very frequently. Maybe it's just an issue with my particular laptop's thunderbolt port?

Bluesklus,

My 2012 13" MBA has no issues after an appstore update to mavericks.  Mine is the base model.

I also use a thunderbolt>monitor with wireless trackpad and keyboard.

Update installed.  It's been a pleasure guys, but I hope I don't have to return to you on here again

I still have the exact same message in the console log after the update, what should i do?

mateo69er we all have them. I reckon now it's more of a notification. As soon as you stop touching your trackpad it goes into sleep mode. By touching it again it wakes up and notifies it in the console.

Glenndisimo wrote:

 

Bobs22 that is actually the error everyone was mentioning. Just copy paste it into google and all threads related to a rMBP late 2013 will show up. For a brief moment I thought it stopped but even after installing it the messages still keep appearing in my console so I'm not feeling to relieved to be honest.

No. The actual error might be related (and most likely is related) to that event shown in the log BUT that is not en error message. The error happens at the same time. Do you understand the difference? Having a device wake up the computer is a normal thing that can and has to happen. The freezing part is the bug. Kernel log doesn mention it

in the description of EFI update, it only mentioned 13 inch, which means, no other model is affecting by the error, what about the people who reported their 15 inch or Air has the same problem?

Ok, if its EFI problem and only affecting the 13 inch (as apple only mentioned 13 inch in its note), which means the 13 inch may use a different chipset? I want to know why this was happening, did apple really fix it or they just use a EFI update to hide the problem, like not putting the keyboard into deeper sleeping mode? is this going to affect the battery?

with such many discussion here and so many people being affceted, I do think Apple should make a offical expliantion about why it happens and how did they fixed it, make sure there is no hardware fault being hide by a firmware update.

plus why the Keyboard/Trackpad log message is happening so often? why there is no apple representive reply to this thread for a decent explaination to clear out our worry?

You people need to stop being so fixated on the idea that seeing the log messages means that the issue existss. The messages in the logs doesn't mean that there's an error. It's just a list of events.