Late 2013 Keyboard / Trackpad still unresponsive AFTER EFI 1.3 update

Question

Level 1

0 points

Late 2013 Keyboard / Trackpad still unresponsive AFTER EFI 1.3 update

I thought I would start a new thread / discussion since the previous thread here seems to be riddled with "install the update" suggestions and off topic assistance such as battery life questions. I have also logged detailed information regarding this issue on my professional blog here.

Anyway, here is a short, condensed version of my story. I have had two brand new late 2013 Retina MacBook Pro's with the 2.4/16GB/256 configuration. Since the config I chose is a CTO, this problem has been going on since the day the first model arrived (December 10th, 2013). The EFI update was preinstalled on both systems and I can verify that because the boot ROM version is MBP111.0138.B03 (the boot rom prior to the update ended in B00 or B01). I am also an AASP and an ACMT meaning that I am certified and employed with a company that allows me to fix all Apple hardware under warranty. I am well-versed in technology and Apple hardware and I have never seen anything quite like this.

Here is the quick summary of things I have attempted and I have been able to re-recreate the issue:

The system will not mount the root device when I boot via a known good external hard drive running 10.9.1. Verbose mode and Single user mode reports a still waiting for root device error.
The system (rMBP) will not boot from another system (late 2011 MacBook Pro 13") when said system (late 2011 MacBook Pro) pushed into target disk mode via thunderbolt.
My system, rMBP, will boot up with the internal SSD but will not allow the keyboard and track pad to function. The caps lock key will not illuminate. The keyboard and track pad will work OUTSIDE of 10.9.1, however. I have installed a clean internet recovery version of Mavericks over 4 times.
If I put my system, rMBP, into target disk mode and connect to any other computer via thunderbolt and boot it on the other Apple systems, the operating system running on the internal SSD of the rMBP will work just fine -- keyboard and mouse included (again, as a target disk mode thunderbolt connection to another host).
If I use a remote agent to connect to my rMBP such as LogMeIn or vnc, the keyboard and mouse will work just fine from the remote system which leaves me to beleive that this is not a software issue nor is it fully a hardware issue since the keyboard and mouse work outside of mavericks.

I believe we are still dealing with a firmware issue here. It took several tries to create a bootable device for the late 2013 rMBP since NONE of my other up-to-date and verified working external drives will boot but I finally created a bootable USB stick. When I run the system from the USB stick, the keyboard and trackpad will work but if I touch the keyboard and / or trackpad in 5 second intervals, I will receive the following error:

1/4/14 4:44:41.000 PM	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)
1/4/14 4:45:00.000 PM	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)
1/4/14 4:45:43.000 PM	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)
1/4/14 4:49:03.000 PM	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)
1/4/14 4:50:20.000 PM	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)
1/4/14 4:51:24.000 PM	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)
1/4/14 4:52:49.000 PM	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)
1/4/14 4:53:00.000 PM	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)
1/4/14 4:53:10.000 PM	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)
1/4/14 4:55:25.000 PM	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)
1/4/14 4:56:07.000 PM	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)
1/4/14 4:57:06.000 PM	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)
1/4/14 4:58:40.000 PM	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)
1/4/14 4:59:45.000 PM	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)

I had actually created a system log query to search for the above. The search string includes "the USB " and any entry after 1/1/2014. The above error should only present itself when waking an Apple system from sleep and instead it happens on every touch after, at least, a 5 second period of non-use.

When I remote into the system using LogMeIn, VNC or even use an application called ShareMouse which shares the keyboard and mouse of my Windows system with any other computer on the network presuming they have ShareMouse also installed, I can use the system as I would expect, without continuous error in the console log. When I check the system information, Bluetooth is completely disabled and the USB hub does not report address information. Since the keyboard, track pad, Bluetooth peripheral and USB ports all sit on the same USB stack / hub this leads me to think there is a firmware / driver failure occurring after Mavericks loads. The only two errors I see when I am using a remote keyboard and mouse via a remote service is as follows:

1/5/14 6:58:16.000 PM kernel[0]: The USB device HubDevice (Port 1 of Hub at 0xfa000000) may have caused a wake by issuing a remote wakeup (2)

