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

How would that explain that just this particular model of Macbook is buggy?

Interesting question is: why is Mavericks build 13A2093 affected much more than other builds?
Again, it can only be guessed by me. (Apple doesn't tell, so I have to guess)

Since the new MacBook Air has proven to have a fantastic battery life (and with Mavericks even more) Apple had to make sure the new Haswell rMBP dos not fall far behind that.
And to be even more specific, the 13 inch Haswell rMBP should not fall far behind.
Why that?
Because the past has shown, the 15 inch was often bought by people who do not care as much about portability and battery life and such things. These devices are often used almost as desktop computers.

But the 13 inch is a different story. It has to compete with the 13 inch MacBook Air directly.

So, battery life is a big issue for this modell. If the 13 inch Air is at 14-15 hours now with Mavericks, the 13inch rMBP would look quite bad if it would sit around 7 or 8 hours.

So my guess is: the software guys were asked to max out the power savings for the build 13A2093. Save what you can. We need every single minute extra battery life.

So they maxed it out.

On build 13A2093 of Mavericks.

And we all see the result.

Oli.S75

What You wrote is exactly the usb c1 bridg problem. If keyboard and touchpad are usb3 (somone can cofniemy otherwise?) then the simple answer that resolvoes using usb2 is that usb2 is holding usbcipset prom going to s3 mode.

I was go order tonight CTO but in this case ill wiat for mainboard with c2

wronekk wrote:

 

Oli.S75

What You wrote is exactly the usb c1 bridg problem. If keyboard and touchpad are usb3 (somone can cofniemy otherwise?)

         

I think, I can.

Keyboard and Touchpad both report to me in the system information console as:
up to 12 MBit/s

Same applies to bluetooth.

Only the Hub reports as:
up to 5GBit/s

are you bringing yours back oli ? i am new to mac and it seems you know a lot when it comes to apple os.

are you prefering a c2 chip or is it ok for you to wait for an update that fixes the older ones ? thx

AdamVidalis wrote:

 

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.

I'm in the same boat fella, waiting to purchase when this is resolved, however you can't knock people for repeating the same thing on this thread, they've paid a nice bit of cash for something that should work great with no bugs 'out of the box' like the 15" late 2013 retina is doing. They will carry on and so be it, the longer this thread is the faster Apple will sort this out and the faster me and you can order our awesome bug-free 13" retina MBP's, just let it roll out man as people notice their MBP's buggering up, Apple will sort it as they always do!

Joukoda wrote:

 

How would that explain that just this particular model of Macbook is buggy?

It is not proven to be the model. It could much likely be the special build of Mavericks (13A2093) that is preinstalled on these devices.
Of course, it could simplay be the combination of both:
- Mavericks has this feature "I put USB to sleep if no device is present"
- 13" rMBP has a specific chip/transistor/whatever that does not like to wake up under special circumstances
if you change one of the both, the problem is solved.

So we might see an update for Mavericks coming from Apple that

a) fixes the problem

b) costs a few % of battery life.

Oli still You dont confirm it's usb2. Thats just showing keyboard using bt dongle. I tunik it's possible  still to repair althought it's hardware. If yous different cpu firmware would do.

deleted

deleted

RIVERSTALKER wrote:

 

are you bringing yours back oli ? i am new to mac and it seems you know a lot when it comes to apple os.

are you prefering a c2 chip or is it ok for you to wait for an update that fixes the older ones ? thx

I do not know so much about Apple OS X in particular. But I work as an IT professional for 15 years now and I have a fair knowledge of UNIX based operating systems. Since Apple OSX is based on Darwin, I have an idea about what could be going on.

Right now I tend to keep mine. If I would have seen graphical errors, I would return it though. I can hardly believe these topics are related. One is USB, the other is graphics. They are nowhere connected.

wronekk wrote:

 

Oli.S75

What You wrote is exactly the usb c1 bridg problem. If keyboard and touchpad are usb3 (somone can cofniemy otherwise?) then the simple answer that resolvoes using usb2 is that usb2 is holding usbcipset prom going to s3 mode.

I was go order tonight CTO but in this case ill wiat for mainboard with c2

No it is not the exact c1 bridge problem.
I have a very good ressource on the c1 bridge problem, but unfortunately it is German. anyway, it is http://www.heise.de/ct/hotline/USB-3-0-Probleme-mit-Haswell-1895962.html

Reading this, I understand that the c1 bridge problem has to do with enumerating the controller of memory (stick) after a sleep mode. If there where files open on the filesystem on the external USB3 memory, the paths pointing to the files are not available for a very short time after the wakeup. And some controllers of external USB3 memory take this as a signal for introducing themselves as being a new attached device.
So there are quite a few differences there.

But I have another reason not to believe in your theory. The c1 bug is known for many months. Apple would not have dared to say "oh, what the heck?" and build them into the rMBP anyway. Also, why do the new MacBook Air does not have the same problem? It was introduced much closer to the time when the c1 bug was discovered, yet there had been no indication that the MacBook Air has this bug.

I strongly do not believe the c1 bug has to do anything with this.

And for people booting windows and running some chip-test on the Mac hardware to find out the stepping of the chipset:

the article I mentioned above states clearly that it is somewhere from hard to impossible to find out which stepping of the chipset you really have in your device.

Also, do not forget, the Haswell CPU that is build into the rMBP is a brandnew model. It came on the market after the c1 problem was already well known.

In my experience, it appears that if you are connected to only one network, system doesn't freeze on MacBook Pro, Retina, late 2013. Whenever, network changes, it freezes once and fine afterward. Let me know if you have similar experience.

Yes I am in agreement with you. We have actually paid hundreds of pounds for this machine, so we can have our rant if we want.

This page was started up for people with the MacBook Pro retina that have encountered problems. Not for people to go on how they would like to buy one when they're fixed.

AdamVidalis doesn't understand as he has not paid hundred pounds for a faulty machine. He doesnt even have one!!! Fact!

do you guys experience any speker problem? mine is like sometimes even after you unplug the headphone from the rMBP, it doesnt have sound and I need to plug and unplug again to solve it..

Usernj wrote:

 

In my experience, it appears that if you are connected to only one network, system doesn't freeze on MacBook Pro, Retina, late 2013.

My rMBP has been on only one network since I bought it and has frozen 2 times. Also a huge amount of people reported this problem and I think not many people change their network often.