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

redrocket11 wrote:

 

Can someone who had the freeze problem with the keyboard and the trackpad on how MacBook pro retina 13"  tell me if after the apples update the problem is fixed . I don't want to risk buying something that is not worth it

So you're certainly not a risk taker in life huh, what do you think would happen if you get an MBP with a problem? Apple will just point and laugh at you? Come on man...

The sheer lack of activity on this thread (compared to before the firmware update was released) should answer your question perfectly.

If you want a 13" rMBP then just grow a backbone and buy one, like the rest of us did.

I am still having the Freeze problem with the keyboard and the trackpad after Apple's update.

syntactic wrote:

 

I am still having the Freeze problem with the keyboard and the trackpad after Apple's update.

So then go and tell Apple and have them replace your machine for a new one, if you're still having the freeze up problem post-update then they have no choice other than to replace your machine, and they will.

I already replaced my machine for a new one. This is replacement machine #2. At this point I'd just like my money back.

Ok,

Doing some more research into the issue. This only happens when vmWare Fusion 6 is running - and my Windows 7 Virtual machine is powered on. In fact, I am able to reproduce the issue quite effectively. I did switch to OmniGraffle (not Pro) and it is working great for me. Thanks.

When I have fusion and the Windows VM Running, if I quickly connect and disconnect the USB keyboard and mouse (it happens both with a Dell Wired Keyboard and mouse, and with a Microsoft Wireless keyboard and mouse) then my built-in trackpad and keyboard freeze. The USB keyboard works fine, the mac is operational and I can use it for days - only caveat, I cant use it without the external keyboard and mouse. The built in trackpad and keyboard are dead. I think It could be the USB Hub, ut doubt it. I am using a IOGEAR MiniHub 4-port USB 2.0 Hub. I will go out and buy a USB3.0 Hub and try to repeat this experiment.

With Microsoft Wireless Keyboard/Mouse:

1/13/14 9:07:59.000 AM kernel[0]: AppleUSBMultitouchDriver::_deviceSetReport - DeviceRequest for reportID 0xac returned with result 0xe0004051 - retrying

1/13/14 9:07:59.000 AM kernel[0]: AppleUSBMultitouchDriver::_deviceSetReport - DeviceRequest for reportID 0xac returned with result 0xe000404f - retrying

1/13/14 9:07:59.000 AM kernel[0]: AppleUSBMultitouchDriver::_deviceSetReport - DeviceRequest for reportID 0xac returned with result 0xe000404f - retrying

