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

Somebody who doesn't understand the difference between a status message and a real error in the log and pretends to be any kind of expert shouldn't be taken seriously.

To everybody who hasn't got a clue about how their mac works and just discovered the console this past week: install the update and go back to work and enjoy your macbooks, they are fine. The console logs thousands of messages every day for everything going on on your machine. That's the way unix based systems are supposed to work. Be assured that logging two extra lines every five seconds will have exactly zero impact on the battery life.

really, start using your machines and worry only if they stop working, don't spend any more time wondering about what MIGHT happen.

>> As a hardware engineer, I give my guess as following.

good disclaimer. As a hardware engineer, I suppose you speak of what you know, so you understand hardware better than software and can see the potential problem in the hardware part. Although equally fairly we can say a software engineer would know better the software interactions between the components and could be able to come up with some perfectly credible software based explanation for it.

A few pages back, Oli wrote an intersting theory about milliseconds and thresholds, for example.

I guess the only way is to wait reports of freezing on patched machines.

ThatIsTheWay wrote:

 

As a hardware engineer, I give my guess as following.

 

This is a hardware problem exising in the keyboard and trackpad. The keyboard or trackpad sometimes might fail to send a valid wakeup signal to the system through the usb interface. The system put the usb hub into sleep in a short time if no device triggers a wakeup signal. If the system is connected with another properly working usb device such as mouse, which will keep the usb hub awake, the problem is likely "cured".

 

As the problem existing in the chip of keyboard and trackpad module (or some chip mudule on logic board handling events from keyboard and trackpad), it can't be fixed by updating the OS, or firmware. The only solution is to replace the keyboard and trackpad module by apple if luckily the defect module lies out of the logic board.

This is too funny. You are trying to convince that the issue (freezing) can't be fixed with a software update... But hey, guess what: Apple already provided a fix!

And obviously you don't understand that hardware is designed so that most regressions can be fixed either by updating the software using the hardware or by updating the firmware inside the hardware.

DSL_Steve wrote:

 

Late 2013 rMBP, 13in, 4/128

 

Installed the update last night and all went well.

 

But this morning had a strange event happen. After the MBP went to sleep I went to wake it up by touching the track pad and nothing happened—no wake up. Then I started hitting keys, even the power key, and nothing happened.

 

Guess what worked? Closing and reopening the lid!

 

I hope this is a onetime event and not a new issue.

Just reposting for everyone.

ThatIsTheWay wrote:

 

As a hardware engineer, I give my guess as following.

 

This is a hardware problem exising in the keyboard and trackpad. The keyboard or trackpad sometimes might fail to send a valid wakeup signal to the system through the usb interface. The system put the usb hub into sleep in a short time if no device triggers a wakeup signal. If the system is connected with another properly working usb device such as mouse, which will keep the usb hub awake, the problem is likely "cured".

 

As the problem existing in the chip of keyboard and trackpad module (or some chip mudule on logic board handling events from keyboard and trackpad), it can't be fixed by updating the OS, or firmware. The only solution is to replace the keyboard and trackpad module by apple if luckily the defect module lies out of the logic board.

Now, isn't that strange?

Just a few minutes after I told some other guy here, that he has not proven yet even once to have any profound knowledge about software or hardware, this new user shows up. Registered just today, his first posting is what we can read here. A hardware engineer. What a coinsidence.

Now I have to be very careful not to fall for that conspiracy thing as well ...

ThatIsTheWay? What a funny nickname ... Maybe I should choose "TrustMeIknowAllaboutTheOneAndOnlyTruth" next time? What do you think, sTro ... errr, sorry, ThatIsTheWay ...?

@dsl_steve

interesting, although I've had that happening extremely rarely on a very old Snow Leopard based macbook and one time also on a new Mountain lion based macbook air. since this is not a freeze in mid-use, it might be something else, although keep us posted because this kind of sane reporting really helps (unlike extreme schizoid trolling).

DSL_Steve wrote:

 

DSL_Steve wrote:

 

Late 2013 rMBP, 13in, 4/128

 

Installed the update last night and all went well.

 

But this morning had a strange event happen. After the MBP went to sleep I went to wake it up by touching the track pad and nothing happened—no wake up. Then I started hitting keys, even the power key, and nothing happened.

 

Guess what worked? Closing and reopening the lid!

 

I hope this is a onetime event and not a new issue.

 

Just reposting for everyone.

