MacBook Pro (Retina, 15-inch, Late 2013): Keyboard and Multi-Touch trackpad unresponsive

Resuscitation failed today and got a crash.

Eventually got to a sleep/wake failure...

2/3/14 6:48:08.000 PM kernel[0]: vtd[0] fault: device 0:20:0 reason 0x6 R:0x25b000

2/3/14 7:19:00.000 PM kernel[0]: System was rebooted due to Sleep/Wake failure

Any ideas?

2/3/14 6:48:08.000 PM kernel[0]: ARPT: 80344.840670: scanparams:

2/3/14 6:48:08.000 PM kernel[0]: ARPT: 80344.840673: flags 0

2/3/14 6:48:08.000 PM kernel[0]: ARPT: 80344.840675: active_time 0, passive_time 0

2/3/14 6:48:08.000 PM kernel[0]: ARPT: 80344.840676: scan_start_delay 0

2/3/14 6:48:08.000 PM kernel[0]: ARPT: 80344.840678: scan_cycle_idle_rest_time 0, scan_cycle_idle_rest_time_multiplier 0

2/3/14 6:48:08.000 PM kernel[0]: ARPT: 80344.840681: max_scan_cycles 0, max_rest_time 0

2/3/14 6:48:08.000 PM kernel[0]: ARPT: 80344.840683: Scan Channels (0): None

2/3/14 6:48:08.000 PM kernel[0]: ARPT: 80344.840685: SSID (0): None

2/3/14 6:48:08.000 PM kernel[0]: ARPT: 80344.840687: SSID count = 0

2/3/14 6:48:08.000 PM kernel[0]: ARPT: 80344.840689: wl0: leaveModulePoweredForOffloads: Wi-Fi will turn off.

2/3/14 6:48:08.000 PM kernel[0]: AppleThunderboltHAL::earlyWake - complete - took 0 milliseconds

2/3/14 6:48:08.000 PM kernel[0]: Bluetooth -- LE is supported - Disable LE meta event

2/3/14 6:48:08.000 PM kernel[0]: wlEvent: en0 en0 Link DOWN virtIf = 0

2/3/14 6:48:08.000 PM kernel[0]: AirPort: Link Down on en0. Reason 8 (Disassociated because station leaving).

2/3/14 6:48:08.000 PM kernel[0]: IOThunderboltSwitch<0xffffff803ae5d000>(0x0)::listenerCallback - Thunderbolt HPD packet for route = 0x0 port = 11 unplug = 0

2/3/14 6:48:08.000 PM kernel[0]: **** [IOBluetoothHostControllerUSBTransport][SuspendDevice] -- Suspend -- suspendDeviceCallResult = 0x0000 (kIOReturnSuccess) -- 0x0000 ****

2/3/14 6:48:08.000 PM kernel[0]: vtd[0] fault: device 0:20:0 reason 0x6 R:0x25b000

2/3/14 6:48:08.000 PM kernel[0]: USBF: 80345.464 AppleUSBXHCI::SaveControllerStateForSleep - Controller not saved state after 100ms

2/3/14 6:48:09.000 PM kernel[0]: AppleCamIn::systemWakeCall - messageType = 0xE0000340

2/3/14 6:48:09.000 PM kernel[0]: AppleThunderboltNHIType2::waitForOk2Go2Sx - retries = 6

2/3/14 7:10:52.000 PM kernel[0]: Wake reason: XHC1

2/3/14 7:10:52.000 PM kernel[0]: AppleCamIn::systemWakeCall - messageType = 0xE0000340

2/3/14 7:10:52.000 PM kernel[0]: AppleCamIn::wakeEventHandlerThread

2/3/14 7:10:52.000 PM kernel[0]: Previous Sleep Cause: 5

...

2/3/14 7:15:24.947 PM WindowServer[96]: device_generate_desktop_screenshot: authw 0x7fc26a845090(2000), shield 0x7fc269481070(2001)

2/3/14 7:15:25.018 PM WindowServer[96]: device_generate_lock_screen_screenshot: authw 0x7fc26a845090(2000), shield 0x7fc269481070(2001)

2/3/14 7:15:34.401 PM loginwindow[66]: CoreAnimation: warning, deleted thread with uncommitted CATransaction; set CA_DEBUG_TRANSACTIONS=1 in environment to log backtraces.

