kyawlin
Level 1 (18 points)

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

by kyawlin,Solvedanswer
kyawlin kyawlin
Level 1 (18 points)
A:

Yes thats true. I hope its something wrong with osx instead of out mac. If you guys find any solution. Pls let me know! Cheers!

Posted on Oct 25, 2013 7:30 AM

Close
kyawlin

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

  • All replies
  • Helpful answers

first Previous Page 59 of 199 last Next

  • by jcnba28,

    jcnba28 jcnba28 Oct 30, 2013 8:53 AM in response to kyawlin
    Level 1 (0 points)
    Oct 30, 2013 8:53 AM in response to kyawlin

    I haven't had a freeze for four days now but I am still getting multiple errors in the console. The most freiquent ones are:

     

    30/10/2013 15:48:33.000 kernel[0]: The USB device Apple Internal Keyboard / Trackpad (Port 5 of Hub at 0x14000000) may have caused a wake by issuing a remote wakeup (2)


    30/10/2013 15:49:30.080 Google Chrome Helper[3696]: Internals of CFAllocator not known; out-of-memory failures via CFAllocator will not result in termination. http://crbug.com/45650

    30/10/2013 15:51:30.289 iTunes[148]: tid:8657 - Can't handle disconnect with invalid ecid

    30/10/2013 15:50:58.174 com.apple.usbmuxd[47]: HandleDeviceAttachHelperCallback preflighting failed for WiFi device 0x116-fe80::1a:a75f:fea7:b343:0: 0xe8000084. Ignoring device.

    Is anyone else getting these same errors? If there is no update within the next few days I will be returning under the 14 days.

  • by mrakers85,

    mrakers85 mrakers85 Oct 30, 2013 8:59 AM in response to jcnba28
    Level 1 (0 points)
    Oct 30, 2013 8:59 AM in response to jcnba28

    The keyboard/mouse error is the recurring error.

  • by manomacas,

    manomacas manomacas Oct 30, 2013 9:00 AM in response to CarWei
    Level 1 (0 points)
    Oct 30, 2013 9:00 AM in response to CarWei

    Hi CarWei

    Build on My MacBook Pro (late 2008) is 13A603. As I mentioned before - no issues..I am (or was) going to buy a new Mac and before doing that i just checkt Google - "macbook pro haswel issue" without knowing about this particular issue..Thats the way I fould this thread. So I follow it hoping hoping that it will be solved very soon..

  • by jimmyhuangy,

    jimmyhuangy jimmyhuangy Oct 30, 2013 9:15 AM in response to kyawlin
    Level 1 (0 points)
    Oct 30, 2013 9:15 AM in response to kyawlin

    i got my macbook me865 this afternoon. After use 2 hour, show this issue, the same with everyone here, the trackpad and the keyboard freeze.

  • by Glenndisimo,

    Glenndisimo Glenndisimo Oct 30, 2013 9:15 AM in response to jcnba28
    Level 1 (10 points)
    Oct 30, 2013 9:15 AM in response to jcnba28

    jcnba, I have the same thing going on as you are experiencing. No freezes but constant logs in the console showing this error.

     

    So I don't think we should be all that worried, besides what guarantees you that your exchange model won't have the same issue?

     

    And there's no need to be worried at all since hardware problems are covered by your 1 year warranty and software issues will be most likely to get fixed in the upcoming updates.

  • by jcnba28,

    jcnba28 jcnba28 Oct 30, 2013 9:26 AM in response to Glenndisimo
    Level 1 (0 points)
    Oct 30, 2013 9:26 AM in response to Glenndisimo

    Glenndisimo, thanks for the response. If I return the Macbook I will not be exchanging it for a new one until the errors are resolved but I will wait til next week before I make my decision. Hopefully it is just a software issue and the update will be available soon.

  • by wwiii,

    wwiii wwiii Oct 30, 2013 9:30 AM in response to kyawlin
    Level 1 (0 points)
    Oct 30, 2013 9:30 AM in response to kyawlin

    My rMBP trackpad never worked from the moment I removed it from the box. I've mostly been able to navigate using the keyboard, though sometimes that also fails to respond. The trackpad is completely unusable.

  • by Oli.S72,

    Oli.S72 Oli.S72 Oct 30, 2013 9:35 AM in response to wwiii
    Level 1 (0 points)
    Oct 30, 2013 9:35 AM in response to wwiii

    wwiii wrote:

     

    My rMBP trackpad never worked from the moment I removed it from the box. I've mostly been able to navigate using the keyboard, though sometimes that also fails to respond. The trackpad is completely unusable.

    Well that is defenetly a hardware failure. I'd return this MBP right on the spot.

  • by KOBOC,

    KOBOC KOBOC Oct 30, 2013 9:40 AM in response to kyawlin
    Level 1 (0 points)
    Oct 30, 2013 9:40 AM in response to kyawlin

    Same Issue here.. Freezing of Keyboard and Trackpad on a brandnew Retina 13" :/ Very Apple unusal experience.. Is there any response from apple yet, whether this concerns a software issue? Because a update which fix that issue would be more than desirable..

  • by Oli.S72,

    Oli.S72 Oli.S72 Oct 30, 2013 9:52 AM in response to KOBOC
    Level 1 (0 points)
    Oct 30, 2013 9:52 AM in response to KOBOC

    KOBOC wrote:

     

    Same Issue here.. Freezing of Keyboard and Trackpad on a brandnew Retina 13" :/ Very Apple unusal experience.. Is there any response from apple yet, whether this concerns a software issue? Because a update which fix that issue would be more than desirable..

    No official statement from Apple yet.
    Many supporters from Apple say it's a software issue. Some still recommend to return it.

  • by binbashdevnull,

    binbashdevnull binbashdevnull Oct 30, 2013 9:56 AM in response to azbe
    Level 1 (0 points)
    Oct 30, 2013 9:56 AM in response to azbe

    azbe wrote:

     

    Would agree with that!

    Apple would not

  • by rebrose,

    rebrose rebrose Oct 30, 2013 9:57 AM in response to kyawlin
    Level 1 (0 points)
    Oct 30, 2013 9:57 AM in response to kyawlin

    Thanks Atterking for recommending this forum. Hope to hear some responses soon...

     

    Having the same issue here on my 2013 MBP 8gb.

  • by tisch,

    tisch tisch Oct 30, 2013 10:05 AM in response to kyawlin
    Level 1 (0 points)
    Oct 30, 2013 10:05 AM in response to kyawlin

    The fact that apple didn't responded yet can have several reasons. Let me guess:

     

    • Apple is hard at work at fixing the issue with an software update (I hope) and it will not be long until it is released. That could be the answer to why apple doesn't come up with a statement yet (We all know apples way to do statements are often just an software update).
    • Apple haven't figured out what exactly the problem is (very unlikly but possible ;-)).

     

    So keep calm. Return your device if you are not satisfied. I also want to point out that we all are early adopters and with EVERY product on the earth there is a potential probability that not all things will went well.

     

    And yes I wish also that apple should announce SOMETHING.

  • by iDevelope,

    iDevelope iDevelope Oct 30, 2013 10:07 AM in response to kyawlin
    Level 1 (0 points)
    Oct 30, 2013 10:07 AM in response to kyawlin

    I have MacBook Pro (early 2008) Core Duo 2, 160 GB HD, 4G RAM 15''. I've updated to Mavericks last weak and I started to encounter FREEZING. It's very annoying.

     

    I have done the following with no luck:

     

    - PRAM resetting.

    - verify Disk Permission and Repairing.

     

    We want a quick solution.

  • by mfnyc,

    mfnyc mfnyc Oct 30, 2013 10:09 AM in response to kyawlin
    Level 1 (0 points)
    Oct 30, 2013 10:09 AM in response to kyawlin

    The trackpad wake thing a lot of you are writing about may not be an error at all unless it’s actually in an error log. Think of a counter counting down the computer to sleep mode and when you don’t touch anything for a while a counter is starting counting down so when you then touch your trackpad or keyboard it sends a wake call to reset the counter. Short explanation because it’s more to it in reality but hope you get the point and that’s also why the messages stops when you have something else preventing/delaying the countdown like a usb drive. If you have something usb-connected long enough there will be new wake calls. That said, It may still be part of the overall problem but not by itself, check an older computer with Mountain Lion and you will see exactly the same wake texts in the console.

first Previous Page 59 of 199 last Next