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

And this is probably a stupid question, let's say the trackpad issue is resolved. Is my console log supposed to have anything in it? Other than the trackpad message, there's always random stuff that pop up in there and I don't know if this is normal....

For example:

11/5/13 6:47:00.939 AM fseventsd[39]: check_vol_last_mod_time:XXX failed to get mount time (25; &mount_time == 0x100f613d8)

Yes it's normal that the console shows a lot of stuff.

you can check out the manufacturer and the display model by

open system preferences, displays, colours, open profile, scroll down to mmod (last) and open.

first is manufacturer, mine is 610

second is model type, mine is A020

still do not know if this result means samsung or lg, maybe the linked thread i post here can help us soon.

to find out the date of build just copy and paste the following to the terminal and press return.

ioreg -l | grep IODisplayEDID | sed 's/^.*<//g' | cut -b 33-36

the result is the date, your display was build (mine 0417). 04 means week 4 and 17 has to be calculated in a special way which i did not understand to be honest but you can read and learn it in the thread were i found all this.

https://discussions.apple.com/thread/5481839?start=1710&tstart=0

i just know my displays build date (week 4 2013) because a forum member had the same terminal result like me and he could work out the correct date.

feel free to join the discussion there, everything is explained very well and a lot of people share their opinions about image retention with the brandnew retinas.

i am just a poor devil when it comes to computers and i hope OLI.S can handle things better

edit:

here is how you calculate the terminal result to get your displays build date !

First two characters of the result are the week number and the last two are the number of years since 1990 (both in hexadecimal). You can use http://easycalculation.com/hex-converter.php to convert to decimal. For example, that command gives me "3016", which corresponds to week 48 of 2012 (1990 + 22).

my mac just froze twice this morning so I recorded it and I'm on my way to apple store to show them the video and hopefully get an answer.

Mine is slightly different

command gives me 3016

and mmod shows

manufacturer 610 but

Model A018

Hello,

I went to the Apple Store this morning (France) to bring back my MBPr 13. The first Apple guy said me that the problem was known and they are waiting for an update.

