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

Do you guys think that one - if not too unconvenient - should return the Macbook no matter if there will be an update or not? Somebody wrote about SSD lifespan or something... or are those errors not really exhausting the hardware right now? Or, to put it differently: Is any longterm damage done by those errors?

Of course it's a lot of money, I'm not saying it isn't... But within that 14 days your money is not at risk.

Anyway, I am in the same boat and I do hope they get it fixed sooner rather than later. 

I do not believe they are exhausing the hardware at all. In any case apple would happily provide you with a replacement if the hardware fails within a year. I would be really surpirsed if they did not replace a defected machine even after the 14 day period is up. This is because a hardware defect is different from normal ware - it is more so Apple's fault and therefore they would be responsible, not the user.

I've been following this discussion since it started and appreciate all the info that has been posted.  Also, that it appears to be a problem with the majority, if not all, late 2013 13" rMBPs regardless of place of purchase.

Just out of interest though, is there anybody out there with the same problem that purchased their late 2013 13" rMBP from the Apple Store at Westfield, Doncaster in Melbourne, Australia?  If so, any comment from the Apple staff there?

Thanks.

In Russia we have special rules.

For example, I can send MacBook back to Apple, but Apple will open the box and find stones or sawdust inside.

Helpful information:

If you have not received your MacBook yet, postal company can keep it for a week before you pay for it.

Joukoda wrote:

 

Do you guys think that one - if not too unconvenient - should return the Macbook no matter if there will be an update or not? Somebody wrote about SSD lifespan or something... or are those errors not really exhausting the hardware right now? Or, to put it differently: Is any longterm damage done by those errors?

one of these lines has 167 Bytes.

So 1000 lines make 163 kB.

If you surf on facebook for a few minutes, look at some photos your friends uploaded, etc. your browser will easily save a few MB to the cache on your SSD.

So I would not worry about this aspect at all.

I would look at it from a very different angle. How do you feel? If you feel really worried - return it. Because you didn't spend a whole lot of money for a premium product in order to feel worried for many days.

I see no way that any longterm damage could be caused by this. The amount of data written to the syslog is nothing.

BTW: I have a Macbook Air with 128 GB SSD. Three years old (late 2010). Daily heavy usage. (And I mean daily as in: really every day, since this is my workhorse and my private Mac in one machine)

SSD is always at least 70-80% full.

On average I wrote 15-20 GB of data every day to this SSD. On some days with heavy video editing even a few hundred GB.

The SSD still works perfectly.

You can count how many people reported problem in the thread... Let say 500? That's not many, plus another 2000 people didn't post on this thread, 2500 in total? Out of how many mbp sold? You need to get the exact number before saying anything, it looks so many ppl complaint on the forum doesn't means it is everyone have the problem.

I just talked with a Senior advisor for about 25 minutes and told him everything about the issue. He said that it is a non-fatal software bug (he is 100% sure) and said a fix is on the way, but is not sure when it will be out. He also confirmed that pluggging in a USB fixes the issue for the time being. He said the issue was not caught before launch because it is an intermittent issue that is spontatneous and only affects a certain model with a certian build. It therefore makes sense, although does not excuse them, as to why the issue was not fixed prior to launch.

Thanks for the info, where is his source from btw? apple internal communication?

Another little update. Today i visited the Apple Store and i looked at rMBP on display. All rMBP 13 late 2013 had Build 13A2093 Mavericks but one thing was very interesting:

- 2 Macbook Retina Late 2013 i5 2.4GHz 8GB 256GB had error logs "The USB device Apple Internal Keyboard..."

- 1 Macbook Retina Late 2013 i5 2.6GHz 8GB 512GB had no errors on console, nothing connected...

So i asked to Genius guy if they are aware if this situation and he said to no worry about this because it is at 99% a software/driver/Firmware issue and Apple should resolve it very soon. So i asked why the 2.6GHz had no error logs and the 2.4GHz always shows that error, he said that this is due to that Hardware...

He also said that we cannot be 100% sure about this because only Apple knows the bug detail and we can only wait or give it back but for him it is a software issue...

I am pretty sure that somebody had freeze problem also with 2.6GHz 512GB, we can read in any page of this discussion...

This is another info for you all

I am not sure but it sounded like he has heard of the issue before and assured me that it is a sofware problem numerous times, and highlighted that the same trackpad and keyboard are on the 15 inch model, which does not experience the problem.

i say all you guys return them, for as much as apple charges for its products they have been bringing a lot of crap to the market, apple is not what it used to be...

JapaneseAreBitch wrote:

 

You can count how many people reported problem in the thread... Let say 500? That's not many, plus another 2000 people didn't post on this thread, 2500 in total? Out of how many mbp sold? You need to get the exact number before saying anything, it looks so many ppl complaint on the forum doesn't means it is everyone have the problem.

Correct. And even more: who does not have problems will very likely not end up here.

We had that topic before.

I opened a thread in a German mac forum. (www.macusers.de) asking everybody who owns a new 13" rMBP to please report whether he has freeze problems or not. So this was not a place where only people would go if they have a problem.

result:

10 people answered (have a rMBP 13")

7 people have had freezes

2 reported to have USB devices plugged in often or most of the time

1 did not answer yet, whether he has USB devices plugged in or not.

So we have 1 potential (not more than just potential) healthy candidate out of 10.

That is why I am by now 100% convinced: all devices are affected.

Having followed this discussion for days, let me provide some new info. Just visited an apple store nearby, and all the 13'' macbook pro retina there do not have the "...USB..." log message. No USB devices are connected and they are not in guest account, build number still 2093. I didn't ask the staff there, but my guess is somehow they managed to do a quick fix at least on their display machines. Consider that they are still selling the machines, I believe there will be a fix sooner or later.

idark77 wrote:

 

Another little update. Today i visited the Apple Store and i looked at rMBP on display. All rMBP 13 late 2013 had Build 13A2093 Mavericks but one thing was very interesting:

- 2 Macbook Retina Late 2013 i5 2.4GHz 8GB 256GB had error logs "The USB device Apple Internal Keyboard..."

- 1 Macbook Retina Late 2013 i5 2.6GHz 8GB 512GB had no errors on console, nothing connected...

 

So i asked to Genius guy if they are aware if this situation and he said to no worry about this because it is at 99% a software/driver/Firmware issue and Apple should resolve it very soon. So i asked why the 2.6GHz had no error logs and the 2.4GHz always shows that error, he said that this is due to that Hardware...

He also said that we cannot be 100% sure about this because only Apple knows the bug detail and we can only wait or give it back but for him it is a software issue...

 

I am pretty sure that somebody had freeze problem also with 2.6GHz 512GB, we can read in any page of this discussion...

 

This is another info for you all

I have the i5 2.6/16/512 and have freezes and the lines inside the log.

Are you sure you were not logged in as Guest on that 2.6?