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 94 of 199 last Next
  • by mrakers85,

    mrakers85 mrakers85 Nov 1, 2013 9:06 PM in response to Potatohead_33
    Level 1 (0 points)
    Nov 1, 2013 9:06 PM in response to Potatohead_33

    Plug in a USB flash drive and it will cease lock ups. Been plugged in for 4 days with no lock ups. Ends the errors found in the console as well.

     

    As for everyone freaking out over what so and so said at which store - nothing is official. If you want to return, that's great. You are free to do so. But remember, nothing is definitive. From IT folks online, it points to a software issue, not a hardware issue.

     

    Remember: a USB plugged in ceases the problem (which would not indicate a hardware problem).

     

    This is unique to the 13 inch MBP, so it is not the Haswell issue, plus the Haswell issue would not lead to this problem.

     

    It is wide spread - not unique to just a few MacBooks.

     

    Go back and look at what Oli.S72 has said throughout the thread - great points and thoughts from someone who knows a lot more than the average person.

  • by dmndkut,

    dmndkut dmndkut Nov 1, 2013 9:07 PM in response to kyawlin
    Level 1 (0 points)
    Nov 1, 2013 9:07 PM in response to kyawlin

    My logs are full of " The USB device Apple Internal Keyboard / Trackpad (Port 5 of Hub at 0x14000000) may have caused a wake by issuing a remote wakeup (2)" So i'm sure this has something to do with it, which makes me think it is software.

  • by Potatohead_33,

    Potatohead_33 Potatohead_33 Nov 1, 2013 9:08 PM in response to dmndkut
    Level 1 (0 points)
    Nov 1, 2013 9:08 PM in response to dmndkut

    One thing is for sure, if Apple doesn't say something soon there are going to be a million refurbs for sale shortly from people returning machines.

  • by dmndkut,

    dmndkut dmndkut Nov 1, 2013 9:13 PM in response to Potatohead_33
    Level 1 (0 points)
    Nov 1, 2013 9:13 PM in response to Potatohead_33

    Exactly, I just wish they would address the issue. They clearly see the 94 pages on this discussion.

  • by Potatohead_33,

    Potatohead_33 Potatohead_33 Nov 1, 2013 9:14 PM in response to dmndkut
    Level 1 (0 points)
    Nov 1, 2013 9:14 PM in response to dmndkut

    dmndkut, I have the same logs in mine. It seems this is likely the problem.

  • by buyspaul,

    buyspaul buyspaul Nov 1, 2013 9:25 PM in response to Oli.S72
    Level 1 (0 points)
    Nov 1, 2013 9:25 PM in response to Oli.S72

    The apple genius didn't want me to have a subpar experience so he advised me to return it.

    Nothing dramatic except for the way you interpreted my comments.

  • by 135F2l,

    135F2l 135F2l Nov 1, 2013 10:30 PM in response to kyawlin
    Level 1 (0 points)
    Nov 1, 2013 10:30 PM in response to kyawlin

    Hey guys,I may have found something new.(I'm not sure whether other guys have already mentioned it.)

    Here it is,I use a Magic Mouse from my old iMac instead of plug in ANY usb device, just as the usual way I use the Mac.And NO error log in the console, and NO freeze any more, at least for the recent hours.

    To me, that will be a perfect way to fix/avoid this issue, because I needn't to do anything that is unnecessary.

    I'm not sure whether other brand of bluetooth/wireless mouse would work.

     

    BTW,my model is 13" i5 2.6Ghz/16GB/512GB, with the build number of 13A2093.

    Hope it helps.

  • by idelaviuda,

    idelaviuda idelaviuda Nov 1, 2013 11:12 PM in response to 135F2l
    Level 1 (0 points)
    Nov 1, 2013 11:12 PM in response to 135F2l

    Hi 135F2I. In the same boat here. Yes, your experience has been shared a couple of times. My error logs also do appear to stop after connecting Apple's Magic Mouse. But come back as soon as it is turned of or disconnected.

     

    I'm just half way through the 14 days no-hassle return period. Countdown started.

  • by Artyom Devyatov,

    Artyom Devyatov Artyom Devyatov Nov 1, 2013 11:50 PM in response to Oli.S72
    Level 1 (0 points)
    Nov 1, 2013 11:50 PM in response to Oli.S72

    New MacBook Pro affected by this c1 bug?

  • by glgerard,

    glgerard glgerard Nov 2, 2013 12:26 AM in response to kyawlin
    Level 1 (0 points)
    Nov 2, 2013 12:26 AM in response to kyawlin

    I am also having the same exact freeze issue on my Late 2013 MBP 13. When I connect a USB2 thumb drive the console error messages go away and no more freezes. It seems that having a bluetooth connected mouse also solves the problem but I have to test it for a bit longer (I generally use the trackpad).

     

    Just to share the outcome of an unsuccessful attempt I also tried to copy over the AppleUSBMultiTouch.kext extension under /System/Library/Extensions of an MBA 13 running 10.9 (the different build as we all know by now) to the MBP 13 because I noticed the two extensions had a different revision number (I did run kextstat on both). Well, don't bother, as expected the MBA version didn't work on the MBP. Luckily enough I had both a bluetooth keyboard and a mouse attached so I didn't loose control of the system otherwise I wouldn't have been able to use the system any longer and I wouldn't have been able to revert to the original kext. Anybody tried different recipes of kext mixings between the two different OSX builds and can show better outcomes?

     

    Anyhow, it is a very annoying issue and I am wondering how it could slip through the quality tests. Given the size of this thread it doesn't seem rare at all. Moreover when I don't have an USB drive attached my console logs are full of trackpad/keyboard errors (the SSD will surely enjoy all this unnecessary activity just to reduce its average lifespan!). Really difficult to miss it. I really hope Apple will issue a fix within days or I will definitively return my unit before the 14 days return period expires.

  • by Oli.S72,

    Oli.S72 Oli.S72 Nov 2, 2013 1:55 AM in response to kyawlin
    Level 1 (0 points)
    Nov 2, 2013 1:55 AM in response to kyawlin

    Since some old questions and findings come up again and again, please make sure to read the summary in https://discussions.apple.com/thread/5509561

  • by nstr,

    nstr nstr Nov 2, 2013 1:59 AM in response to kyawlin
    Level 1 (0 points)
    Nov 2, 2013 1:59 AM in response to kyawlin

    As mentioned quite often in here... I just want to confirm I'm running now 4 days without a freeze. I plugged in an USB2-device into one of the USB ports and used the machine a lot... with normal office work and also some games.

     

    I think, if it is an hardware issue, why would a USB2-device stop it? Or closing the lid and reopening after a while?

     

    Now just a quick info I found on the web, it has nothing to do with our issue, but with the way Apple supports the products after the 14 day refund period:

    http://www.techradar.com/us/news/computing/apple/apple-recalling-macbook-air-lap tops-with-faulty-flash-drives-1191193

    Looks like they have faulty SSDs in the MBA during the period of one year. They found the issue now and do a recall on ALL devices which are affected.

     

    So far, I would say there's nothing to worry about. It's annoying to buy a quite expensive piece of hardware to find out there's an annoying bug somewhere. I'll hope the best and looking forward to the update to be released.

  • by Oli.S72,

    Oli.S72 Oli.S72 Nov 2, 2013 1:58 AM in response to Artyom Devyatov
    Level 1 (0 points)
    Nov 2, 2013 1:58 AM in response to Artyom Devyatov

    Artyom Devyatov wrote:

     

    New MacBook Pro affected by this c1 bug?

    So far not a single person has reported it.

    It is more than unlikely that the rMBP is affected by the c1 stepping bug of the intel chipset.

    I am 100% sure that the rMBP is free of the c1 stepping bug.

  • by Oli.S72,

    Oli.S72 Oli.S72 Nov 2, 2013 2:13 AM in response to nstr
    Level 1 (0 points)
    Nov 2, 2013 2:13 AM in response to nstr

    Let's look at it:

    1) Within 14 days after purchase you can return your device and not give any reason why you do.

    2) There is a 90 days full warranty that includes phone tech support.
    3) You have one year limited warranty on hardware defects.

     

    As you can see, there is no logical sense in people saying "it is a hardware defect, please return your device within 14 days of purchase". You would have 1 year coverage for this.

     

    Now this comes with a few details that could explain a little.

     

    Your warranty of hardware defects of course mean, that your device will get repaired if possible and not swapped. So the guys that tell you to return it now quickly think they are doing you a favor:

    - right now there is no reason given to swap your device (neither will it help since not a single device had shown up yet that is not affected) so it needs to get swapped within 14 days (since you do not have to have a "real" reason)

    - they want you to feel the super service of apple. You have the feeling something is not as it is supposed to be? Apple gives you a new device without any discussions.

    - they do not know themselves what the problem is. Going for "it's better to be safe than sorry" they tell you to return it. Simply because they think if it's hardware, they told their clients and customers to get a new device, so they did the right thing.

     

    That's my thoughts on this

first Previous Page 94 of 199 last Next