2/3/14 7:15:34.404 PM loginwindow[66]: CoreAnimation: warning, deleted thread with uncommitted CATransaction; set CA_DEBUG_TRANSACTIONS=1 in environment to log backtraces.

2/3/14 7:15:34.694 PM loginwindow[66]: CoreAnimation: warning, deleted thread with uncommitted CATransaction; set CA_DEBUG_TRANSACTIONS=1 in environment to log backtraces.

2/3/14 7:15:39.000 PM kernel[0]: com_apple_driver_AppleUSBCardReaderSBC::setPowerState(0xdef9f6d8a88b0079, 0 -> 2) timed out after 101209 ms

2/3/14 7:15:44.690 PM loginwindow[66]: CoreAnimation: warning, deleted thread with uncommitted CATransaction; set CA_DEBUG_TRANSACTIONS=1 in environment to log backtraces.

2/3/14 7:15:52.000 PM kernel[0]: Restarting to collect Sleep wake debug logs

2/3/14 7:15:52.000 PM kernel[0]: AppleCamIn::systemWakeCall - messageType = 0xE0000310

2/3/14 7:15:52.000 PM kernel[0]: [BNBMouseDevice][willShutdown][d8-30-62-37-0e-06]

2/3/14 7:18:57.000 PM bootlog[0]: BOOT_TIME 1391483937 0

So this may be cargo-cult debugging, but vtd is related to virtual instructions.

I wasn't using virtualbox (and old version) but uninstalled it just in case it might do something at startup...

There was one message in the console log:

2/3/14 7:22:50.578 PM SystemStarter[50]: VirtualBox Support and USB Drivers (312) did not complete successfully

I'll post back if the problem happens again...

Traveler42 wrote:

2/3/14 7:15:39.000 PM kernel[0]: com_apple_driver_AppleUSBCardReaderSBC::setPowerState(0xdef9f6d8a88b0079, 0 -> 2) timed out after 101209 ms

What was in your SD card reader? I'm debugging a random hang that seems to be caused by a card in the SD card reader. This hang comes with a log message like the above. Using the disk utility to look at the partitions (you can't make this stuff up) sometimes seems to unstuck this. Ugly bug.

I have a late 2013 macbook pro 13.3 retina, 2.6 i5,8 GB ram.

I'm experiencing same freezing problem using 2 AUDIO 2 DJ Native Instruments Sound Cards connected to a DLINK powered USB HUB. I tried with other USB Hub and got the same results. Its very frustrating for me, Apple please release a fix for these fails.

Thanks

I also want to add that I am experiencing this error on a Late 2013 13" 2.6/500/16.

I reinstalled Osx a few days ago in an attempt to fix this problem by avoiding installing drivers for peripherals like my xbox360 controller and mouse utilities. My friend had just plugged in his Experia Android phone into my laptop's right side usb port to charge and it took out my laptop's KB and Trackpad. The android file transfer tool I use for my MotoX came up ( not sure if it may be a part of the issue.) To remedy the problem I usually have to plug in peripherals and take them out and on the first try my WD Passport Usb3 fixed the problem and after it was recongized and the partitions mounted I got the KB and Trackpad back.

The error I got was the one posted by the OP as well as a few others.

3/20/14 3:34:56.000 PM kernel[0]: AppleUSBMultitouchDriver::_deviceSetReport - DeviceRequest for reportID 0xac returned with result 0xe0004051 - retrying

3/20/14 3:34:57.000 PM kernel[0]: AppleUSBMultitouchDriver::_deviceSetReport - DeviceRequest for reportID 0xac returned with result 0xe000404f - retrying