This sounds like a different issue to me.
In the past: system is not sleeping, keyboard/touchpad freeze, system continues to work
In your case: system is sleeping and refuses to wake up. We don't know whether the keyboard/tochpad did not work or whether the whole system simply would not want to come back from sleep.

That EFI update will not keep all Macs on this planet from crashing or misbehaving from time to time under some circumstances. So far, since the update no one besides you has reported any problems. Until it gets more of these, I tend to believe it  might have been simply a "normal problem" as they sometimes happen on computers.

Is it the same keyboard and trackpad on the 15 inch rMBP?

This is the rumor.........

Your screenshot is pretty fake:

1. only two record? mine is about 100+

2. two of your record has the exactly same time, even the second part is same, did you used photoshop? they can't be the same second mate, the trackpad has to fall into sleep first then being waked up according to what you say.

i have strong reason to believe the 13 mbp is faulty and also proved by apple senior advisor. i am not sure why you trying to comfort everyone with your imagination?

hahaha stronic you ar some hardcore troll, although at this point you just got into last stage trolling where it's basically just baseless accusations without any kind of proof or authority. it's too bad that human nature has such a hard time to get to ignore guys like you. I'll try first, goodbye!

sTronic wrote:

 

Your screenshot is pretty fake:

 

1. only two record? mine is about 100+

 

2. two of your record has the exactly same time, even the second part is same, did you used photoshop? they can't be the same second mate, the trackpad has to fall into sleep first then being waked up according to what you say.

 

i have strong reason to believe the 13 mbp is faulty and also proved by apple senior advisor. i am not sure why you trying to comfort everyone with your imagination?

ROFL

You know what? When I made the screenshot, I knew you were going to say it is faked with photoshop. Muahaha.

Yes, only two records, sorry I can't give you more. As I mentioned before, I have USB devices plugged in now.

09 is the hour, 15 is the minute and 22 is the second (I am in Germany, so it was done this morning my time)
So the messages happened during the same second. You know what? I bet they even happened within the same 10 milliseconds. Because today computers are quite fast, you know?

Your conspiracy thing is really funny. I'm in for the game. Let me know how I can prove to you that my screenshot is real. I'll go for it.

You have to understand, this is an Hardware problem, why ?!? Of course, cause Dave the wise men says that !!

So, please stop with this blasphmeous rumors about software issue !!!
And what about the patch released ?!? Wanna talk about it ?!? It's just a smoke in the eyes for poor people !!!

Believe in me, cause I'm a famous Hardware (& Software too) enginer and also a good chef, moreover I am a very good swimmer and I've two dogs and one cat.

World is going crazy !

This board is so funny !

That "error" message appears on my 2012 MBP running on Mountain Lion. Should I try to return it and get a new one? Let's just use common sense here. We had the issue for so many days, people now are on denial mode. The issue was fixed, accept it. I paid a lot of money for my new rMBP as you all did, but at the end of the day is JUST a computer. Enjoy it.

sTronic, please stop trolling. You are not helping at all. It is easy to see that those events might have identical time stamps. Like here:

https://discussions.apple.com/thread/3207951?start=30&tstart=0

BTW, that post is from 2011. So please, stop the trolling. The kernel event is not a problem necessarily. And there is no reason to believe this can't be corrected with a software fix. Why? Because Apple corrected it with a software fix

sTronic wrote:

 

Your screenshot is pretty fake:

 

1. only two record? mine is about 100+

 

2. two of your record has the exactly same time, even the second part is same, did you used photoshop? they can't be the same second mate, the trackpad has to fall into sleep first then being waked up according to what you say.

 

i have strong reason to believe the 13 mbp is faulty and also proved by apple senior advisor. i am not sure why you trying to comfort everyone with your imagination?

I made a new one, just for you, my special friend.

I tried to think of "what would be hard to do on photoshop?". For me, this would be impossible to fake, but of course I admit there are freaks that can fake anything. Even on video. So I give you credit in this point: today you can hardly trust anything that is made of pixels.
Anyway, I believe this would be much harder to fake than the first screenshot.

I chose images (searched in google by "crowd") with many small details, so this would make it harder to fake, no?
Otherwise, please advise me, what to do. As long as I do not need to send nude pictures, I'm happy to convince you that the thing about aliens living amongst us is worth to be thought of a little more ...

Are we getting a little off-topic here? I'm sorry. I can not resist.