kyawlin

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

Hello Everyone.

 

I have just got my new macbook pro retina 13 Haswell (October Model). This is my second day of usage and i have encountered sudden system freeze for 2 times already. The keyboard and the trackpad stops working including brigtness keys and volume control keys. i have use apple hardware test but no problem are found.

 

 

Could anyone tell  me what is going on or having the same issue?

MacBook Pro with Retina display, OS X Mavericks (10.9)

Posted on Oct 25, 2013 5:56 AM

Close

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

  • All replies
  • Helpful answers

first Previous Page 140 of 199 last Next
  • by xuhaotian,

    xuhaotian xuhaotian Nov 7, 2013 4:31 PM in response to kyawlin
    Level 1 (0 points)
    Nov 7, 2013 4:31 PM in response to kyawlin

    so happy Apple released a fix and hope it will solve the problem!

     

    happy I kept it

  • by lifesaver101,

    lifesaver101 lifesaver101 Nov 7, 2013 4:55 PM in response to kyawlin
    Level 1 (0 points)
    Nov 7, 2013 4:55 PM in response to kyawlin

    Finally the fix arrived! Hurray! :-)

  • by EsKlar,

    EsKlar EsKlar Nov 7, 2013 5:13 PM in response to Supreem
    Level 1 (0 points)
    Nov 7, 2013 5:13 PM in response to Supreem

    Hey everyone,

     

    I originally had bought a 13inch 2.6 i5/8gig/256 and exchanged it to a new 15inch baseline model instead and have been using it for a few days.

     

    I can absolutely confirm that my 15inch model does not have the log message that shows up in the 13inch. The only time that the 13inch did not have the log message was after I left a USB flash drive plugged in.

     

    This makes me wonder about a few things.

     

    1. Is the Mavericks build in the 13inch interacting with the keyboard/trackpad differently than the 15inch?

     

    2. If Mavericks is suppose to handle the keyboard/trackpad the same way in both the 15inch and 13inch, then did the newly release patch actually fix the root of the problem, if the same log message is still showing up?

     

    3. Could Apple only have masked the freeze issue, but the root software/hardware issue is still present?

     

    4. How will the new patch release impact overall system performance on the 13inch

     

    Just some thoughts.....

     

    Either way, congrats on a functioning Macbook Pro 13inch! Cheers.

  • by Oli.S72,

    Oli.S72 Oli.S72 Nov 7, 2013 5:19 PM in response to kyawlin
    Level 1 (0 points)
    Nov 7, 2013 5:19 PM in response to kyawlin

    Happy to hear the fix is out. My guess that this will happen until Friday at the latest was not too bad after all.

     

    We have an EFI update. So an update of the piece of code that is between hardware and the operating system. Looks a lot like the guesses have been right and some boundarys had been overstepped. Probably a timing in interrupts or something alike. No "broken" hardware, sorry to the trolls from Redmond or wherever you are from.

    Will the freezes stop now, after applying the EFI update?  I would bet my house, my car and my yacht on this.
    The errors still show up? They are no errors, as mentioned before. They are messages from the kernel. They are set to the lowest priority. They are like your neighbour - giving you plenty of information that is not really interesting and for sure not important at all. But also they don't hurt. Just ignore them.Have fun using your device the way it's supposed to be.

     

    I sure hope that Apple will do better next time. This was really bad quality checking. Worse than bad. In my opinion, some people should get fired now. There is no excuse for something like this.

     

    Update the EFI and relax. Your new 13 inch Haswell MacBook Pro is finally doing what it was supposed to be from the beginning: it works.

  • by chkamran,

    chkamran chkamran Nov 7, 2013 5:19 PM in response to xuhaotian
    Level 1 (0 points)
    Nov 7, 2013 5:19 PM in response to xuhaotian

    I was about to return mine. I hope they didn't just mask the problem. It is working as expected so I think I'll keep mine too.

  • by Oli.S72,

    Oli.S72 Oli.S72 Nov 7, 2013 5:36 PM in response to EsKlar
    Level 1 (0 points)
    Nov 7, 2013 5:36 PM in response to EsKlar

    EsKlar wrote:

     

     

    1. Is the Mavericks build in the 13inch interacting with the keyboard/trackpad differently than the 15inch?

     

    2. If Mavericks is suppose to handle the keyboard/trackpad the same way in both the 15inch and 13inch, then did the newly release patch actually fix the root of the problem, if the same log message is still showing up?

     

    3. Could Apple only have masked the freeze issue, but the root software/hardware issue is still present?

     

    4. How will the new patch release impact overall system performance on the 13inch

    1. it has a different EFI. Some parts of the hardware are different, like the mainboard, etc. so it has to be a individual EFI. Interaction should be about the same.

     

    2. If you code an operating system or a driver, you can decide, what to log and what not to log. Apple decided on build 13A2093 to log those kernel messages more than on other builds. I have no clue, why, to be honest.

     

    3. What is the difference between a mask and a patch? As someone else mentioned before: the complex hardware of a modern computer is full of "issues" - and the operating systems and drivers are full of code to mask/patch/fix those issues. Again: this is not "broken hardware".

     

    I try to give you an easy example: You develop a software to calculate the average gas consumption of a car. Your piece of code is set to figure between 5 and 10 liters per 100 kilometers.
    Now, on a special day, you have massive traffic and guess what, the car needs 11 liters.
    Is your car broken? No. Is your software broken? No. It is simply a circumstance that has happened which you didn't think of, when you wrote your code.

     

    4. My guess: you will not notice any difference. Both keyboard and touchpad and even the USB hub take so little power (both electrical power from the battery and also CPU power) that I don'T think it will have any effect.

  • by TessaK9,

    TessaK9 TessaK9 Nov 7, 2013 5:35 PM in response to kyawlin
    Level 1 (0 points)
    Nov 7, 2013 5:35 PM in response to kyawlin

    Been using mine for a few hours since the update and all is well so far. Battery life is the same. No change in performance from what I can see. In fact, trackpad response seems better to me and it was already pretty damned good before.

  • by sTronic,

    sTronic sTronic Nov 7, 2013 5:37 PM in response to Oli.S72
    Level 1 (0 points)
    Nov 7, 2013 5:37 PM in response to Oli.S72

    @Oli.S72,

     

    basically you are bullsh*ting people.

     

    The log message can not be ignored, this message doesn't happy to any other apple device, at least no other user complains for this kind of message keep poping up. There is NO reason for 13 inch to be so special to have this message keep poping up!! NO! the only reason is, there is something wrong with this machine.

     

    Plus, the log message is gone when USB device is pluged in!! that means. the log is not telling you someone touched the trackpad and try to wake up, otherwiese with a USB pluged in, it should still show up, but why not??? THis is so strange plus the keyboard/trackpad locking up happend, you can imagine the whole thing is not that simple.

     

    I have speak to the senior advisor from Apple Australia 5 minute ago. what he said, looking carefully below:

    1. EFI update is attempt to fix that message as well, it should no longer appear.

    2. The EFI update is tried to solve the prolbem on software side, to make a workaround.

     

    With those two points, its extremely clear, that error message shouldn't be there and one more thing:

    1. when i asked him is this a hardware issue, he slicent for few second and said: I can't say anything at this point, but there is something wrong with your MBP, bring it back to the apple store.

     

    So.. Oli.S72, you should keep your mount shut, stop sending wrong information and try to comfort everyone.

     

    The EFI is not fixing the root problem and just mask the problem and it could end up with shorter battery life.

     

    Everyone should return their 13 inch macbook Pro. they all faulty at this stage, until they run out, buy a new one. There are nothing special for the 13 inch, not because the special build or anything, it just a fualty machine.

     

    I am going to meet the store guy tomorrow and question them, will keep you guys updated.

     

    If you are nearly the end of 14 days, do not think, return it immediately, the one you have, is 100% has fault in it.

  • by Supreem,

    Supreem Supreem Nov 7, 2013 5:49 PM in response to sTronic
    Level 1 (5 points)
    Nov 7, 2013 5:49 PM in response to sTronic

    I hear what you're saying and I'm relatively neutral to the debate at hand as I don't have the new 13" rMBP yet as I'm waiting for mine to be delivered, however the one thing I can say is that I am currently on a Mid 2010 MBP 13" and I see 3 of those exact same console logs for the trackpad and keyboard and the Mavericks build number on this 2010 machine is the same as the Mavericks build number on the the Late 2013 rMBP 13" so could those log messages not simply be to do with Mavericks build 13A603?

  • by Sledgenet,

    Sledgenet Sledgenet Nov 7, 2013 5:45 PM in response to EsKlar
    Level 1 (0 points)
    Nov 7, 2013 5:45 PM in response to EsKlar

    This is almost certainly tangental but I thought it might be worth downloading Mavericks from the AppStore (partly for curiosity, partly for the extra protection of having one more place to reinstall it from), which tells me... "OSX Mavericks cannot be installed on this computer"!

     

    I dunno if that's just badly phrased (maybe it can't be reinstalled right now over the top of an existing installation?) or why it assumes I want to install it rather than stow the installer, but it's almost as if there's something peculiar about the 13" models and their particular build of Mavs...

  • by Potatohead_33,

    Potatohead_33 Potatohead_33 Nov 7, 2013 5:49 PM in response to xuhaotian
    Level 1 (0 points)
    Nov 7, 2013 5:49 PM in response to xuhaotian

    I am getting about 40 - 50% more battery life after update now too. I show 95% remaining which says 13:17 remaining. Wow.

  • by sTronic,

    sTronic sTronic Nov 7, 2013 6:05 PM in response to Potatohead_33
    Level 1 (0 points)
    Nov 7, 2013 6:05 PM in response to Potatohead_33

    getting 40-50% is impossible mate, its an error estimated time after update.

  • by EsKlar,

    EsKlar EsKlar Nov 7, 2013 6:06 PM in response to Oli.S72
    Level 1 (0 points)
    Nov 7, 2013 6:06 PM in response to Oli.S72

    Oli,

     

    Thanks for your thoughtful response. I do have one nagging question, and it looks like sTronic beat me to the punch in asking it.

     

    How come when you leave a USB drive in the 13inch, the log message suddenly disappears? It all of a sudden starts to look exactly like the kernel log in the 15inch.

  • by PieceOfChum,

    PieceOfChum PieceOfChum Nov 7, 2013 6:11 PM in response to EsKlar
    Level 1 (0 points)
    Nov 7, 2013 6:11 PM in response to EsKlar

    I updated my Macbook 13 Haswell and still see the "USB device Apple Internal Keyboard / Trackpad (Port 5 of Hub at 0x14000000) may have caused a wake by issuing a remote wakeup (2)" message.

  • by lib8,

    lib8 lib8 Nov 7, 2013 6:14 PM in response to kyawlin
    Level 1 (0 points)
    Nov 7, 2013 6:14 PM in response to kyawlin

    Just updated mine. I'm still a little confused. So previously I had 2 freezes in 13 days of use. Even though I havent experienced a freeze yet in the last couple of hours, I didn't for the past 6 days prior to the update.

     

    How would I know that it's fixed now if the error messages are appearing exactly as it did before? I know some of you said that this is no longer an "error" but just a notification....how would I be able to distinguish between the two?

first Previous Page 140 of 199 last Next