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

idelaviuda wrote:

 

As I previously reported I have the same issue with my rMBP 13" as all late 2013 owners. Tody I have visited the Apple Store located in Majadahonda/Madrid/Spain  Entered into console in 3 rMBP 13". All consoles reported the dreaded error.  Repeated procedure with several rMBP 15" and with a couple non retina's. No errors there. FYI.

Yeah man, my money is firmly on the fact that this specific issue affects every late 2013 Haswell 13" MBP and ONLY them models.

They'll either have to issue a proper fix which can be downloaded to your MBP real soon or if that's not possible then do a total recall and start all over again.

Hopefully the words 'product testing' will be remembered well for future releases.

I too am having the same issue. I spoke to my friends with rMBPs that were non-Haswell, and it seems I am the only one with the issue.

Hoping Apple fixes this problem, it is begining to feel like this is just a cheap dell, with the number of random freezes.

Got my new 13" MBP today. So far no issues, but I am going to use the computer native for a while before installing anything. There are several AppStore updates waiting including a system update which states nothing interesting to update, but that does not mean Apple is not updating other things besides what is stated. Out of the box build is 13A2093.

The wake errors are occuring in the log, but they really appear to be benign. If you create a query in the console just on those errors you will see that they only occur when you touch the trackpad or keyboard. It is a common occurrence for an interrupt to generate when that happens and the system is reporting it occurred. That by itself should not be related to the error unresponsiveness error at all. Not clear why those errors stop occuring though if you plug in a USB device. That piece does not make sense.

The various pace at which the unresponsive is reported is interesting. It would be interesting to note any sequence of steps anyone on this thread can remember prior to the keyboard/trackpad freeze occurring. There are many that made it many days without the error and some who had the error within hours of opening the device. If anyone can recall what was installed, changed on the system it may help identify pattern for this issue to occur.

I've kept an eye on this disscussion for the last week or so.

I originally posted when the issues emerged shortly after launch, since then I have returned my rMBP 13.3 8GB 256SSD. Due to the store being out of stock I reordered from the Apple store online, and recieved my new machine today. It's shipped all the way from China, so most likely would not have been part of the inital batches.

I've only been using it for a few hours, the same error message is appearing in the console. Its running OS X 10.9 13A2093.

So far no freezes - will update in a couple of days.

Unfortunately,I have encountered the freeze keyboard and touchpad issue today.

Now I change to used my windows laptop for working.

Late 2013, 2.4Ghz, 8g ram, 256g ssd model.

I removed my wireless mouse receiver from the USB port and later, the issue occurred.

I don't get why people are still complaining. I know It's extremely aggravating, I can imagine, but Apple did said they were working on an update to resolve this issue. There's really no need to keep repeating over and over how their new 13-inch Haswell MacBook Pro has this issue. Everybody has it.

I'm waiting to purchase this when Apple has resolved this issue.

bcozd wrote:

 

It is a common occurrence for an interrupt to generate when that happens and the system is reporting it occurred. That by itself should not be related to the error unresponsiveness error at all.

I could reproduce the occurance of the entry in the system.log

(if you open a terminal in the background and do a tail -f /var/log/system.log you can watch very nicely what happens)

It only shows up when you use the keyboard or touchpad after not using one of them for a couple of seconds and then using it again.

So here’s my best guess:

After a specific amount of time (5 seconds seems a quite close figure from my tests) »something that has to do with the USB Hub« (meaning some parts of the hardware) is put into an  sleep mode. As we know, Mavericks is trying to get the max out of power saving.

Now if you touch keyboard or touchpad after these 5 seconds, the system gets a »wake up call«.

This is what the kernel reports. »kernel[0]: Hey guys, guess what, parts of me just woke up. The USB device Apple Internal Keyboard / Touchpad may have caused this by issuing a remote wakup. Or something else happend. I don't know.«

And now something more: I personally experienced my freezes only in situations when I did not use keyboard and touchpad for quite a few seconds (happened only 2 times to me, so I remember)

This leeds me to my guess: sometimes (in the from Apple mentioned rare circumstances) the wakup-call simply fails. Parts of the system are sleeping too deeply to hear the keyboard/Tochpad knocking on the door, so to speak.

Under which circumstances this glitch happens is unknown of course. But it leads me more into the direction to say: this is 100% a software problem. (Software as in »not-hardware«)

Some even more guesses: The system knows, whether a USB device is plugged in. If so, the system does not put the USB hub to sleep. Because the USB device could have a problem with this. But if no USB device is present, the HUB (or something else that is connected to this topic) is put to sleep after 5 seconds.
This would explain perfectly why plugging in an USB device stops the freezing.

Amazing analysis man!

I returned my new but affected (freezing) MBP (which I received from China 8 days ago) and purchased a new one (at the Apple store) and upgraded the SSD to 512 from 256 and went from 2.4 to 2.6. The rest is the same...13, 8G.

As soon as I updated the software for my apps the machine froze. Same issue with this second MBP.

I'm a Mac novice, but the analysis just offered by Oli.S72 seems persuasive to me - and gives me hope that the fix will be straightforward enough.

Can I ask - are you keeping your machine for the time being then?

other bugs i noticed with my haswell 13":

takes about 10 seconds to open my hd macintosh data in finder (normal in mac os ? i am new to this.)

my screen started dimming to the absolute minimum. the daylight changed a little at that moment but no reason to go to the minimum.

my battery time indicator shows me sometimes 12 hour left then 5 hours at the quite same battery level. is my mac recording my typing and working frequenz ? when i read this thread and do not work a lot the battery level increases extremely. could be normal and a good feature ...

back to the urgent problem: since i got usb mouse connected i never had a single freeze. no error logs or other problems. the graphic glitches is have seen for a few times never happend again.

and i noticed one thing that make me smile: there are endless people reporting problems with mavericks with all kind of systems, macbooks old and new, imac, macbook air ...

it has to be mavericks.

and thx again oli

There are 87 pages of people saying the exact same thing over and over. It's repetitave and annoying. Your situation is no different than everyone else who has this.

People are worried they've made an expensive investment, sometimes the first time in apple and OSX, people are just worried and need reassuring that their money hasnt gone to waste. Plus the more people that have the issue the more likely it is that apple will release the fix or at least physically do something sooner.

Actually, what you are saying is somewhat annoying; let the man share if he wants. I'm all for creating a clamour - might, just might, make Apple work faster.

Brilliant.

Which also would beg to question: in QC, if they are active on the computer, then it may have masked the issue because I removed my USB and checked and it is a 4 second deal for me. I couldn't get the error message for anything less than 4 seconds.

Likewise, I don't know how they do QC, but is it possible that the machines that they are testing are plugged in via USB to something for recording or whatnot? Again, I have no clue, but right now, we're all playing the speculative game anyways.

If nothing else, I've learned a lot about my new MBP this week....