Apple Event: May 7th at 7 am PT
From time to time, quite very often when I'm typing, the input is paused for about half a second then appears on the screen as I continue to type. I'm using the default MacBook Air keyboard with no external keyboards attached. I don't know if this is just the keyboard lagging or the whole screen is lagging. This is very annoying, is there a way to fix this? Could this be a hardware problem?
iPhone 4S, iOS 5.1
Well, no luck with the lsboxd fix. I just got the dreaded keyboard and trackpad lag again. It happened fairly soon after a wake from sleep, and I fixed it by rebooting.
Luckily, I was able to isolate the console log entries during which the lag occurred. This is the one that looks the most suspicious and coincided with the lagginess by timestamp:
5/14/13 3:04:36.000 AM kernel[0]: USBF: 26669.269 AppleUSBEHCI[0xffffff8041bbd000]::Found a transaction which hasn't moved in 5 seconds on bus 0x1a, timing out! (Addr: 2, EP: 0)
However, based on the bus number, it is for the Facetime camera on a separate USB bus than the Trackpad and Keyboard.
I went back further and saw these:
5/14/13 3:04:06.000 AM kernel[0]: USBMSC Identifier (non-unique): 000000000310 0x5ac 0x8404 0x310
5/14/13 3:04:06.000 AM kernel[0]: IOBluetoothUSBDFU::probe
5/14/13 3:04:06.000 AM kernel[0]: IOBluetoothUSBDFU::probe ProductID - 0x821F FirmwareVersion - 0x0100
5/14/13 3:04:06.000 AM kernel[0]: [BroadcomBluetoothHCIControllerUSBTransport][start] -- completed
5/14/13 3:04:06.000 AM kernel[0]: [IOBluetoothHCIController][staticBluetoothHCIControllerTransportShowsUp] -- Received Bluetooth Controller register service notification
5/14/13 3:04:06.000 AM kernel[0]: [IOBluetoothHCIController::setConfigState] calling registerService
5/14/13 3:04:06.000 AM kernel[0]: IOHIDDevice::newUserClient called on an inactive device
5/14/13 3:04:06.000 AM kernel[0]: IOHIDDevice::newUserClient called on an inactive device
5/14/13 3:04:06.000 AM kernel[0]: IOHIDDevice::newUserClient called on an inactive device
5/14/13 3:04:06.000 AM kernel[0]: IOHIDDevice::newUserClient called on an inactive device
5/14/13 3:04:06.000 AM kernel[0]: AppleUSBMultitouchDriver::checkStatus - received Status Packet, Payload 2: device was reinitialized
Other people have noticed this same error with wake from sleep on lid open and keyboard/trackpad lag:
http://www.reddit.com/r/applehelp/comments/15a6pi/macbook_air_13_2011_keyboardtr ackpad_not_working/
Original poster here,
I just hope that they fix this in the next firmware update or Mac OS X 10.9. It seems quite common on MacBook Airs.
Yeah, they gotta fix this soon. It is pretty maddening...
Anybody: does this lag happen to you every time you open your MBA's lid and wake it from deep sleep? That seems to be the most consistent way for me to reproduce keyboard or trackpad lag. HOWEVER, the lag has definitely happened out of nowhere, in the middle of a long session, so it is not only triggered by wake-from-deep-sleep...
I just definitely had some trackpad lag that corresponded with these console entries:
5/14/13 9:22:21.000 PM kernel[0]: AppleUSBMultitouchDriver::_deviceGetReport - DeviceRequest for reportID 0x0 returned with result 0xe000404f - retrying
5/14/13 9:22:25.000 PM kernel[0]: AppleUSBMultitouchDriver::_deviceGetReport - DeviceRequest for reportID 0x0 returned with result 0xe000404f - retrying
5/14/13 9:22:29.000 PM kernel[0]: AppleUSBMultitouchDriver::_deviceGetReport - DeviceRequest for reportID 0x0 returned with result 0xe000404f - retrying
This happened after a wake from deep sleep.
Not for me dchang0, I get this problem so randomly out of the blue when I'm even typing a document on Pages! It's making me very mad. For a span of 10 seconds or so, my MacBook Air doesn't respond to some of my keys but I'm not sure about my trackpad. Closing the laptop and opening it fixed this little problem for me. Mind you, this happens to me very rarely. I only had this problem 5 times now over the course of months.
Keyboard input lag doesn't happen that often too, to be honest. I guess I can now live safely and soundly now with my loving MacBook Air.
Or maybe I got used to the whole thing! Oh dear.
Jokes aside, I will post again if any problems concerning this pop up.
It doesn't happen often for me either, but when it does, it's usually really inconvenient...
Anyway, when it does happen, please check to see if the trackpad is frozen too. You'll probably notice that the pointer is missing (it disappears when typing, and that's normal). Then, you can frantically move and swipe on the trackpad, and the pointer won't show up until the trackpad finally begins to respond.
Usually, once the trackpad is back, the keys are also back.
Some other people have noted that it's just the internal keyboard and internal trackpad that locks up; they were able to continue using externally-attached USB mice and USB keyboards without trouble...
You are right dchang0! This just happened and the trackpad wasn't responding with the keys.
That's good and bad in some ways. The good news is that we can now search based on "trackpad freezes" or "trackpad lags" and find other people who have the same problem we do but didn't notice that the keyboard is also frozen.
The bad news is that nobody seems to have found a solid fix for that problem either.
Personally, I think it's a hardware issue. Probably a bad USB hub chip/controller that manages both the keyboard and trackpad. We just have to get enough people to band together for Apple to notice and do something about it, so joining hands with the "trackpad lags" people will ultimately help us.
Ha, I was just posting to say that I think the recent Thunderbolt v1.2 update http://support.apple.com/kb/DL1653 fixed the keyboard and trackpad freezing issue. I had been working for over 10 minutes without an issue. Then as soon as I click into the reply box on this website, they keyboard freezes and the "5/16/13 4:13:45.000 PM kernel[0]: AppleUSBMultitouchDriver::_deviceGetReport - DeviceRequest for reportID 0x0 returned with result 0xe000404f - retrying" message shows up in the console.
So far it doesn't seem as bad as it was before the install but I'll known more over the next 24 hours.
It's interesting that you mention the Thunderbolt update. That didn't fix the problem for me, BUT I DID manage to totally lock up my system (trackpad not working, keyboard not working except for power button, screen appears okay) when I plugged in a Thunderbolt-Gigabit-Ethernet adapter.
Anyway, some people have reported success clearing out caches, clearing out certain LaunchDaemons and StartupItems, etc. Maybe this will help some of you:
https://discussions.apple.com/thread/4315898
There are plenty of reports coming from non-MBA owners. Some MB Pros, some older MBs. So it MAY be software, but it sure seems that a lot of MBA owners are seeing this.
Also, I own an older MB unibody with the same software updates and nowhere near the same kinds of problems.
Oh, and some people have reported that replacing the top case or the trackpad of their MBA fixed the problem for them, but I did that already, and it did not work for me.
I repaired my disk permissions using Disk Utility. Then I removed VMWare, Maide Connect, and a few other non-essential items from System Preferences > Users > Login Items. After a restart the freezing problems seems to have disappeared.
The problem isn't just confined to the MacBook Air. I have a 2011 MacBook Pro and I've had the problem since the first time I updated to a new OS from the original. The typing lag happens ALL THE TIME when I'm typing. It happens in Word, blogs, and even now as I'm typing this. Sometimes it is accompanied by the spinning beach ball. I've taken my laptop to the Apple geniuses twice and they have done lots of diagnostics and they can't fix the typing lag or the spinning beach balls when it's happening. Frankly, they say they don't know what is wrong with my MacBook Pro but it's very frustrating to pay so much for a laptop and have this problem. I hope someday they come up with a fix. By the way my husband has a 2013 MacBook Air and he doesn't have the typing lag at all.
MacBook Air Keyboard Input Lag
