New Retina Macbook pro 13 Haswell system hang/unresponsive

Oli.S72 wrote:

And again: Apple says no official word about all this. Why? Some senior advisor saying something on the phone or chat to some customer does not make it official to me, sorry.

I have not made up my mind yet, but one thing I know for sure: if Apple does not officially make a statement very soon, I'll return it. Why taking any risk if obviously Apple has not made it's homework?

I get your point. I'm going to take advantage of the 2 week window while I can. Each person I talked to led me to believe it is a software issue. Senior advisor that I talked to tonight (number 4 for the day...they probably loathe me by now) even said that.

Right now, patience cannot hurt, because I'm less than a week in.

Well, if you buy a new car, do you post in a car forum "it drives"? Something so basic might not be worth mentioning ...
People always only write on forums about what is not working.

No new infor, hust to add my woes to the long list (and hopefully push Apple more to work on this), same random trackpad and keyboard randomly lock (13inch late 2013 Retina Macbook).

I was in DxO editing images when it last happened. Here is the log. Closing the lid and opening it after 5 minutes made it unfreeze.

2013-10-29 15:31:28 -0700 DXOOpticsPro8[1102]: Prepare: DenoiseRawCamerabody not available for this image (not an error).

2013-10-29 15:31:46 -0700 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)

2013-10-29 15:32:39 -0700 DXOOpticsPro8[1102]: Prepare: DenoiseRawCamerabody not available for this image (not an error).

People are saying it also happens on non-haswell 13" MB Pro's, but I've yet to see anyone actually state their non-13 haswells are having this issue. Every single post on this discussion is from people with the 13" haswells. So anyone reading this, if you have an earlier model or a new 15" model and you have this problem, can you please reply and let us know. Because if it is just 13" haswell then that's a bit of a worry.

@mrakers85

Waiting is no problem for me either. What i am scared about is this scenario: one day, an update comes out.
"This fixes the problem of some MBPrs freezing" - and no more words than that.

Do i have buggy hardware, or not? Will the problem come back in 4 or 8 or (X) weeks when I plug in this new USB3 device for the first time? Was it a bug in software, or was it a bug in hardware and thy simply made Mavericks more tolerant about buggy hardware? I doubt we will ever know. And by this, I will never know whether I spent huge cash on something that was never the way it is supposed to be.

Bobs22 wrote:

People are saying it also happens on non-haswell 13" MB Pro's, but I've yet to see anyone actually state their non-13 haswells are having this issue. Every single post on this discussion is from people with the 13" haswells. So anyone reading this, if you have an earlier model or a new 15" model and you have this problem, can you please reply and let us know. Because if it is just 13" haswell then that's a bit of a worry.

I have seen a MacBook Air Haswell do the same thing, but not sure about other ones.

What I have heard is that a wide array of other Mavericks-upgraded Macs have the same issues.

@Oli.S72

Very true. I'm sitting tight until I hear from Apple on the issue and then making my decision on how to proceed.

The one year warranty does protect against faulty hardware though, so it's not as though I'm worried that a faulty computer is just mine forever.

Good thoughts.

Anyone have one that hasn't frozen?

since there has been alot of mavericks vs hardware talk here, has anyone tried running the machine with mountain lion instead? does the issue come up?

Mine hasn't frozen after a day of intensive use. However I do have some frame drops when switching tabs and stuff, you'll get my point probably.

Oli.S72 wrote:

@mrakers85

Waiting is no problem for me either. What i am scared about is this scenario: one day, an update comes out.
"This fixes the problem of some MBPrs freezing" - and no more words than that.

Do i have buggy hardware, or not? Will the problem come back in 4 or 8 or (X) weeks when I plug in this new USB3 device for the first time? Was it a bug in software, or was it a bug in hardware and thy simply made Mavericks more tolerant about buggy hardware? I doubt we will ever know. And by this, I will never know whether I spent huge cash on something that was never the way it is supposed to be.

Have a look a Linux sources codes and you'll find drivers are full of work-arounds for buggy hardware. It's really quite common. As long as that fixes the issue and the system as a whole functions as promised that's not really an issue.

Keep in mind that hardware is designed to function within certain specifications. There isn't a big difference between something that's just within specs and something that just outside. I don't know about this particular problem but very often it's not a black or white situation.

Did Apple drop the ball on quality assurance? Sure. But that doesn't mean they would've rejected the hardware had they noticed the issue themselves. Adjusting the specifications and having the driver guys fix it would've been an option then just as much as it is now.

I'm waiting for a 13" MBP retina, 2.6, 8, 512 to arrive in the mail, and then I'm going to turn right around and return it. Sad, but I feel it's the right thing. I'm not chancing a hardware issuse for eighteen hundred dollars.

I'm literally going to pick it up at the fedex site, remove the tags on the box and attach my return tag so I can get my refund ASAP. I'll keep watching these forums to see when it's safe to get one.

It's quite weird that not a single review has mentioned this.

After fresh re-installing Mavericks and without using flash, haven't had a freese since yesterday. That being said, I'm still getting errors in logs: "The USB device Apple Internal Keyboard / Trackpad (Port 5 of Hub at 0x14000000) may have caused a wake by issuing a remote wakeup (2)"