3/20/14 3:34:57.000 PM kernel[0]: AppleUSBMultitouchDriver::_deviceSetReport - DeviceRequest returned error 0xe000404f (interface 1, reportID 0xac, payload 2

3/20/14 3:34:57.000 PM kernel[0]: AppleUSBMultitouchDebug: _deviceSetReport returned an error in configureDataMode

3/20/14 3:34:57.000 PM kernel[0]: AppleUSBMultitouchDriver::_deviceSetReport - DeviceRequest returned error 0xe000404f (interface 1, reportID 0xac, payload 2

3/20/14 3:34:57.000 PM kernel[0]: AppleUSBMultitouchDebug: _deviceSetReport returned an error in configureDataMode

3/20/14 3:35:53.000 PM kernel[0]: USBF: 14657.126 USB (XHCI):Port 11 on bus 0xa - connect status changed but still enabled. clearing enable bit: portSC(0xe021203)

3/20/14 3:35:54.000 PM kernel[0]: USBMSC Identifier (non-unique): 575833314137335738353935 0x1058 0x748 0x1022, 3

3/20/14 3:36:00.000 PM kernel[0]: AppleUSBMultitouchDriver::message - kIOUSBMessagePortHasBeenReset.

3/20/14 3:36:00.000 PM kernel[0]: AppleUSBMultitouchDriver::checkStatus - received Status Packet, Payload 2: device was reinitialized

3/20/14 3:36: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 (1)

3/20/14 3:36:00.111 PM hidd[670]: MultitouchHID: device bootloaded

3/20/14 3:36:00.000 PM kernel[0]: AppleUSBMultitouchDriver::_deviceGetReport - DeviceRequest for reportID 0xc8 returned with result 0xe000404f - retrying

3/20/14 3:36:00.000 PM kernel[0]: AppleUSBMultitouchDriver::handleReport() - restoring correct operating mode

3/20/14 3:36:00.000 PM kernel[0]: hfs: mounted Passport on device disk1s2

Quite a few of the above errors showed up once or twice in a row, I just posted each time they showed and in order.

FYI, it hasn't happened again (so far).

same problem here, combination with traktor s4.

without usb connection the problem does not happen.

trackpad and keybaord become unresponsive.

any solution yet?

After some more research I have found that the Android File Transfer tool tends to kill the usb stack when peripherals are plugged in. If you have it installed, try the guide here to keep the agent from runnning. It is what causes the problem, and its only purpose is to load the Tool automatically when an Android device is plugged in. Which in my opinion is very annoying when plugging in to charge.

I have the same problem with my late 2013 15" rMBP. I can't understand why 13" EFI was updated to 1.3 and 15" is still at 1.2.

This thing is proving to be much less reliable than my trusty '11 17" MBP.

Crashes while slepping (seems to be fixed in 10.9.2), suddenly loosing all means of input and having to perform a hard reboot without any hope of saving ongoing work... 😠

Sorry, but for all of this I migh as well have got a Windows laptop. 😟

Same crap here with late 2013 15" retina.

I was actually sure that this only happens when i connect my external display, but since i always connect both the external display AND the usb HUB of the display to the left USB port i guess i can't be sure which one of them causing the issue.

I did have android file transfer installed and just now removed it but i am quite sure the problem was happening before i installed it too.

This is seriously ****** up, i bought a MAC to forget about all this b.s problems, instead i got this, the wifi reconnect back from sleep bug..

Annoying as ****..

Give it some time, as long as you properly removed AFT and reinstalled (AFT) properly you should not have the problem again. I was very bummed that I was having this issue, but the same thing would happen on any other computer or OS if a program you used and installed was improperly handling usb.

I was going to say at least it wouldn't straight to bluescreen like Windows, but I feel like it it would be able to tell better what was running or what had just ran to cause the problem. With this I was scratching my head until I resintalled and wrote down each application that accesses usb. Then I found out people had already figured out the issue....

No it doesn't.

I unistalled AFT some days ago hoping it would solve the problem, and here I am, just after a hard reboot because keyboard and touchpad stopped working!!!!

This is a very serious issue, as you can't even save your ongoing work.

One workaround I have done when keyboard and touchpad stop working is to plug in a usb external keyboard. That seems to break the freeze and I can unplug it and the internal keyboard/trackpad continue to work.

This hack is preferable to losing all of your work in flight...

Postcert give us some details about your investigation, please. I've experienced the same problem and AFT disabling helps (I hope 🙂 I test this solution for 10 minutes only)) but it would be extremely helpfull to know more about this trouble.

I haven't had any issues with the freezing after reinstalling AFT with the agent removed. There is always the possibility that another application can cause it as well, but the problem for me was the agent AFT uses to detect when android devices were attached.