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

does the terminal still show the usb keyboard/trackpad errors when caffeine is on?

I would check this myself, but i am holding off on buying the new rMBP 13in until this issue is fixed, just in case. I can live with other small glitches being fixed in the coming weeks, but the keyboard and trackpad are pretty essential for a laptop ;p

i don't think that 12 hours are enough... Nobody can tell how much time is enough because it happens in "Rare Cirmumstances"

For example my rMBP locked during second day and after i reinstalled Mavericks and now 8 days without freezing but i have a lot of error logs... and I know that it could happen again...

Something to try.

I haven't had a freeze in 6 days with no USB devices connected, this is what I did:

Boot into the Safe Mode by booting while the Shift key is pressed.

After the Safe Mode completes booting, reboot normally.

DSL_Steve,

Do you still get the error message in the kernel log after your Safe Mode Boot?

Thanks,

idark77,

Do you still get error logs when your computer is asleep? If so, has it had impact on your battery life?

I haven't experienced any freezes, but the error logs keep going after I close the lid on my computer and it drains my battery very quickly.

Thank,

EsKlar wrote:

 

DSL_Steve,

 

Do you still get the error message in the kernel log after your Safe Mode Boot?

 

Thanks,

Yes.

But it is MHO that 'the' error messages are not related to the malfunction.

No abnormal batery life either.

idark77 wrote:

 

i don't think that 12 hours are enough... Nobody can tell how much time is enough because it happens in "Rare Cirmumstances"

 

For example my rMBP locked during second day and after i reinstalled Mavericks and now 8 days without freezing but i have a lot of error logs... and I know that it could happen again...

Well at least for me the circumstances haven't been rare at all. Maybe it's because I spend a lot of hours in front of my macbook every day but this happens at least twice per day for me. If it would not occur for 24 hours, I would consider it fixed for now. We'll see...

Caffeine doesn't fix the error.

They may be linked to insomnia issues?  I have more concern when I type "leak" into the Console search field and read the programmer's comments!

Kimeechi wrote:

 

does the terminal still show the usb keyboard/trackpad errors when caffeine is on?

I would check this myself, but i am holding off on buying the new rMBP 13in until this issue is fixed, just in case. I can live with other small glitches being fixed in the coming weeks, but the keyboard and trackpad are pretty essential for a laptop ;p

Yes, the message is still there, every minute or so.

But I'm not sure yet how the freeze issue relates to the message in the log: the system does not freeze every time that the message is displayed in the log. Maybe that means that only people who see that message in the logs will experience the freeze BUT if the message is visible in the log files, it doesn't necessarily mean that a freeze will follow? I guess I'll just have to wait and find out.

Kimeechi wrote:

but the keyboard and trackpad are pretty essential for a laptop ;p

yup, it's one of those little details that you suddenly miss a lot when they are taken away. but hey, the power off button still works just fine!

DSL_Steve wrote:

 

EsKlar wrote:

 

DSL_Steve,

 

Do you still get the error message in the kernel log after your Safe Mode Boot?

 

Thanks,

Yes.

 

But it is MHO that 'the' error messages are not related to the malfunction.

Most people think they are related.

Plugging in an USB device, the freezes stop. And nor more messages from the kernel. Unplug the USB device and you have freezes and the messages again.

The freezes seem to be related to some sleep mode. The kernel message says, keyboard or touchpad has woken (parts of) the kernel from that sleep mode. Sometimes, this might simply fail.

btw: rebooting into safe mode was tested by others before as well. For them, it didn't work.

EsKlar wrote:

 

idark77,

 

Do you still get error logs when your computer is asleep? If so, has it had impact on your battery life?

 

I haven't experienced any freezes, but the error logs keep going after I close the lid on my computer and it drains my battery very quickly.

 

Thank,

No when i close the lid the laptop sleeps and i have no error logs. Have you Power Snap enabled with battery ?

@ carina123

My 2010 MBP (non-retina) running Mavericks also shows 3 of the exact same trackpad keyboard messages in 'Console', it shoes them each day as the older ones drop off the newer ones appear. However my keyboard and trackpad doesn't freeze like on the late 2013 13" rMBP.

Pont being that these console messages seem to be widespread in Mavericks beyond just the late 13" rMBP however assuming these console messages are related to the keyboard and trackpad freeze-up problem, then the console messages only affect the late 13" rMBP in that particular way.

Not sure if that is of any interest or help but I felt obliged to say it anyway

Just chiming in with exact same issue and console messages on 13" Haswell.  Raced to the Apple store the day the new MB w Retina's arrived and for my fan boy mental breakdown of buying into v1.0 I have experienced freeze every hour or so since.

Reboot w power off seemd only option but then found closing lid for a few minutes would often do the tirck too.

Apple Care yesterday on the phone dude had me reinstall Mavericks (command + R on reboot + 3hours) and now it freezes a lot less... but it still freezes.  Apple Care seemed surprised and this problem was 'news to him' and he suggested I might have to go back to the store for them to look at it in person. For what... other than wasting my time.. I do not know because this ain't getting fixed till Apple issues an update.  I'll probably be making noise about my money back and returning the unit if it isn't fixed before too much longer.

I've had the new 13"/256/8 model for over a week now, and the problem has so far only happened once, on the second day.  I do get the console messages constantly about remote wakeup as well.

Having been an early adopter of various Android and Windows releases, I have to say this doesn't bother me much.  I'm sure the fix won't take too long...