1/13/14 9:07:59.000 AM kernel[0]: AppleUSBMultitouchDriver::_deviceSetReport - DeviceRequest returned error 0xe000404f (interface 1, reportID 0xac, payload 2

1/13/14 9:07:59.000 AM kernel[0]: AppleUSBMultitouchDebug: _deviceSetReport returned an error in configureDataMode

1/13/14 9:07:59.000 AM kernel[0]: AppleUSBMultitouchDriver::_deviceSetReport - DeviceRequest for reportID 0xac returned with result 0xe000404f - retrying

1/13/14 9:07:59.000 AM kernel[0]: AppleUSBMultitouchDriver::_deviceSetReport - DeviceRequest for reportID 0xac returned with result 0xe000404f - retrying

1/13/14 9:07:59.000 AM kernel[0]: AppleUSBMultitouchDriver::_deviceSetReport - DeviceRequest returned error 0xe000404f (interface 1, reportID 0xac, payload 2

1/13/14 9:07:59.000 AM kernel[0]: AppleUSBMultitouchDebug: _deviceSetReport returned an error in configureDataMode

With Dell Wired Keyboard and Mouse:

1/13/14 9:54:26.000 AM kernel[0]: AppleUSBMultitouchDriver::_deviceSetReport - DeviceRequest for reportID 0xac returned with result 0xe0004051 - retrying

1/13/14 9:54:26.000 AM kernel[0]: AppleUSBMultitouchDriver::_deviceSetReport - DeviceRequest for reportID 0xac returned with result 0xe000404f - retrying

1/13/14 9:54:26.000 AM kernel[0]: AppleUSBMultitouchDriver::_deviceSetReport - DeviceRequest for reportID 0xac returned with result 0xe000404f - retrying

1/13/14 9:54:26.000 AM kernel[0]: AppleUSBMultitouchDriver::_deviceSetReport - DeviceRequest returned error 0xe000404f (interface 1, reportID 0xac, payload 2

1/13/14 9:54:26.000 AM kernel[0]: AppleUSBMultitouchDebug: _deviceSetReport returned an error in configureDataMode

1/13/14 9:54:26.000 AM kernel[0]: AppleUSBMultitouchDriver::_deviceSetReport - DeviceRequest for reportID 0xac returned with result 0xe000404f - retrying

1/13/14 9:54:26.000 AM kernel[0]: AppleUSBMultitouchDriver::_deviceSetReport - DeviceRequest for reportID 0xac returned with result 0xe000404f - retrying

1/13/14 9:54:26.000 AM kernel[0]: AppleUSBMultitouchDriver::_deviceSetReport - DeviceRequest returned error 0xe000404f (interface 1, reportID 0xac, payload 2

1/13/14 9:54:26.000 AM kernel[0]: AppleUSBMultitouchDebug: _deviceSetReport returned an error in configureDataMode

I Shut down VMware fusion completely and tried to connect and disconnect the USB Hub hundreds of times... worked with no issues. So Fusion seems to be the culprit. Not sure if Apple can do anything here... thoughts?

I will test with a different USB hub and post back if I find anything different. For now, it is a fusion issue.

No need to be ironic. And yes I am not a risk taker, I prefer to make  decisions based on facts.

If I were Supreem, I wouldn't have even bothered to reply to your post.

If you were unable to form an opinion based on the 179 pages of posts in this thread, then...

Well it looks like after replacement # 2 this track pad Keyboard issue is STILL happening. I see no reason why this would stop happening at this point and the MacBook must be returned..

For anyone reading this thread that was thinking about getting a rMBP HasWell Build... Stay Away and try to find yourself an IvyBridge Model. Not his one, as it will chronically give you issues.

P.s This was after the EFI update was preinstalled by apple, and judging my their response to the troubleshooting steps conducted its all pointed to the hardware.

I would stay clear of the Haswell builds

I've owned the Haswell 13-inch MacBook Pro for 3 weeks now. This model came pre-installed with the EFI update. I don't use a USB mouse, and I rarely have any USB flash drives plugged in. I'm constantly on it and I have to say, I've never once experience any issues with freezing of the trackpad/keyboard. I first bought the 13-inch Haswell MacBook Pro back in November, but then returned it because I wanted the 2.6GHz,512GB model rather than the 2.4GHz,256GB model which I had. I've owned that one for 1 month before returning it to BestBuy (because of the extended Holiday return policy, I was able to do that). I've never had a problem once with that one either.

I seriously don't know if some of you are bullsh*tting on here or what, but there is nothing wrong with these models. Most people, including myself, are very happy with them.

The only problem is that there will sometimes be horizontal white lines across the screen. This is very rare, and I've never had screen burn-in either. The messages in the Console are not a big deal. People need to stop complaining about that. If Apple hasn't addressed that as being a serious issue, than forget about it. Obviously, It isn't anything serious.

i have the 15 inch MBP retina, haswell... same issue!!!! but i only experience it when i use USB devices, like the other 199 of you guys have posted....

i guess we just have to sit and wait...... and waiiit.... and wait. hopefully before this year is over, i won't be afraid of leaving my usb wireless mouse dongle in overnight.

Sorry that is incorrect.

That seems to be the culprit. USB powered devices such as the ones mentioned in this thread. Mine in particular is an external MIDI controller/external HDD that causes the unresponsiveness on a chronic level. Interesting enough this only happens after the sleep/wake function is issued after a remote wake.

I have been visiting this thread for a long time and finally decided to share my experience since I can see a lot of speculations about the cause of this problem.

I bought my MBP Retina Haswell at the beginning of December (after returning two different Samsung machines, by the way...). Here is the important part: it became unresponsive the very first time I turned it on, while creating a user account. It, however, did not have the EFI update preinstalled back then. But still, I believe that this rules out all kinds of mentioned causes like Chrome, USB devices, etc.

After installing the EFI update it took two weeks until it became unresponsive again (while doing nothing unusual, just browsing). Then I returned it and now I keep reading this thread, waiting for the solution to appear. So, unfortunately, those who feels safe after using their MBPr for several weeks without any problems, one day might be surprised.

I'm in direct contact with a senior support analyst, and we are actively troubleshooting these issues.