1/5/14 6:58:16.000 PM kernel[0]: The USB device Apple Internal Keyboard / Track pad (Port 2 of Hub at 0xfa100000) may have caused a wake by issuing a remote wakeup (3)

Bottom line: Even for those of you who have installed the EFI 1.3 update and have verified that your freezing issues have ceased, for the most part, could you check your console log for the above error. My guess is, you will still see the error repeated there in 5 second intervals if you touch the keyboard, put your hands up for 5 seconds, touch the keyboard and / or track pad again. My concerns is that this is a product line issue since it has occurred on two brand new systems and the log errors appeared on another model on display in an Apple store. (The display model was logged into an Admin account so I took the liberty of checking the console log.)

MacBook Pro (Retina, 13-inch, Late 2013), OS X Mavericks (10.9.1)

Posted on Jan 6, 2014 10:54 AM

Reply

Answer 1

Jan 14, 2014 10:02 PM in response to jldeen

I'm tired of this message. Bought a Mac 13" retina from bestbuy that was shipped to me on December 24th. The finder took a long time to load 'All My Files' with three to five second delay. My older macbook unibody (late 2009)was instantaneous. My wife's macbook aluminum (2011) also loaded the files instantaneously. Sorry I digressed but while I was trying to research that issue, I was caught up in the console and multiple of these,'The USB device Apple Internal Keyboard / Trackpad (Port 5 of Hub at 0x14000000) may have caused a wake by issuing a remote wakeup (2)' kept showing up whenever I touched the trackpad in intervals of 6-7 seconds.

Called up apple, used screen sharing and after spending an hour was transferred to the second tier tech. The second tier rep troubleshooted and told me it WAS an issue and asked me to go to apple store to run diagnostics and that most likely I'll receive another notebook in exchange since it fell within 14 day period. I told him the internet was filled with this discussion and asked if it was prevalent. He said it was the first time he has come across this issue and most forums on the internet may not be addressing my specific issue. I wasn't convinced and simply returned it at best buy.

The unfortunate thing is I sold my macbook unibody and having owned 2 macbooks for last eight years I caved and ordered another 13". After a week and a half I received it today and guess what, I see the same message filling up my console.

I noted the following,

* Use guest account and you'll never see the 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)'. All admin accounts created will throw that error.

Though off topic I'd like to state what happened with the Finder's 'All my files' issue:

1. Once I upgraded my older macbook unibody to mavericks, the 'All my files' took longer to load as the new macbook pro.

2. I was able to replicate the same slow load times with macbook aluminium(2011) when I upgraded it to mavericks.

Oh, I also showed the slowness to the representatives and all they tried doing was reindex spotlight which did no good.

So much for 1799$ notebook and the "free" OS. Very disappointed.

Reply

Answer 2

Jan 15, 2014 10:18 PM in response to jldeen

Ok, this is an excerpt from my chat conversation today:

…

(Me):

I'm haunted with the following message on my console on the two 13" retina MacBooks I purchased since Dec 24th. 'The USB device Apple Internal Keyboard / Trackpad (Port 5 of Hub at 0x14000000) may have caused a wake by issuing a remote wakeup (2)'

…

(Me):

Would you like to see the screenshot?

(Rep):

Yes please!

…

(Rep):

Let me do some research on this message in console. Since the two internal devices aren’t having any issues there has to be a software/firmware issue causing this message to appear

…

(Rep):

It does in fact look like this is a normal feature on your computer. It plays a part in our new OS, OS X Mavericks. There is a new feature called App Nap. App Nap allows supported apps to consume very little energy when they are open but not being used. For example, App Nap might be used if an app is open on a desktop that you are not currently viewing, or if an app is hidden under other windows.

(Rep):

Every time you use a application, while using your trackpad/keyboard, you are awakening the application which causes the Console to show the message that the trackpad was used to awaken the app

(Rep):

There isn’t anything to worry about! The message isn’t a error, just a notification

So I guess it may not a problem after all! Its still weird that the trackpad would throw so many logs on the console though.

I must also note that I have never actually faced a freeze/unresponsive behavior on the hardware. The spinning wheel does show up sometimes for a second or two but that's about it.

Reply

Answer 3

Feb 21, 2014 4:33 PM in response to jldeen

I'm stilling battling this isse as well.

Console is full of the same errors:

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

Tried a fresh install, it came back.

Got a new logic board from Apple, it came back.

