Keyboard & Trackpad freeze (MBA 13" 2011)

Discussion in 'MacBook Air' started by HunPro, May 28, 2014.

  1. HunPro macrumors member

    Joined:
    Oct 28, 2013
    Location:
    Budapest, Hungary
    #1
    I'm experiencing a similar problem that others do (MBA 13", 2011). However none of the possible fixes got me closer, so I tried to narrow down where the real reason for this could be.

    When I bought it (August 2011), it did a 100 day uptime, straight out of the box.

    Then, out of a sudden, a trackpad & keyboard freeze while watching flash video.

    It was hard to reproduce, but I was sure that it happens after the Macbook was put to sleep, and then woken up, and having flash content in a browser. So I figured that it's a software problem.

    It went away sometime mid-2012, and so I wasn't bothered about it.

    I updated to Mavericks when it came out.

    A bit later, maybe after a software update, it started happening again.

    And recently it's getting pretty severe: the keyboard and the trackpad freezes. Power button works. External mouse usually works. The keyboard and the mouse doesn't show up in the USB devices tab, System Preferences says "No trackpad", the Bluetooth icon sometimes shows it's broken. (usually when the external mouse fails as well)

    Restart sometimes solves it, sometimes it goes into a boot loop (keeps playing the "ding" with a white screen), sometimes it gets to the login screen with the keyboard and trackpad still frozen. SMC & PRAM reset solves it temporarily, that is, I can log in eventually, if I don't just restart, but go through the reset procedures.

    Things I tried and didn't help:

    • delete 3rd party kernel extensions related to USB
    • deleting all the login stuff that was mentioned in related threads
    • turning off bluetooth
    • turning off keyboard backlight
    • SMC reset
    • PRAM reset
    • delete caches with OnyX
    • fresh start (never putting it to sleep)
    • fresh start and battery only (to cross off power supply fault)
    • turning off active sleep
    • no flash content
    • only using Firefox OR Safari OR Chrome
    • all of these at the same time

    Things that should cause it, but never do:

    • heavy CPU load seemingly has no effect by itself
    • heavy GPU load seemingly has no effect by itself

    Things that make it happen sooner (anecdotal, have no hard data on it):

    • flash video after wake up
    • utorrent client downloading at 3+ MB/s
    • external monitor plugged in
    • all these combined

    I could post error logs, but it's always different and USB related: checksum error, fatal error, USB stuff. All the error messages I encountered have been encountered by others, that's how I found the possible (but ineffective) fixes.

    It is really annoying, and I'm not looking to waste money on an off-warranty logic board replacement, as I'm not sure that would solve it (it didn't work for others). Can it be a ribbon cable? Can it be a software problem?

    It is really annoying, and seeing all the attention 13" Retina MacBook Pro users got after experiencing similar issues (and also an SMC update), I'm hoping that there's a verifiable problem here that can be fixed in a less drastic way.
     
  2. HunPro thread starter macrumors member

    Joined:
    Oct 28, 2013
    Location:
    Budapest, Hungary
    #2
    More detailed console report

    I'm getting these on startup

    2014.05.28. 18:25:19,000 kernel[0]: SMC::smcReadKeyAction ERROR: smcReadData8 failed for key B0OS (kSMCKeyNotFound)
    2014.05.28. 18:25:19,000 kernel[0]: SMC::smcReadKeyAction ERROR: smcReadData8 failed for key BC3V (kSMCKeyNotFound)
    2014.05.28. 18:37:21,000 kernel[0]: SMC::smcReadKeyAction ERROR: smcReadData8 failed for key LsNM (kSMCKeyNotFound)


    However, this could just be a monitoring tool.

    This is the serious stuff:
    2014.05.28. 18:20:54,000 kernel[0]: USBF: 19. 62 AppleUSBHubPort::FatalError - Port 1 of Hub at 0xfa100000 reported error 0xe00002c0 while doing setting port power
    2014.05.28. 18:20:54,000 kernel[0]: USBF: 19. 62 AppleUSBHubPort::FatalError - Port 2 of Hub at 0xfa100000 reported error 0xe00002c0 while doing setting port power
    2014.05.28. 18:20:54,000 kernel[0]: USBF: 19. 62 AppleUSBHubPort::FatalError - Port 3 of Hub at 0xfa100000 reported error 0xe00002c0 while doing setting port power


    Now I'm typing this on the Macbook, and it works fine. But I had to do many resets, I got the boot loop, I got the frozen cursor at the login screen.

    Also, creating another account (administrator) didn't help.

    If that's not enough, now that it's running, somethings off with the battery charge: it's at 99%, yet it says that it will take a further 12 minutes to be full.
     
  3. HunPro thread starter macrumors member

    Joined:
    Oct 28, 2013
    Location:
    Budapest, Hungary
    #3
    Yesterday night

    Yesterday night it went without a hitch. I did a shutdown instead of putting it to sleep.

    This morning, it turned on just fined, used it for an hour, and put it into sleep again. Without any problem.

    This bug is weird. It doesn't look like failing hardware.
     
  4. HunPro thread starter macrumors member

    Joined:
    Oct 28, 2013
    Location:
    Budapest, Hungary
    #4
    I uninstalled flash, maybe that will make a difference.
     
  5. HunPro thread starter macrumors member

    Joined:
    Oct 28, 2013
    Location:
    Budapest, Hungary
    #5
    It happened again: after waking up from sleep, unlugged, while playing flash video (Youtube).

    This happens in the system console:

    2014.05.30. 16:45:04,000 kernel[0]: AppleUSBMultitouchDriver::validateChecksum - 22-byte packet checksum is incorrect (expected 0x62d, checksum bytes were 0xfde)
    2014.05.30. 16:45:04,000 kernel[0]: AppleUSBMultitouchDriver::validateChecksum - 22-byte packet checksum is incorrect (expected 0x21f, checksum bytes were 0xd63)
    2014.05.30. 16:45:05,000 kernel[0]: AppleUSBMultitouchDriver::message - kIOUSBMessagePortHasBeenReset.
    2014.05.30. 16:45:05,000 kernel[0]: AppleUSBMultitouchDriver::message - kIOUSBMessagePortHasBeenReset.
    2014.05.30. 16:45:05,000 kernel[0]: AppleUSBMultitouchDriver::message - kIOUSBMessagePortHasBeenReset.
    2014.05.30. 16:45:05,000 kernel[0]: AppleUSBMultitouchDriver::_deviceGetReport - DeviceRequest for reportID 0x0 returned with result 0xe0004061 - retrying
    2014.05.30. 16:45:05,000 kernel[0]: AppleUSBMultitouchDriver::_deviceGetReport - DeviceRequest for reportID 0x0 returned with result 0xe0004061 - retrying
    2014.05.30. 16:45:05,000 kernel[0]: AppleUSBMultitouchDriver::_deviceGetReport - DeviceRequest for reportID 0x0 returned with result 0xe0004061 - retrying
    2014.05.30. 16:45:05,000 kernel[0]: AppleUSBMultitouchDriver::_deviceGetReport - DeviceRequest returned error 0xe0004061 (interface 0, reportID 0x0)
    2014.05.30. 16:45:05,000 kernel[0]: AppleUSBMultitouchDebug: _deviceGetReport returned an error in configureDataMode
    2014.05.30. 16:45:06,000 kernel[0]: AppleUSBMultitouchDriver::_deviceGetReport - DeviceRequest for reportID 0x0 returned with result 0xe0004061 - retrying
    2014.05.30. 16:45:06,000 kernel[0]: AppleUSBMultitouchDriver::_deviceGetReport - DeviceRequest for reportID 0x0 returned with result 0xe0004061 - retrying
    2014.05.30. 16:45:06,000 kernel[0]: AppleUSBMultitouchDriver::_deviceGetReport - DeviceRequest for reportID 0x0 returned with result 0xe0004061 - retrying
    2014.05.30. 16:45:06,000 kernel[0]: AppleUSBMultitouchDriver::_deviceGetReport - DeviceRequest returned error 0xe0004061 (interface 0, reportID 0x0)
    2014.05.30. 16:45:06,000 kernel[0]: AppleUSBMultitouchDebug: _deviceGetReport returned an error in configureDataMode
    2014.05.30. 16:45:06,000 kernel[0]: AppleUSBMultitouchDriver::_deviceGetReport - DeviceRequest for reportID 0x0 returned with result 0xe0004061 - retrying
    2014.05.30. 16:45:06,000 kernel[0]: AppleUSBMultitouchDriver::_deviceGetReport - DeviceRequest for reportID 0x0 returned with result 0xe0004061 - retrying
    2014.05.30. 16:45:06,000 kernel[0]: AppleUSBMultitouchDriver::_deviceGetReport - DeviceRequest for reportID 0x0 returned with result 0xe0004061 - retrying
    2014.05.30. 16:45:06,000 kernel[0]: AppleUSBMultitouchDriver::_deviceGetReport - DeviceRequest returned error 0xe0004061 (interface 0, reportID 0x0)
    2014.05.30. 16:45:06,000 kernel[0]: AppleUSBMultitouchDebug: _deviceGetReport returned an error in configureDataMode
    2014.05.30. 16:45:06,000 kernel[0]: AppleUSBMultitouchDriver::message - kIOUSBMessagePortHasBeenReset.
    2014.05.30. 16:45:07,000 kernel[0]: AppleUSBMultitouchDriver::message - kIOUSBMessagePortHasBeenReset.
    2014.05.30. 16:45:07,000 kernel[0]: AppleUSBMultitouchDriver::checkStatus - received Status Packet, Payload 2: device was reinitialized
    2014.05.30. 16:45:07,316 hidd[69]: MultitouchHID: device bootloaded


    This goes on for a while, then:

    2014.05.30. 16:45:12,000 kernel[0]: USBF: 14632.511 The IOUSBFamily is having trouble enumerating a USB device that has been plugged in. It will keep retrying. (Port 2 of Hub at 0xfa100000)
    2014.05.30. 16:45:12,000 kernel[0]: USBF: 14633. 38 AppleUSBHubPort::FatalError - Port 2 of Hub at 0xfa100000 reported error 0xe00002ed while doing get status (first in port status change)
    2014.05.30. 16:45:12,000 kernel[0]: USBF: 14633. 38 The IOUSBFamily was not able to enumerate a device.
    2014.05.30. 16:45:12,000 kernel[0]: USBF: 14633.166 AppleUSBHubPort::FatalError - Port 2 of Hub at 0xfa100000 reported error 0xe00002ed while doing get status (second in port status change)
    2014.05.30. 16:45:13,000 kernel[0]: **** [BroadcomBluetoothHostControllerUSBTransport][LMPLoggingBulkOutWriteCompleteHandler] -- Received 0xe00002eb (kIOReturnAborted); inBufferSizeRemaining = 0x00000002; isInactive = FALSE, suspended = TRUE -- 0xb400
    2014.05.30. 16:45:14,000 kernel[0]: USBF: 14634.328 AppleUSBHubPort::FatalError - Port 1 of Hub at 0xfa100000 reported error 0xe00002c0 while doing getting port status (2)


    And it's gone.

    The mouse pointer froze for a second, then it came back for a fraction of a second, then it was gone, along with the keyboard and the bluetooth (which was already turned off).
     
  6. HunPro thread starter macrumors member

    Joined:
    Oct 28, 2013
    Location:
    Budapest, Hungary
    #6
    Preventing it

    I managed to prevent it while it was about to happen.

    I was using Google street view (it usually happens during street view), and as the cursor began to freeze, I started using the physical click on the touchpad, and it snapped out of it.

    However, clicking didn't work from then on (either physical or tap), until I put it into sleep and brought it back.

    Now it's working again.

    It cannot be just a hardware error.

    (I was using street view in Chrome, I uninstalled Flash a few days ago).
     
  7. HunPro thread starter macrumors member

    Joined:
    Oct 28, 2013
    Location:
    Budapest, Hungary
    #7
    Anyone familiar with this?

    2014.06.05. 10:58:15,000 kernel[0]: AppleUSBMultitouchDriver::message - kIOUSBMessagePortHasBeenReset.
    2014.06.05. 10:58:16,000 kernel[0]: AppleUSBMultitouchDriver::message - kIOUSBMessagePortHasBeenReset.
    2014.06.05. 10:58:16,000 kernel[0]: AppleUSBMultitouchDriver::checkStatus - received Status Packet, Payload 2: device was reinitialized
    2014.06.05. 10:58:16,000 kernel[0]: AppleUSBMultitouchDriver::_deviceSetReport - DeviceRequest for reportID 0x0 returned with result 0xe000404b - retrying
    2014.06.05. 10:58:16,000 kernel[0]: AppleUSBMultitouchDriver::_deviceSetReport - DeviceRequest for reportID 0x0 returned with result 0xe000404b - retrying
    2014.06.05. 10:58:16,000 kernel[0]: AppleUSBMultitouchDriver::_deviceSetReport - DeviceRequest for reportID 0x0 returned with result 0xe000404b - retrying
    2014.06.05. 10:58:16,000 kernel[0]: AppleUSBMultitouchDriver::_deviceSetReport - DeviceRequest for reportID 0x0 returned with result 0xe000404f - retrying
    2014.06.05. 10:58:16,510 hidd[68]: MultitouchHID: device bootloaded
    2014.06.05. 10:58:16,000 kernel[0]: AppleUSBMultitouchDriver::_deviceGetReport - DeviceRequest for reportID 0xc8 returned with result 0xe000404b - retrying
    2014.06.05. 10:58:16,000 kernel[0]: AppleUSBMultitouchDriver::_deviceGetReport - DeviceRequest for reportID 0xc8 returned with result 0xe000404b - retrying
    2014.06.05. 10:58:16,000 kernel[0]: AppleUSBMultitouchDriver::_deviceSetReport - DeviceRequest for reportID 0xc8 returned with result 0xe000404b - retrying
    2014.06.05. 10:58:16,000 kernel[0]: AppleUSBMultitouchDriver::_deviceSetReport - DeviceRequest for reportID 0xc8 returned with result 0xe000404b - retrying
    2014.06.05. 10:58:16,000 kernel[0]: AppleUSBMultitouchDriver::_deviceSetReport - DeviceRequest for reportID 0xc8 returned with result 0xe000404b - retrying
    2014.06.05. 10:58:16,000 kernel[0]: AppleUSBMultitouchDriver::_deviceSetReport - DeviceRequest for reportID 0xc8 returned with result 0xe000404b - retrying
    2014.06.05. 10:58:16,000 kernel[0]: AppleUSBMultitouchDriver::_deviceSetReport - DeviceRequest returned error 0xe000404b (interface 1, reportID 0xc8, payload 9
    2014.06.05. 10:58:16,000 kernel[0]: AppleUSBMultitouchDriver::_deviceSetReport - DeviceRequest for reportID 0xac returned with result 0xe000404b - retrying
    2014.06.05. 10:58:16,000 kernel[0]: AppleUSBMultitouchDriver::_deviceSetReport - DeviceRequest for reportID 0xac returned with result 0xe000404b - retrying
    2014.06.05. 10:58:16,000 kernel[0]: AppleUSBMultitouchDriver::_deviceGetReport - DeviceRequest for reportID 0x0 returned with result 0xe000404b - retrying
    2014.06.05. 10:58:16,000 kernel[0]: AppleUSBMultitouchDriver::_deviceSetReport - DeviceRequest for reportID 0xac returned with result 0xe00002eb - retrying
    2014.06.05. 10:58:16,000 kernel[0]: AppleUSBMultitouchDriver::_deviceSetReport - DeviceRequest returned error 0xe000404f (interface 1, reportID 0xac, payload 2
    2014.06.05. 10:58:16,000 kernel[0]: AppleUSBMultitouchDebug: _deviceSetReport returned an error in configureDataMode
    2014.06.05. 10:58:16,000 kernel[0]: AppleUSBMultitouchDriver::_deviceSetReport - DeviceRequest for reportID 0xac returned with result 0xe000404f - retrying
    2014.06.05. 10:58:16,000 kernel[0]: AppleUSBMultitouchDriver::_deviceSetReport - DeviceRequest for reportID 0xac returned with result 0xe000404b - retrying
    2014.06.05. 10:58:16,000 kernel[0]: AppleUSBMultitouchDriver::_deviceSetReport - DeviceRequest for reportID 0xac returned with result 0xe000404f - retrying
    2014.06.05. 10:58:16,000 kernel[0]: AppleUSBMultitouchDriver::_deviceSetReport - DeviceRequest returned error 0xe000404b (interface 1, reportID 0xac, payload 2
    2014.06.05. 10:58:16,000 kernel[0]: AppleUSBMultitouchDebug: _deviceSetReport returned an error in configureDataMode
    2014.06.05. 10:58:17,000 kernel[0]: **** [BroadcomBluetoothHostControllerUSBTransport][LMPLoggingBulkOutWriteCompleteHandler] -- Received 0xe00002eb (kIOReturnAborted); inBufferSizeRemaining = 0x00000002; isInactive = FALSE, suspended = TRUE -- 0x7400
    2014.06.05. 10:58:21,000 kernel[0]: BootCache: too many history clusters (150, limit 151)
    2014.06.05. 10:58:32,000 kernel[0]: HubDevice::terminate(kIOServiceSynchronous) timeout
    2014.06.05. 10:58:33,000 kernel[0]: USBF: 104.553 The IOUSBFamily is having trouble enumerating a USB device that has been plugged in. It will keep retrying. (Port 1 of Hub at 0xfa000000)
    2014.06.05. 10:59:46,000 kernel[0]: considerRebuildOfPrelinkedKernel com.apple.driver.AppleUSBCDC triggered rebuild
     
  8. SmOgER macrumors 6502a

    Joined:
    Jun 2, 2014
    #8
    Sorry but I'am not familiar with this and haven't experienced this.
    I havent read all your posts here, but I assume you've tried smc and pram reset as well as OS X clean reinstall? Cause if these things weren't done, the process of fixing such issue is usually similiar to searching for a needle in a haycock. Extremely time consuming and frustrating. So in the end of the day, it's easier to cleanly reinstall the OS.
     
  9. HunPro thread starter macrumors member

    Joined:
    Oct 28, 2013
    Location:
    Budapest, Hungary
    #9
    I'll try to give it a go, but I have to make manual backups, and I have to be sure that I've backed up everything, before I give it a go.

    Although I could create a Time Machine backup, just in case.
     
  10. Scorpion008 macrumors member

    Joined:
    Sep 28, 2013
  11. HunPro thread starter macrumors member

    Joined:
    Oct 28, 2013
    Location:
    Budapest, Hungary
    #11
    Well, it's been almost a year and NO.

    I've installed Yosemite beta, from scratch, just to see what happens, and was really excited for a day.

    Then the same error happened.

    I had it taken apart, cleaned, I disconnected the keyboard/trackpad assembly, reconnected it, it didn't matter.

    So I gave up, reinstalled my Mavericks Time Machine backup, bought an Apple keyboard, and a monitor, and since then I've been using it this was.

    One USB port stays active, so the keyboard acts as a USB hub.

    It's effectively an SSD-equipped Mac Mini with a UPS.
     
  12. HunPro thread starter macrumors member

    Joined:
    Oct 28, 2013
    Location:
    Budapest, Hungary
    #12
    Some new console messages

    During the wakeup:

    Code:
    AppleUSBMultitouchDriver::handleReport - not in path binary mode
    Code:
    2015.02.20. 11:04:01,000 kernel[0]: Apple Internal Keyboard / Trackpad::terminate(kIOServiceSynchronous) timeout
    2015.02.20. 11:04:02,000 kernel[0]: AppleUSBMultitouchDriver::checkStatus - received Status Packet, Payload 2: device was reinitialized
    2015.02.20. 11:04:02,000 kernel[0]: AppleUSBMultitouchDriver::handleReport - not in path binary mode, received 0x74 data packet of length 142
    2015.02.20. 11:04:07,000 kernel[0]: full wake (reason 1) 297294 ms
    2015.02.20. 11:04:07,000 kernel[0]: IOPMrootDomain: idle cancel, state 2
    
    Interestingly, the "not in path binary mode" message can be found in a german forum, where they go through similar steps: removing MagicPrefs, removing plist files, repairing permissions, removing USB Overdrive. To no avail.

    This is during a wakeup from sleep:

    Code:
    2015.02.20. 10:30:35,000 kernel[0]: AirPort_Brcm43xx::powerChange: System Sleep 
    2015.02.20. 10:30:37,000 kernel[0]: AppleThunderboltHAL::earlyWake - complete - took 0 milliseconds
    2015.02.20. 10:30:37,000 kernel[0]: Thunderbolt Self-Reset Count = 0xedefbe00
    2015.02.20. 10:31:03,000 kernel[0]: SMC::smcHandleInterruptEvent WARNING status=0x0 (0x40 not set) notif=0x0
    2015.02.20. 10:31:03,000 kernel[0]: Wake reason: EC.LidOpen (User)
    2015.02.20. 10:31:03,000 kernel[0]: AirPort_Brcm43xx::powerChange: System Wake - Full Wake/ Dark Wake / Maintenance wake
    2015.02.20. 10:31:03,000 kernel[0]: Previous Sleep Cause: 5
    2015.02.20. 10:31:03,000 kernel[0]: AppleThunderboltHAL::earlyWake - complete - took 1 milliseconds
    2015.02.20. 10:31:03,000 kernel[0]: AppleUSBMultitouchDriver::validateChecksum - 64-byte packet checksum is incorrect (expected 0xbf2, checksum bytes were 0xdfc)
    
    Already, as you can see from the quoted line, something's not right.

    The maddening thing about this problem is the infrequent nature of it: I could use my MacBook for weeks, before it started happening again. Impossible to figure out if I removed what causes the problem, there's no trial and error way.
     
  13. HunPro, Feb 23, 2015
    Last edited: Feb 23, 2015

    HunPro thread starter macrumors member

    Joined:
    Oct 28, 2013
    Location:
    Budapest, Hungary
    #13
    Good (?) news

    So even though it's a hardware error, there is a software side to it.

    Apple's USB drivers are not robust enough.

    For the first time since it started occuring, I could regain the keyboard/trackpad, without putting the machine to sleep or cycle the power.

    The method:

    1. Bluetooth was off, when the keyboard/trackpad died.
    2. The keyboard/trackpad died
    3. I used an external keyboard/mouse to go to System Preferences, and turned bluetooth back on
    4. The keyboard/trackpad came back to life!

    I started using it, and it all went well until I opened the Mail app, which started using the cpu at full speed, and then everything died: keyboard, trackpad and the bluetooth controller.

    The bluetooth icon is crossed out (with a buzzsaw):
    [​IMG]

    Here's the console log for the successful keyboard/trackpad reactivation trough bluetooth:
    Code:
    2015.02.23. 11:10:49,000 kernel[0]: **** [IOBluetoothHostControllerUSBTransport][SuspendDevice] -- Resume -- suspendDeviceCallResult = 0x0000 (kIOReturnSuccess) -- 0x6c00 ****
    2015.02.23. 11:10:49,000 kernel[0]: [BluetoothHCISetAFHHostChannelClassification] fails because POWER IS OFF
    2015.02.23. 11:10:49,000 kernel[0]: [BluetoothHCIReadLocalSupportedFeatures] fails because POWER IS OFF
    2015.02.23. 11:10:56,732 iTunes[269]: Entered:_AMMuxedDeviceDisconnected, mux-device:5
    2015.02.23. 11:10:56,732 iTunes[269]: Entered:__thr_AMMuxedDeviceDisconnected, mux-device:5
    2015.02.23. 11:10:56,734 iTunes[269]: tid:f2bf - Mux ID not found in mapping dictionary
    2015.02.23. 11:10:56,734 iTunes[269]: tid:f2bf - Can't handle disconnect with invalid ecid
    2015.02.23. 11:11:20,000 kernel[0]: **** [IOBluetoothHostControllerUSBTransport][SuspendDevice] -- Suspend -- suspendDeviceCallResult = 0x0000 (kIOReturnSuccess) -- 0x6c00 ****
    And here's an excerpt from the complete death of all the USB devices on that hub:
    Code:
    2015.02.23. 11:14:48,000 kernel[0]: Apple Internal Keyboard / Trackpad::terminate(kIOServiceSynchronous) timeout
    2015.02.23. 11:14:48,000 kernel[0]: USBF:    1793.921    AppleUSBHubPort::FatalError - Port 2 of Hub at 0xfa100000 reported error 0xe00002ed while doing clearing port feature (4)
    2015.02.23. 11:14:49,000 kernel[0]: **** [BroadcomBluetoothHostControllerUSBTransport][LMPLoggingBulkOutWriteCompleteHandler] -- Received 0xe00002eb (kIOReturnAborted); inBufferSizeRemaining = 0x00000002; isInactive = FALSE, suspended = TRUE -- 0x6c00
    2015.02.23. 11:14:49,000 kernel[0]: USBF:    1794.408    AppleUSBHubPort::FatalError - Port 1 of Hub at 0xfa100000 reported error 0xe00002c0 while doing setting port power
    2015.02.23. 11:14:49,000 kernel[0]: USBF:    1794.408    AppleUSBHubPort::FatalError - Port 2 of Hub at 0xfa100000 reported error 0xe00002c0 while doing setting port power
    2015.02.23. 11:14:49,000 kernel[0]: USBF:    1794.408    AppleUSBHubPort::FatalError - Port 3 of Hub at 0xfa100000 reported error 0xe00002c0 while doing setting port power
    As you can see from the age of this topic, I was pretty calm about this problem.

    You see it's hard to pinpoint to a given component: maybe the bluetooth chip, maybe the top case, maybe the logic board.

    I find no help out there, and now in the light of the 17" MacBook Pro replacements from the same era, I'm a bit mad.

    13" Retina Macbook Pro users got similar errors in the past. I can find their topics by searching for these exact error messages. They received an EFI update, and I'm left here hanging.

    I know that this problem is not unique to me: there are others out there, reporting the same problems, the same chain of events, trying the same methods over and over again, to no avail.

    It is maddening, I would replace this laptop, even though it cost me serious money in 2011 as it's nearly topped out, but I just can't trust Apple.

    I paid the Apple tax and I have a laptop that couldn't last as long as any of the plastic Windows crap that I used before. I have a crappy 2007 Acer (with an AMD chip and dedicated graphics, a dangerous combo), punished beyond imagination, and it still works.

    One of the richest companies in the world, bragging about customer satisfaction, leaves me in the dirt or gives me cynical options that cost so much that I'm better of buying something new.

    Appalling.
     

    Attached Files:

  14. motrek macrumors 68020

    Joined:
    Sep 14, 2012
    #14
    You need to get a grip. It's a bad situation but now you're ranting and raving as if Apple hired a hit man to kill your wife.
     
  15. HunPro thread starter macrumors member

    Joined:
    Oct 28, 2013
    Location:
    Budapest, Hungary
    #15
    I haven't even used caps!

    Seriously, if you read the whole topic, you'll see that it's almost a year old. I went to the extremes, even disassembled it.

    And I'm not the only one: so many people report similar problems, only to be dismissed or ignored.

    Having stuck with a laptop that I can't even sell as parts with a good conscience is a pretty hopeless place.

    I have work to do, and yet I'm stuck googling for "error 0xe00002ed" hoping to find just one person who overcame this problem.

    If you want rant and rave, check out the comments section at Ars Technica, where users had to wait 4 years to get recognition from Apple.

    They bought the most expensive MacBook. And it's Ars Technica.
     
  16. motrek macrumors 68020

    Joined:
    Sep 14, 2012
    #16
    Maddening... appalling... leaving you in the dirt...

    Really? Did Apple really "leave you in the dirt"? I see that you are from Hungary so maybe English is your Nth language and you don't understand all of its nuances. But these are not expressions that really make sense in the context of a laptop that costs, at most, a couple thousand dollars.

    I'm sorry that you're having trouble with your laptop but the way you're talking about it doesn't engender much sympathy.

    And of course you can sell it for parts, presumably the screen and SSD and so forth work fine, right? And if it functions well in lid-closed mode, just make that clear in any ad that you post of the laptop. Presumably you can sell the laptop for the same price as an equivalently-specced Mac Mini since you said it functions well as such, right?

    If you're really in such mental anguish over this then do something about it.

    I understand that $1000-$2000 is a significant amount of money but worse things could happen. I've had several car repairs that cost more than that.
     
  17. HunPro, Feb 24, 2015
    Last edited: Feb 24, 2015

    HunPro thread starter macrumors member

    Joined:
    Oct 28, 2013
    Location:
    Budapest, Hungary
    #17
    I didn't come here for comforting or sympathy, I came here to find others with a similar problem, to get constructive advice.

    Car repairs are costly, but at least cars usually have common, easily reproducible problems. Also, relativizing this is not helpful at all.

    You might as well go to any topic here and tell people to quit bitching about Apple's SSD pricing and just go with the topped out model, it's nothing compared to a mortgage.

    You contributed nothing to this topic, it's no help to anyone who finds this by googling the symptoms, it's similar to the cynical and dismissive attitude that the 17" 2011 MacBook Pro owners got for years from Apple.

    Until their problem was acknowledged.
     
  18. HunPro thread starter macrumors member

    Joined:
    Oct 28, 2013
    Location:
    Budapest, Hungary
    #18
    Recent freeze, new log entries

    Code:
    2015.03.10. 14:02:52,000 kernel[0]: AppleUSBMultitouchDebug: _deviceGetReport returned an error in configureDataMode
    2015.03.10. 14:02:52,000 kernel[0]: **** [BroadcomBluetoothHostControllerUSBTransport][LMPLoggingBulkOutWriteCompleteHandler] -- Received 0xe00002eb (kIOReturnAborted); inBufferSizeRemaining = 0x00000002; isInactive = FALSE, suspended = TRUE -- 0xa800
    2015.03.10. 14:02:52,000 kernel[0]: USBF:    8831.126    AppleUSBHub::ConfigureHub(hub @ 0xfa100000)  could not get hub descriptor (0xe00002c0)
    2015.03.10. 14:02:52,000 kernel[0]: USBF:    8831.228    AppleUSBHubPort::FatalError - Port 1 of Hub at 0xfa100000 reported error 0xe00002c0 while doing getting port status (2)
    2015.03.10. 14:02:52,000 kernel[0]: USBF:    8831.228    AppleUSBHubPort::FatalError - Port 2 of Hub at 0xfa100000 reported error 0xe00002c0 while doing getting port status (2)
    
    Highlighted:
    Code:
    AppleUSBHub::ConfigureHub(hub @ 0xfa100000)  could not get hub descriptor (0xe00002c0)

    It all began with:
    Code:
    AppleUSBMultitouchDriver::message - kIOUSBMessagePortHasBeenReset.
    
    :(

    ----------

    By googling for the symptoms, I managed to find someone who's having the exact problem. I'm trying to contact him.

    His post was in Spanish, here's the google translate version:

    Good, after changing my plate full in the official Apple store less than a month ago, now it is giving me problems bluetooth. The fault I found is that even having it disconnected and no active bluetooth device around, I get stuck the magic touchpad and keyboard, and the bluetooth icon a horizontal line. Until that line is not going no I can keep working. It has come to stay fixed touching reboot. You think you may be related to the change? I made an appointment to take it and see what we do, but as I touch back to pay for it I put a complaint form and consumption. I never fail anything and after repair start having problems flake me enough ... I took the Saturday morning, I'll tell you I'm told.
    PS I just did while writing, hit the log if there are any who understand
     
  19. HunPro thread starter macrumors member

    Joined:
    Oct 28, 2013
    Location:
    Budapest, Hungary
    #19
    This problem really brings out the animal from people:

    [​IMG]
     

    Attached Files:

  20. SmOgER, Mar 10, 2015
    Last edited: Mar 10, 2015

    SmOgER macrumors 6502a

    Joined:
    Jun 2, 2014
    #20
    Do you have anything at all connected to the MBA (usb/sd cards...) when this happens?
    If I were you, I would try figuring out the way to reinstall/downgrade the EFI/SMC. Usually when my mac wakes from deeper sleep it takes up to 5sec for keyboard and trackpad to respond, that's the same behavior on the first and second MBA I'am having (both 2011 13"). Actually I can now recall 1 or 2 times when it failed to respond at all and I had to restart as well. I can see how this might become a serious problem if the are errors in the SMC/EFI, the fact that resetting them temporarily solves the issue kinda supports my theory.

    Oh, and what about the bootcamp, does it freeze there as well?
     
  21. HunPro thread starter macrumors member

    Joined:
    Oct 28, 2013
    Location:
    Budapest, Hungary
    #21
    No, only the magsafe cable.

    But it did happen while on battery power before. I'm not sure if it's less likely while on battery, it feels like it, but it might just be wishful thinking.

    I've looked into that, but I couldn't find a soultion. I just get an "unsupported" error message when I try to reinstall the SMC upgrade. Both the SMC and the EFI is up-to-date.

    Downgrading seems to be a bad idea, as users have been reporting similar problems since 2012, so I'm not sure how far I should go. If it's too troublesome, then doing this by trial and error is not an option.

    I already have trouble reproducing it, which makes troubleshooting a nightmare.

    Yes, it has to be some software problem. Even if the trackpad sometimes sends corrupt data, it seems that older firmwares or OSX versions where more robust.

    I've seen people who encountered this after upgrading from Lion.

    I kept Lion for more than 2 years, I upgraded to Mavericks, skipping Mountain Lion. I don't recall this problem with Lion.

    I don't have bootcamp, with only 256GB of SSD space, on a production machine, I can't afford a separate Windows install.

    Also the problem is hard to reproduce. I wish that the keyboard/bluetooth/trackpad would always die within 2 minutes after booting, that way I could test it.

    When I did the clean install of Yosemite beta last summer, I was really excited. Everything worked for one and a half days, I even stress tested it by playing multiple youtube videos. But then the error happened again.

    I believe that if it's not a serious hardware problem, then it's either something with the SMC/EFI or something introduced to the OSX drivers after Lion.

    I keep my sanity by googling this from time to time, and I find people with exactly the same problem. Crossed out bluetooth icon. Right side ports dead, but left side working. It has to be something specific.
     
  22. HunPro thread starter macrumors member

    Joined:
    Oct 28, 2013
    Location:
    Budapest, Hungary
    #22
    Last freeze with some new errors (trimmed for readability):

    AppleUSBMultitouchDriver::message - kIOUSBMessagePortHasBeenReset.
    AppleUSBMultitouchDriver::checkStatus - received Status Packet, Payload 2: device was reinitialized
    AppleUSBMultitouchDriver::_deviceGetReport - DeviceRequest for reportID 0x0 returned with result 0xe000404b - retrying

    ...

    AppleUSBMultitouchDriver::_deviceGetReport - DeviceRequest returned error 0xe00002eb (interface 0, reportID 0x0)
    AppleUSBMultitouchDebug: _deviceGetReport returned an error in configureDataMode
    MultitouchHID: device bootloaded

    ...

    AppleUSBHubPort::FatalError - Port 2 of Hub at 0xfa100000 reported error 0xe00002ed while doing get status (first in port status change)

    ...

    Apple Internal Keyboard / Trackpad::terminate(kIOServiceSynchronous) timeout
    USB Device Apple Internal Keyboard / Trackpad is violating Section 9.3.5 of the USB Specification -- Error in GetConfigDescriptor( wLength = 4)

    ...

    AppleUSBMultitouchDebug: _getFeatureReportInfo returned an error in AppleUSBMultitouchDriver::_deviceGetReportWithLookUp


    However, the bluetooth part of the "left side" USB hub remain accessible, and was visible in System Information.

    I tried to turn it on:

    [IOBluetoothHostControllerUSBTransport][SuspendDevice] -- Resume -- suspendDeviceCallResult = 0x0000 (kIOReturnSuccess) -- 0xc000 ****
    [BroadcomBluetoothHostControllerUSBTransport][LMPLoggingBulkInReadHandler] -- Received kIOReturnNotResponding error -- retrying: 1 -- 0xc000
    [BroadcomBluetoothHostControllerUSBTransport][LMPLoggingBulkInReadHandler] -- kIOReturnNotResponding -- Calling objPtr->mClearLMPLoggingBulkEndpointHaltThread() -- 0xc000
    [BroadcomBluetoothHostControllerUSBTransport][ClearLMPLoggingBulkEndpointHalt] -- DeviceRequest() failed 0xE000404F (kIOUSBPipeStalled) -- 0xc000 ****


    And then I got a crossed out bluetooth icon, and a lot of these entries:

    [SendRawHCICommand] ### ERROR: EnqueueRequestForController failed (err=e00002bc)
     
  23. HunPro thread starter macrumors member

    Joined:
    Oct 28, 2013
    Location:
    Budapest, Hungary
    #23
    Here are the hubs compared for two different states:

    [​IMG]

    [​IMG]

    The Keyboard Hub part is the external keyboard/mouse that I connected to have control after failures.

    As you can see, the memory card reader is not affected: that rules out the IO Board.


    Another interesting event happened: after the last failure, I've put it to sleep by closing the lid. Instead, my MacBook shut down.

    This is what happened:

    SMC::smcInitHelper ERROR: MMIO regMap == NULL - fall back to old SMC mode

    Here are the smc related logs for that period. The shutdown happened between 15:17 and 15:27

    2015.03.12. 15:16:29,000 kernel[0]: SMC::smcReadKeyAction ERROR: smcReadData8 failed for key LsNM (kSMCKeyNotFound)
    2015.03.12. 15:16:29,000 kernel[0]: SMC::smcReadKeyAction ERROR LsNM kSMCKeyNotFound(0x84) fKeyHashTable=0x0
    2015.03.12. 15:16:29,000 kernel[0]: SMC::smcGetLightshowVers ERROR: smcReadKey LsNM failed (kSMCKeyNotFound)
    2015.03.12. 15:16:29,000 kernel[0]: SMC::smcPublishLightshowVersion ERROR: smcGetLightshowVers failed (kSMCKeyNotFound)
    2015.03.12. 15:16:29,000 kernel[0]: SMC::smcInitHelper ERROR: smcPublishLightshowVersion failed (kSMCKeyNotFound)
    2015.03.12. 15:16:29,000 kernel[0]: SMC::smcInitHelper ERROR: MMIO regMap == NULL - fall back to old SMC mode
    2015.03.12. 15:17:29,000 kernel[0]: SMC::smcReadKeyAction ERROR: smcReadData8 failed for key B0OS (kSMCKeyNotFound)
    2015.03.12. 15:17:29,000 kernel[0]: SMC::smcReadKeyAction ERROR: smcReadData8 failed for key BC3V (kSMCKeyNotFound)
    2015.03.12. 15:27:13,000 kernel[0]: SMC::smcReadKeyAction ERROR: smcReadData8 failed for key LsNM (kSMCKeyNotFound)
    2015.03.12. 15:27:13,000 kernel[0]: SMC::smcReadKeyAction ERROR LsNM kSMCKeyNotFound(0x84) fKeyHashTable=0x0
    2015.03.12. 15:27:13,000 kernel[0]: SMC::smcGetLightshowVers ERROR: smcReadKey LsNM failed (kSMCKeyNotFound)
    2015.03.12. 15:27:13,000 kernel[0]: SMC::smcPublishLightshowVersion ERROR: smcGetLightshowVers failed (kSMCKeyNotFound)
    2015.03.12. 15:27:13,000 kernel[0]: SMC::smcInitHelper ERROR: smcPublishLightshowVersion failed (kSMCKeyNotFound)
    2015.03.12. 15:27:13,000 kernel[0]: SMC::smcInitHelper ERROR: MMIO regMap == NULL - fall back to old SMC mode
    2015.03.12. 15:28:10,000 kernel[0]: SMC::smcReadKeyAction ERROR: smcReadData8 failed for key B0OS (kSMCKeyNotFound)
    2015.03.12. 15:28:11,000 kernel[0]: SMC::smcReadKeyAction ERROR: smcReadData8 failed for key BC3V (kSMCKeyNotFound)
     

    Attached Files:

  24. HunPro thread starter macrumors member

    Joined:
    Oct 28, 2013
    Location:
    Budapest, Hungary
    #24
    Still not giving up

    [​IMG]

    Yesterday I took my MacBook apart, and did the following:

    • removed the battery
    • disconnected the ribbon cable running from the logic board to the touchpad
    • removed the bluetooth/wifi card
    • cleaned all these connections with alcohol
    • cleaned the magsafe port with alcohol
    • reassembled the machine

    The two smcReadKeyAction errors (smcReadData8 failed for key B0OS, smcReadData8 failed for key BC3V) remained, but the 'fall back to old SMC mode' is gone!

    That message was reproducible before by cycling the power, so maybe something improved.

    The validateChecksum error still remains, you can see it here happening during power nap:

    [​IMG]

    This was actual sleep for me, so there was no physical contact with the machine. It was on my desk, lid shut. Interestingly, it happens during the first power nap at 0:55, and the rest of these wakeups go trouble free (assuming that the reinitialization is normal).
     

    Attached Files:

  25. HunPro thread starter macrumors member

    Joined:
    Oct 28, 2013
    Location:
    Budapest, Hungary
    #25
    It happened again.

    I try to provide a step-by-step breakdown:

    AppleUSBMultitouchDriver::message - kIOUSBMessagePortHasBeenReset.

    This should be normal, or at least an official workaround done by Apple, according to a post from 2009

    AppleUSBMultitouchDriver::checkStatus - received Status Packet, Payload 2: device was reinitialized
    MultitouchHID: device bootloaded
    AppleUSBMultitouchDriver::_deviceSetReport - DeviceRequest for reportID 0xc8 returned with result 0xe000404f - retrying


    This doesn't look good. "0xe000404f" gets some Google results where people report similar problems

    AppleUSBMultitouchDriver::message - kIOUSBMessagePortHasBeenReset.
    AppleUSBMultitouchDriver::message - kIOUSBMessagePortHasBeenReset.
    AppleUSBMultitouchDriver::checkStatus - received Status Packet, Payload 2: device was reinitialized


    And yet another go at reinitialization

    AppleUSBMultitouchDriver::_deviceGetReport - DeviceRequest for reportID 0x0 returned with result 0xe000404b - retrying
    AppleUSBMultitouchDriver::_deviceGetReport - DeviceRequest for reportID 0x0 returned with result 0xe00002eb - retrying
    AppleUSBMultitouchDriver::_deviceGetReport - DeviceRequest for reportID 0x0 returned with result 0xe000404b - retrying
    AppleUSBMultitouchDriver::_deviceGetReport - DeviceRequest for reportID 0x0 returned with result 0xe00002eb - retrying
    AppleUSBMultitouchDriver::_deviceSetReport - DeviceRequest for reportID 0x0 returned with result 0xe000404b - retrying
    AppleUSBMultitouchDriver::_deviceSetReport - DeviceRequest for reportID 0x0 returned with result 0xe00002eb - retrying
    AppleUSBMultitouchDriver::_deviceSetReport - DeviceRequest for reportID 0xac returned with result 0xe000404b - retrying
    AppleUSBMultitouchDriver::_deviceSetReport - DeviceRequest for reportID 0xac returned with result 0xe00002eb - retrying
    AppleUSBMultitouchDriver::_deviceSetReport - DeviceRequest for reportID 0xac returned with result 0xe00002eb - retrying
    AppleUSBMultitouchDriver::_deviceSetReport - DeviceRequest for reportID 0xac returned with result 0xe000404b - retrying
    AppleUSBMultitouchDriver::_deviceSetReport - DeviceRequest for reportID 0xac returned with result 0xe000404b - retrying
    AppleUSBMultitouchDriver::_deviceSetReport - DeviceRequest for reportID 0xac returned with result 0xe00002eb - retrying


    "0xe00002eb" also gets results. This if for "0xe00002eb macbook air": https://discussions.apple.com/thread/5633084

    "MBA Mid 2013 (A1466) Mac OS X 10.8.5 built-in keyboard and trackpad not working"

    AppleUSBMultitouchDriver::_deviceSetReport - DeviceRequest returned error 0xe00002eb (interface 1, reportID 0xac, payload AppleUSBMultitouchDriver::_deviceSetReport - DeviceRequest returned error 0xe000404b (interface 1, reportID 0xac, payload 2
    AppleUSBMultitouchDebug: _deviceSetReport returned an error in configureDataMode
    2
    AppleUSBMultitouchDebug: _deviceSetReport returned an error in configureDataMode
    MultitouchHID: device bootloaded


    Now it says error, instead of retrying. "MultitouchHID: device bootloaded" again, but now it's in a different state, still retrying these steps:

    AppleUSBMultitouchDriver::_deviceGetReport - DeviceRequest for reportID 0xc8 returned with result 0xe000404f - retrying
    AppleUSBMultitouchDriver::_deviceSetReport - DeviceRequest for reportID 0xc8 returned with result 0xe000404b - retrying
    AppleUSBMultitouchDriver::_deviceSetReport - DeviceRequest for reportID 0xc8 returned with result 0xe0004061 - retrying
    AppleUSBMultitouchDriver::_deviceSetReport - DeviceRequest for reportID 0xc8 returned with result 0xe0004061 - retrying
    AppleUSBMultitouchDriver::_deviceSetReport - DeviceRequest for reportID 0xc8 returned with result 0xe0004061 - retrying
    AppleUSBMultitouchDriver::_deviceSetReport - DeviceRequest returned error 0xe0004061 (interface 1, reportID 0xc8, payload 9


    A new code: "0xe0004061". And it has similar results: "Keyboard, Trackpad and USB on Mac Air not working with latest OS update"
    "My 2009 Mac Air after the last OS update, the only thing that seems to work now is the power button. The USB port, Keyboard and trackpad all dead. Help!"

    No help of course, and in this case, not even from an Apple store.

    AppleUSBMultitouchDriver::message - kIOUSBMessagePortHasBeenReset.

    I resets once again

    AppleUSBMultitouchDriver::_deviceGetReport - DeviceRequest returned error 0xe00002c0 (interface 0, reportID 0x0)
    AppleUSBMultitouchDebug: _deviceGetReport returned an error in configureDataMode
    considerRebuildOfPrelinkedKernel prebuild rebuild has expired
    AppleUSBMultitouchDriver::_deviceGetReport - DeviceRequest returned error 0xe00002c0 (interface 0, reportID 0x0)
    AppleUSBMultitouchDebug: _deviceGetReport returned an error in configureDataMode


    A new code: "0xe00002c0". Also have results: http://www.applephoon.com/Macbook-Air-13-Mid-2011-Keyboard-and-Trac-thread-103925-1-1.html
    "Macbook Air 13" Mid-2011 Keyboard and Trackpad freezing"
    The only answer: "You have to take the computer to the Apple store to have it checked out.
    Best."


    Not really helpful.

    AppleUSBMultitouchDriver::_getFeatureReportInfo - DeviceRequest returned with result 0xe000404b - retrying (reportID 0xd1)
    AppleUSBMultitouchDriver::_getFeatureReportInfo - DeviceRequest returned error 0xe000404f (interface 1, reportID 0xd1)
    AppleUSBMultitouchDebug: _getFeatureReportInfo returned an error in AppleUSBMultitouchDriver::_deviceGetReportWithLookUp
    AppleUSBMultitouchDriver::_getFeatureReportInfo - DeviceRequest returned with result 0xe000404f - retrying (reportID 0xd3)
    AppleUSBMultitouchDriver::_getFeatureReportInfo - DeviceRequest returned error 0xe000404f (interface 1, reportID 0xd3)
    AppleUSBMultitouchDebug: _getFeatureReportInfo returned an error in AppleUSBMultitouchDriver::_deviceGetReportWithLookUp
    AppleUSBMultitouchDriver::_getFeatureReportInfo - DeviceRequest returned with result 0xe000404f - retrying (reportID 0xd0)
    AppleUSBMultitouchDriver::_getFeatureReportInfo - DeviceRequest returned error 0xe000404b (interface 1, reportID 0xd0)
    AppleUSBMultitouchDebug: _getFeatureReportInfo returned an error in AppleUSBMultitouchDriver::_deviceGetReportWithLookUp
    AppleUSBMultitouchDriver::_getFeatureReportInfo - DeviceRequest returned with result 0xe000404b - retrying (reportID 0xa1)
    AppleUSBMultitouchDriver::_getFeatureReportInfo - DeviceRequest returned error 0xe000404b (interface 1, reportID 0xa1)
    AppleUSBMultitouchDebug: _getFeatureReportInfo returned an error in AppleUSBMultitouchDriver::_deviceGetReportWithLookUp
    AppleUSBMultitouchDriver::_getFeatureReportInfo - DeviceRequest returned with result 0xe000404b - retrying (reportID 0xd9)
    AppleUSBMultitouchDriver::_getFeatureReportInfo - DeviceRequest returned error 0xe000404b (interface 1, reportID 0xd9)
    AppleUSBMultitouchDebug: _getFeatureReportInfo returned an error in AppleUSBMultitouchDriver::_deviceGetReportWithLookUp


    And it's pretty much dead at this point. Everything up to this covered a period of 3 seconds.

    Now I plug in an external keyboard/mouse to the right side port (the one that eventually dies), and turn bluetooth on:

    **** [IOBluetoothHostControllerUSBTransport][SuspendDevice] -- Resume -- suspendDeviceCallResult = 0x0000 (kIOReturnSuccess) -- 0xf800 ****
    **** [BroadcomBluetoothHostControllerUSBTransport][LMPLoggingBulkInReadHandler] -- Received kIOReturnNotResponding error -- retrying: 1 -- 0xf800
    **** [BroadcomBluetoothHostControllerUSBTransport][LMPLoggingBulkInReadHandler] -- kIOReturnNotResponding -- Calling objPtr->mClearLMPLoggingBulkEndpointHaltThread() -- 0xf800
    **** [BroadcomBluetoothHostControllerUSBTransport][ClearLMPLoggingBulkEndpointHalt] -- DeviceRequest() failed 0xE000404F (kIOUSBPipeStalled) -- 0xf800 ****
    **** [BroadcomBluetoothHostControllerUSBTransport][ClearLMPLoggingBulkEndpointHalt] -- Calling DoDeviceReset() due to the error of posting a read on the Bulk pipe for LMP Logging -- 0xf800 ****
    **** [IOBluetoothHostControllerUSBTransport][DoDeviceReset] -- success = FALSE -- 0xf800 ****
    **** [IOBluetoothHostControllerUSBTransport][HubResetThreadEntry] -- 0xf800
    **** [IOBluetoothHostControllerUSBTransport][HubReset] -- entering -- 0xf800 ****
    **** [IOBluetoothHostControllerUSBTransport][HubReset] -- in our workloop -- 0xf800 ****
    [IOBluetoothHostControllerUSBTransport][HubReset] -- calling myHub->ReEnumerateDevice() -- gEnumerateCounter = 1
    [IOBluetoothHostControllerUSBTransport][HubReset] -- exit; error = 0x0000 (kIOReturnSuccess)
    **** [BroadcomBluetoothHostControllerUSBTransport][LMPLoggingBulkOutWriteCompleteHandler] -- Received 0xe00002eb (kIOReturnAborted); inBufferSizeRemaining = 0x00000002; isInactive = FALSE, suspended = FALSE -- 0xf800
    IOBluetoothUSBDFU::probe
    (thanks)
    IOBluetoothUSBDFU::probe ProductID - 0x821F FirmwareVersion - 0x0143
    **** [IOBluetoothHostControllerUSBTransport][start] -- completed -- result = TRUE -- 0x0c00 ****
    **** [BroadcomBluetoothHostControllerUSBTransport][start] -- Completed -- 0x0c00 ****
    [IOBluetoothHCIController][staticBluetoothHCIControllerTransportShowsUp] -- Received Bluetooth Controller register service notification -- 0x0c00
    [IOBluetoothHCIController::setConfigState] calling registerService
    **** [IOBluetoothHCIController][protectedBluetoothHCIControllerTransportShowsUp] -- Connected to the transport successfully -- 0x40c0 -- 0x4000 -- 0x0c00 ****


    Bluetooth struggling to wake up. Some messages that have been reported by others:

    **** [IOBluetoothHostControllerUSBTransport][InterruptReadHandler] -- Received kIOUSBHighSpeedSplitError error - retrying: 1 -- 0x0c00
    **** [IOBluetoothHostControllerUSBTransport][InterruptReadHandler] -- Received kIOUSBHighSpeedSplitError error - retrying: 2 -- 0x0c00
    **** [BroadcomBluetoothHostControllerUSBTransport][LMPLoggingBulkInReadHandler] -- Received kIOUSBPipeStalled error -- retrying: 1 -- 0x0c00
    **** [BroadcomBluetoothHostControllerUSBTransport][LMPLoggingBulkInReadHandler] -- kIOUSBPipeStalled -- Calling objPtr->mClearLMPLoggingBulkEndpointHaltThread() -- 0x0c00
    **** [BroadcomBluetoothHostControllerUSBTransport][ClearLMPLoggingBulkEndpointHalt] -- DeviceRequest() failed 0xE000404F (kIOUSBPipeStalled) -- 0x0c00 ****
    **** [BroadcomBluetoothHostControllerUSBTransport][ClearLMPLoggingBulkEndpointHalt] -- Calling DoDeviceReset() due to the error of posting a read on the Bulk pipe for LMP Logging -- 0x0c00 ****
    **** [IOBluetoothHostControllerUSBTransport][DoDeviceReset] -- success = FALSE -- 0x0c00 ****
    **** [IOBluetoothHostControllerUSBTransport][HubResetThreadEntry] -- 0x0c00
    **** [IOBluetoothHostControllerUSBTransport][HubReset] -- entering -- 0x0c00 ****
    **** [IOBluetoothHostControllerUSBTransport][HubReset] -- in our workloop -- 0x0c00 ****
    [IOBluetoothHostControllerUSBTransport][HubReset] -- calling myHub->ReEnumerateDevice() -- gEnumerateCounter = 1
    [IOBluetoothHostControllerUSBTransport][HubReset] -- exit; error = 0x0000 (kIOReturnSuccess)


    It's pretty much a rerun of the previous cycle.

    I will skip some lines, and get to the end, focusing on USBF:

    **** [IOBluetoothHCIController][SetupBroadcomHardware] -- ModuleIsInUHEMode() failed -- result = 0x0010 (kBluetoothHCIErrorHostTimeout) -- retry 1 time(s) -- 0x4000 ****
    CompositeDevice::terminate(kIOServiceSynchronous) timeout
    USBF: 4999.672 AppleUSBHubPort::FatalError - Port 1 of Hub at 0xfa110000 reported error 0xe00002c0 while doing getting port status (7)
    USBF: 4999.683 AppleUSBHubPort::FatalError - Port 2 of Hub at 0xfa110000 reported error 0xe00002c0 while doing getting port status (7)
    [...]
    USBF: 4999.953 The IOUSBFamily is having trouble enumerating a USB device that has been plugged in. It will keep retrying. (Port 1 of Hub at 0xfa100000)
    USBF: 5000. 17 AppleUSBHubPort::FatalError - Port 1 of Hub at 0xfa100000 reported error 0xe00002ed while doing getting port status (5)
    USBF: 5000. 17 The IOUSBFamily was not able to enumerate a device.


    Yay!

    ----------

    It happened again.

    I try to provide a step-by-step breakdown:

    AppleUSBMultitouchDriver::message - kIOUSBMessagePortHasBeenReset.

    This should be normal, or at least an official workaround done by Apple, according to a post from 2009

    AppleUSBMultitouchDriver::checkStatus - received Status Packet, Payload 2: device was reinitialized
    MultitouchHID: device bootloaded
    AppleUSBMultitouchDriver::_deviceSetReport - DeviceRequest for reportID 0xc8 returned with result 0xe000404f - retrying


    This doesn't look good. "0xe000404f" gets some Google results where people report similar problems

    AppleUSBMultitouchDriver::message - kIOUSBMessagePortHasBeenReset.
    AppleUSBMultitouchDriver::message - kIOUSBMessagePortHasBeenReset.
    AppleUSBMultitouchDriver::checkStatus - received Status Packet, Payload 2: device was reinitialized


    And yet another go at reinitialization

    AppleUSBMultitouchDriver::_deviceGetReport - DeviceRequest for reportID 0x0 returned with result 0xe000404b - retrying
    AppleUSBMultitouchDriver::_deviceGetReport - DeviceRequest for reportID 0x0 returned with result 0xe00002eb - retrying
    AppleUSBMultitouchDriver::_deviceGetReport - DeviceRequest for reportID 0x0 returned with result 0xe000404b - retrying
    AppleUSBMultitouchDriver::_deviceGetReport - DeviceRequest for reportID 0x0 returned with result 0xe00002eb - retrying
    AppleUSBMultitouchDriver::_deviceSetReport - DeviceRequest for reportID 0x0 returned with result 0xe000404b - retrying
    AppleUSBMultitouchDriver::_deviceSetReport - DeviceRequest for reportID 0x0 returned with result 0xe00002eb - retrying
    AppleUSBMultitouchDriver::_deviceSetReport - DeviceRequest for reportID 0xac returned with result 0xe000404b - retrying
    AppleUSBMultitouchDriver::_deviceSetReport - DeviceRequest for reportID 0xac returned with result 0xe00002eb - retrying
    AppleUSBMultitouchDriver::_deviceSetReport - DeviceRequest for reportID 0xac returned with result 0xe00002eb - retrying
    AppleUSBMultitouchDriver::_deviceSetReport - DeviceRequest for reportID 0xac returned with result 0xe000404b - retrying
    AppleUSBMultitouchDriver::_deviceSetReport - DeviceRequest for reportID 0xac returned with result 0xe000404b - retrying
    AppleUSBMultitouchDriver::_deviceSetReport - DeviceRequest for reportID 0xac returned with result 0xe00002eb - retrying


    "0xe00002eb" also gets results. This if for "0xe00002eb macbook air": https://discussions.apple.com/thread/5633084

    "MBA Mid 2013 (A1466) Mac OS X 10.8.5 built-in keyboard and trackpad not working"

    AppleUSBMultitouchDriver::_deviceSetReport - DeviceRequest returned error 0xe00002eb (interface 1, reportID 0xac, payload AppleUSBMultitouchDriver::_deviceSetReport - DeviceRequest returned error 0xe000404b (interface 1, reportID 0xac, payload 2
    AppleUSBMultitouchDebug: _deviceSetReport returned an error in configureDataMode
    2
    AppleUSBMultitouchDebug: _deviceSetReport returned an error in configureDataMode
    MultitouchHID: device bootloaded


    Now it says error, instead of retrying. "MultitouchHID: device bootloaded" again, but now it's in a different state, still retrying these steps:

    AppleUSBMultitouchDriver::_deviceGetReport - DeviceRequest for reportID 0xc8 returned with result 0xe000404f - retrying
    AppleUSBMultitouchDriver::_deviceSetReport - DeviceRequest for reportID 0xc8 returned with result 0xe000404b - retrying
    AppleUSBMultitouchDriver::_deviceSetReport - DeviceRequest for reportID 0xc8 returned with result 0xe0004061 - retrying
    AppleUSBMultitouchDriver::_deviceSetReport - DeviceRequest for reportID 0xc8 returned with result 0xe0004061 - retrying
    AppleUSBMultitouchDriver::_deviceSetReport - DeviceRequest for reportID 0xc8 returned with result 0xe0004061 - retrying
    AppleUSBMultitouchDriver::_deviceSetReport - DeviceRequest returned error 0xe0004061 (interface 1, reportID 0xc8, payload 9


    A new code: "0xe0004061". And it has similar results: "Keyboard, Trackpad and USB on Mac Air not working with latest OS update"
    "My 2009 Mac Air after the last OS update, the only thing that seems to work now is the power button. The USB port, Keyboard and trackpad all dead. Help!"

    No help of course, and in this case, not even from an Apple store.

    AppleUSBMultitouchDriver::message - kIOUSBMessagePortHasBeenReset.

    I resets once again

    AppleUSBMultitouchDriver::_deviceGetReport - DeviceRequest returned error 0xe00002c0 (interface 0, reportID 0x0)
    AppleUSBMultitouchDebug: _deviceGetReport returned an error in configureDataMode
    considerRebuildOfPrelinkedKernel prebuild rebuild has expired
    AppleUSBMultitouchDriver::_deviceGetReport - DeviceRequest returned error 0xe00002c0 (interface 0, reportID 0x0)
    AppleUSBMultitouchDebug: _deviceGetReport returned an error in configureDataMode


    A new code: "0xe00002c0". Also have results: http://www.applephoon.com/Macbook-Air-13-Mid-2011-Keyboard-and-Trac-thread-103925-1-1.html
    "Macbook Air 13" Mid-2011 Keyboard and Trackpad freezing"
    The only answer: "You have to take the computer to the Apple store to have it checked out.
    Best."


    Not really helpful.

    AppleUSBMultitouchDriver::_getFeatureReportInfo - DeviceRequest returned with result 0xe000404b - retrying (reportID 0xd1)
    AppleUSBMultitouchDriver::_getFeatureReportInfo - DeviceRequest returned error 0xe000404f (interface 1, reportID 0xd1)
    AppleUSBMultitouchDebug: _getFeatureReportInfo returned an error in AppleUSBMultitouchDriver::_deviceGetReportWithLookUp
    AppleUSBMultitouchDriver::_getFeatureReportInfo - DeviceRequest returned with result 0xe000404f - retrying (reportID 0xd3)
    AppleUSBMultitouchDriver::_getFeatureReportInfo - DeviceRequest returned error 0xe000404f (interface 1, reportID 0xd3)
    AppleUSBMultitouchDebug: _getFeatureReportInfo returned an error in AppleUSBMultitouchDriver::_deviceGetReportWithLookUp
    AppleUSBMultitouchDriver::_getFeatureReportInfo - DeviceRequest returned with result 0xe000404f - retrying (reportID 0xd0)
    AppleUSBMultitouchDriver::_getFeatureReportInfo - DeviceRequest returned error 0xe000404b (interface 1, reportID 0xd0)
    AppleUSBMultitouchDebug: _getFeatureReportInfo returned an error in AppleUSBMultitouchDriver::_deviceGetReportWithLookUp
    AppleUSBMultitouchDriver::_getFeatureReportInfo - DeviceRequest returned with result 0xe000404b - retrying (reportID 0xa1)
    AppleUSBMultitouchDriver::_getFeatureReportInfo - DeviceRequest returned error 0xe000404b (interface 1, reportID 0xa1)
    AppleUSBMultitouchDebug: _getFeatureReportInfo returned an error in AppleUSBMultitouchDriver::_deviceGetReportWithLookUp
    AppleUSBMultitouchDriver::_getFeatureReportInfo - DeviceRequest returned with result 0xe000404b - retrying (reportID 0xd9)
    AppleUSBMultitouchDriver::_getFeatureReportInfo - DeviceRequest returned error 0xe000404b (interface 1, reportID 0xd9)
    AppleUSBMultitouchDebug: _getFeatureReportInfo returned an error in AppleUSBMultitouchDriver::_deviceGetReportWithLookUp


    And it's pretty much dead at this point. Everything up to this covered a period of 3 seconds.

    Now I plug in an external keyboard/mouse to the right side port (the one that eventually dies), and turn bluetooth on:

    **** [IOBluetoothHostControllerUSBTransport][SuspendDevice] -- Resume -- suspendDeviceCallResult = 0x0000 (kIOReturnSuccess) -- 0xf800 ****
    **** [BroadcomBluetoothHostControllerUSBTransport][LMPLoggingBulkInReadHandler] -- Received kIOReturnNotResponding error -- retrying: 1 -- 0xf800
    **** [BroadcomBluetoothHostControllerUSBTransport][LMPLoggingBulkInReadHandler] -- kIOReturnNotResponding -- Calling objPtr->mClearLMPLoggingBulkEndpointHaltThread() -- 0xf800
    **** [BroadcomBluetoothHostControllerUSBTransport][ClearLMPLoggingBulkEndpointHalt] -- DeviceRequest() failed 0xE000404F (kIOUSBPipeStalled) -- 0xf800 ****
    **** [BroadcomBluetoothHostControllerUSBTransport][ClearLMPLoggingBulkEndpointHalt] -- Calling DoDeviceReset() due to the error of posting a read on the Bulk pipe for LMP Logging -- 0xf800 ****
    **** [IOBluetoothHostControllerUSBTransport][DoDeviceReset] -- success = FALSE -- 0xf800 ****
    **** [IOBluetoothHostControllerUSBTransport][HubResetThreadEntry] -- 0xf800
    **** [IOBluetoothHostControllerUSBTransport][HubReset] -- entering -- 0xf800 ****
    **** [IOBluetoothHostControllerUSBTransport][HubReset] -- in our workloop -- 0xf800 ****
    [IOBluetoothHostControllerUSBTransport][HubReset] -- calling myHub->ReEnumerateDevice() -- gEnumerateCounter = 1
    [IOBluetoothHostControllerUSBTransport][HubReset] -- exit; error = 0x0000 (kIOReturnSuccess)
    **** [BroadcomBluetoothHostControllerUSBTransport][LMPLoggingBulkOutWriteCompleteHandler] -- Received 0xe00002eb (kIOReturnAborted); inBufferSizeRemaining = 0x00000002; isInactive = FALSE, suspended = FALSE -- 0xf800
    IOBluetoothUSBDFU::probe
    IOBluetoothUSBDFU::probe ProductID - 0x821F FirmwareVersion - 0x0143
    **** [IOBluetoothHostControllerUSBTransport][start] -- completed -- result = TRUE -- 0x0c00 ****
    **** [BroadcomBluetoothHostControllerUSBTransport][start] -- Completed -- 0x0c00 ****
    [IOBluetoothHCIController][staticBluetoothHCIControllerTransportShowsUp] -- Received Bluetooth Controller register service notification -- 0x0c00
    [IOBluetoothHCIController::setConfigState] calling registerService
    **** [IOBluetoothHCIController][protectedBluetoothHCIControllerTransportShowsUp] -- Connected to the transport successfully -- 0x40c0 -- 0x4000 -- 0x0c00 ****


    Bluetooth struggling to wake up. Some messages that have been reported by others:

    **** [IOBluetoothHostControllerUSBTransport][InterruptReadHandler] -- Received kIOUSBHighSpeedSplitError error - retrying: 1 -- 0x0c00
    **** [IOBluetoothHostControllerUSBTransport][InterruptReadHandler] -- Received kIOUSBHighSpeedSplitError error - retrying: 2 -- 0x0c00
    **** [BroadcomBluetoothHostControllerUSBTransport][LMPLoggingBulkInReadHandler] -- Received kIOUSBPipeStalled error -- retrying: 1 -- 0x0c00
    **** [BroadcomBluetoothHostControllerUSBTransport][LMPLoggingBulkInReadHandler] -- kIOUSBPipeStalled -- Calling objPtr->mClearLMPLoggingBulkEndpointHaltThread() -- 0x0c00
    **** [BroadcomBluetoothHostControllerUSBTransport][ClearLMPLoggingBulkEndpointHalt] -- DeviceRequest() failed 0xE000404F (kIOUSBPipeStalled) -- 0x0c00 ****
    **** [BroadcomBluetoothHostControllerUSBTransport][ClearLMPLoggingBulkEndpointHalt] -- Calling DoDeviceReset() due to the error of posting a read on the Bulk pipe for LMP Logging -- 0x0c00 ****
    **** [IOBluetoothHostControllerUSBTransport][DoDeviceReset] -- success = FALSE -- 0x0c00 ****
    **** [IOBluetoothHostControllerUSBTransport][HubResetThreadEntry] -- 0x0c00
    **** [IOBluetoothHostControllerUSBTransport][HubReset] -- entering -- 0x0c00 ****
    **** [IOBluetoothHostControllerUSBTransport][HubReset] -- in our workloop -- 0x0c00 ****
    [IOBluetoothHostControllerUSBTransport][HubReset] -- calling myHub->ReEnumerateDevice() -- gEnumerateCounter = 1
    [IOBluetoothHostControllerUSBTransport][HubReset] -- exit; error = 0x0000 (kIOReturnSuccess)


    It's pretty much a rerun of the previous cycle.

    I will skip some lines, and get to the end, focusing on USBF:

    **** [IOBluetoothHCIController][SetupBroadcomHardware] -- ModuleIsInUHEMode() failed -- result = 0x0010 (kBluetoothHCIErrorHostTimeout) -- retry 1 time(s) -- 0x4000 ****
    CompositeDevice::terminate(kIOServiceSynchronous) timeout
    USBF: 4999.672 AppleUSBHubPort::FatalError - Port 1 of Hub at 0xfa110000 reported error 0xe00002c0 while doing getting port status (7)
    USBF: 4999.683 AppleUSBHubPort::FatalError - Port 2 of Hub at 0xfa110000 reported error 0xe00002c0 while doing getting port status (7)
    [...]
    USBF: 4999.953 The IOUSBFamily is having trouble enumerating a USB device that has been plugged in. It will keep retrying. (Port 1 of Hub at 0xfa100000)
    USBF: 5000. 17 AppleUSBHubPort::FatalError - Port 1 of Hub at 0xfa100000 reported error 0xe00002ed while doing getting port status (5)
    USBF: 5000. 17 The IOUSBFamily was not able to enumerate a device.


    It's all dead. Yay!
     

Share This Page