They wanted to exchange my computer (I'm in the 14 days return period) because I have an other problem (my screen isn't uniform when it's white) but they were out of stock (mid config).

The guy called his manager which wasn't aware from the problem (He said me "Perhaps the users said that but there isn't statement from Apple yet, I haven't the procedure to deal with your trackpad problem, but you are in one of the best customer service in the world").

So they gave me a card which extends my return period until they receive some new computers.

So I'm waiting their phone call and I hope I will get a new serie.

I've also quickly look at a demonstration MBPr and I haven't seen the logs (no USB plug in)...

I have also the same problem, i've had 3 freezes in 1 week.

Mine says 3016, should i be worried about this?

I don't know wether to return the machine or not, i'm just a bit sacred of the situation, i think it's not normal. i have noticed some screen error also, when playing a movie on itunes for example.

It's my first experience with apple products and so far it hasn't been so positive. I think i'll give it 3 more days, if there is no reason from Apple i'll sadly return the machine. I think it's too expensive to have so many issues, and also to take so long to give a proper solution.

sorry the link to the retina image retention and ghosting thread was the wrong one, my bad.

the correct link is:

http://forums.macrumors.com/showthread.php?t=1662379&page=4

and

here is how you calculate the terminal result to get your displays build date !

First two characters of the result are the week number and the last two are the number of years since 1990 (both in hexadecimal). You can usehttp://easycalculation.com/hex-converter.php to convert to decimal. For example, that command gives me "3016", which corresponds to week 48 of 2012 (1990 + 22).

if anyone knows how we can figure out the manufacturers code then please let us know. thx

and nobody should worry about the results in terminal and system preferences, it just could mean that we all have very old retina screens in our

brandnew premium book. and maybe apple still just uses lg displays which are known for some image retention and ghosting problems.

we have brandnew macbooks with 2012 displays built in which are famous making trouble from time to time.

I am not exactly a fangirl, but I have been an Apple customer for years. This is certainly a PITA and an unfortunate launch. I would be more aggravated as well if I have not left my new 13" rMBP in the box because it arrived after this issue surfaced so I am happily still tapping away on my 2009 13" MBP (which I have not upgraded to Mavericks yet as I want to make sure the bugs are shaken out of that). Many people who have been around technology would never buy the first build of an item, download the first version of any software; the likliness of something not perfect goes up with the complexity of a product. You wait for early adopters to surface the bugs, you wait for the manufacturer's (of the components) defects to surface. Just because something passed QA initially, doesn't mean every batch or lot shipped in is identical. I'm not trying to let them completely off the hook, but I do understand what happened, and I promised you there are people who are working around the clock to get this resolved, there is much yelling in meetings, and there will be a full post mortem (corporate speak for finding the person or persons to blame for what went wrong).

And the bottom line for Apple is simple: they stand behind their products and I have never known them not to make it right, usually being generous in the direction of the customer. So, you can return it, and when it is fixed, buy a new one, and go through the transfer process again, assuming you still have your old computer. Or you can just wait, it will be fixed shortly.

(I have been royally ****** at them when I bought an iMac in 2002 and two weeks later the new model came out. I went to exchange it - unopened - and they said they would - until they found I had a RAM upgrade, which they installed! Custom config? Would not take it back. The store employee said it was at the manager's discretion and this manager was a pitute. Arghhh.)

nbatteur wrote:

 

Hello,

 

I went to the Apple Store this morning (France) to bring back my MBPr 13. The first Apple guy said me that the problem was known and they are waiting for an update.

They wanted to exchange my computer (I'm in the 14 days return period) because I have an other problem (my screen isn't uniform when it's white) but they were out of stock (mid config).

The guy called his manager which wasn't aware from the problem (He said me "Perhaps the users said that but there isn't statement from Apple yet, I haven't the procedure to deal with your trackpad problem, but you are in one of the best customer service in the world").

So they gave me a card which extends my return period until they receive some new computers.

 

So I'm waiting their phone call and I hope I will get a new serie.

 

I've also quickly look at a demonstration MBPr and I haven't seen the logs (no USB plug in)...

Well, what the manager said sure sounds like simple politics to me. Imagine the Apple store that this guy is the manager for starts to burn down. You think that guy would call the firedepartment? I doubt it. He'd wait for someone from Cupertino to call him and officially tell him, yes, there is a fire in your store, yes, the right decision now is to call 110 right now and yes, that is your pair of jeans that is smoking ...

As for the demo rMBP: For a couple of days all stores seem to deny access to the file /var/log/system.log to the default user. So even if you're not logged in as a Guest, you are still not able to see those lines inside the log, although they're there.

Thanks for that info. I will try to look into all this asap. Probably not before tomorrow evening though.

hi oli,

please read my last two posts and you can find out whats going on with the displays built date.

the first link was unfortunately wrong

got places to be ... thx

RE: Apple store employees: the employees on the floor know about the issues from customers or from the geniuses. Sales employees are purposefully kept in the dark about issues, upgrades, and future products by corporate, because it makes it a lot harder to sell a product if you know too much.

New orders: I ordered a second 13"rMBP because I decided I didn't need everything top of the line, only the 16GB of RAM (and thus saved $700 by going with the 512GB and slower processor). This time I had it delivered to a store so I could return the first one I ordered at the same time. Pick up date is November 7. We'll see if this is resolved by then, so I can actually unwrap it;-).

I will say that although the log can be helpful, if you don't know what the logs are actually referring to you could waste a lot of time and cause a lot of undue stress worrying about it.  Not all entries in the log are errors.  Not all errors are bug related. 

Same error here!!, my new laptop not wroking as well it has frozen already four times (at least once a day!!!) very frustrating my first experience with mac !!!

my OS build is 13A2093, hopfully its a OS problem

Is anyone answering from apple suport?

my configuration

2.8

16GB

1TB

some log messages that I think are related

5/11/13 11:20:46.000 pm 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)

5/11/13 11:21:05.000 pm 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)

5/11/13 11:21:16.000 pm 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)

5/11/13 11:21:29.000 pm 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)

5/11/13 11:21:41.000 pm 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)

5/11/13 11:21:50.000 pm 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)

5/11/13 11:22:14.000 pm 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)