For me the hang usually happens when I do something with Chrome.

I may try live without Chrome for a while to see if it goes away but I may just try return it and get a 15" since not running a certain program seems to be a pretty lame restriction for a $2,600 notebook.

Reply

Answer 4

leonby

Level 1

0 points

Mar 17, 2014 5:32 AM in response to jldeen

I thought it's just the trackpad etc. are informing the system that you are active so the machine will not fall into sleep. I had the same issue and I noticed that the log entries matching your touching the trackpad during the period you are webbrowsing (if only waching a video without any touching the pad or keyboard, the machine will sleep after a certain time, even you were watching, or the maching was active before it falls to sleep).

Reply

Answer 5

Mar 20, 2014 10:42 AM in response to crdeutsch

Was hopefull the last OSX update solved the issue and actually went a whole week without a freeze, but got one today.

Always seems to be triggered by selecting a different tab in Chrome.

I don't know what Google is doing to contribute to the issue, but I wish they'd fix it.

I also, successfully went one week with no freezes when I uninstalled Chrome.

Reply

Answer 6

Mar 24, 2014 6:13 PM in response to jldeen

I'm having this same issue. Random freezes every now and then on an Late 2013 13 inch Retina. I have the 1.3 EFI update and the same console messages. I have Chrome installed but never use it, I do however seem to get the lock ups a lot using FireFox!

I've kind of been putting up with it but I'm considering taking it back in to the store if it doesn't stop. The only issue is, it only happens maybe once a day or every two days, so the chance of it happening when I'm in store isn't very remote.

Reply

Answer 7

new2M@c

Level 1

6 points

Apr 5, 2014 6:05 AM in response to jldeen

this is my second macbook pro mavericks late 2013 w retina too and i get the SAME MESSAGE every 2 second intervals on console. and my mousepad freezes andi get spinning wheel. SECOND MACBOOK PRO W RETINA IN TWO MONTHS FROM TWO DIFFERENT STORES, APPLE THEN BEST BUY . BOTH SUCK, UPDATED EVERYTHING, still message and freezing continue, soooo has anyone figured out what is the problem??

Reply

Answer 8

TadWi

Level 1

36 points

Apr 11, 2014 11:43 PM in response to jldeen

Run into this thread because I also noticed these messages and wanted to find out what these are.

I have the late MacBook Pro retina 13". Picked it up on March 13. It's the 2.6GHz/8G/256G model with EFI 1.3.

I do notice the same message in the console, however, it does not repeat itself every 5 or so seconds. It only repeats after a few second (around 5 I believe) *IF* I touch the touchpad. If I don't touch anything, I don't get the message.

Also, it's been almost a month, using it on a daily basis with a minimum of 4 or so hours a day, so far I have not exeprienced any freezes, beach balls, etc.

I never had Chrome installed. Only use Safari.

Reply

Answer 9

May 26, 2014 7:55 PM in response to jldeen

After 1 month i started recieving that message and now my computer freezes randomly specially when whatching a video on a browser, first I thought it was firefox but it has happend using Safari too. Im so disapointed, I switched to Apple thinking they had a very high quality standard and now I get this.

Reply

Answer 10

Jul 6, 2014 4:05 AM in response to jldeen

I'm getting the same message and i'm not happy to learn there's a chance it's related to freezes. For now I only had a freeze since i bought the rMBP late 2013 and thought it was related to not rebooting it EVER.

Reply

Answer 11

adune

Level 1

0 points

Aug 25, 2014 7:29 PM in response to jldeen

This problem still exists on 2014 13" rMBPs. I could reproduce the problem on ALL of the display 13" rMBPs at my local retailer. I also have personally been through two brand new rMBPs, same issue. The problem could not be reproduced on the 15" models or the MBAs.

I will be returning the computer as Apple has made it apparent this is not a priority for them.

Reply

Answer 12

Dec 21, 2014 10:18 PM in response to rhythmic01

I'm having a hard time switching from a Samsung slider phone (Verizon Wireless) to an iPhone 6 plus. Any advice?

Reply

Answer 13

Dec 22, 2014 1:20 AM in response to crdeutsch

I was having similar problems with the interface between RoundCube at my office and my webmail at home. I think I solved it with help from Construct in Great Barrington.

Reply