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

Cheers ;-)

L\'Indien wrote:

 

But so why does rMBP 15 under Mavericks seem to behave differently ???

 

Maybe rMBP 15" has a problem and does not handle sleeping and energy saving properly? But this is just guessing

Hey guys, I've had a little test before and after I installed the EFI update, and what my found is: The trackpad and keyboard will "fall asleep" If you don't use them for 3 seconds (approximately).

I've been full aware of this log "issue" since I bought it 14 days ago (thus sadly I've lost the right to send it back...), but I just knew they are so "tired" that they'd fall asleep this soon. I thought it'd be 5 seconds or longer... BTW, If this really relates to a feature called "power saving", isn't 3 seconds too short?

This will become a myth forever if Apple won't fix or just explain it. Anyway, I've decided not to care these log entries any more. Not because I think it doesn't matter, but they're so annoying to me, just like the red line of "Google Chrome Helper (Not Responding)" in Activity Monitor.

It does look like it is too short, however i think that the existence of these logs could be something good since it shows that there is definitely some power saving happening. No?

I'm sure that the log entry will be removed later on if it is not needed. And as for going to sleep after 3s, why would it be too short?

Modern components go to sleep and wake up very, very quickly. The aim is to have all possible components in sleep as often and as quickly as possible. So 3s is definitely not too short time. Let it sleep whenever it wants!

L\'Indien wrote:

 

Oli.S72 wrote:

 

The information message tells you this:
The USB hub had been in a sleeping state. Then the keyboard and the touchpad had been used. This usage interrupted the sleeping state, now the USB hub is awake again.

 

So what we have? If nothing is going on on the USB port for 5 seconds or longer, the system puts the USB hub into a sleep mode. In order to save some extra battery life. Hitting a key on your keyboard wakes the USB port up again.

 

Totally agree with you, Oli.

 

But so why does rMBP 15 under Mavericks seem to behave differently ???

 

Does your late2010 MacBook Air running Mavericks report this console message only when waking up from sleep or after "every 5 seconds USB sleeping" like the rMBP 13 does ?

 

Thanks !

About the 15" rMBP: I don't know. The only idea I have: since there are no messages that the USB has been woken up from a sleep mode, it indicates to me that maybe on the 15" rMBP the USB port never goes to sleep at all. Many people with a 15" rMBP use this device as a desktop computer replacement with rather little interest in portability or battery life. So this thought might be not too far off. But I don't know. No 15" rMBP ever reported the log messages? I don't remember that clearly. No freezes I do remember, but for the log messages I would have to search through 145 pages of this thread ...

Of course, I could ask some senior tech guru about this and after making sure that nobody listens to us, he might whisper "the 15" rMBP has some serious hardware issues, you know? It never sleeps ...!"
Sorry, could not resist on playing a little s-tronic games here ...

Yes, the message comes up in my MBA after not touching keyboard and mouse for a while. My feeling is that it might be longer than 5 seconds, but I would have to test that - which I can't right now as I have some work to do and for that I need some USB and other external devices to be plugged in. I will test that out on the weekend.

First of all i wanted to say Oli.s75 You were right;)

To all the trollers about its hw problem, I was the only one person from You all who was saying its hw, but the difference is that I am a system engeenier with some knowledge of what I was writing. I mean that you are saying it's for sure hw but you don't have any, none argument for that.

So every hw troll should say sory to Oli for bullsh*****.

For any one how does not understand the idea of hw and sw problem,  most commercial protocol hubs like c1 c2 on normal motherboard  are special purpouse  micro controller which is programmed with special software. So mostly if something is ****** up its software. I guess that the only problem with the old c1 c2 problem is that they could not been programmed from PC data. But as apple has own motherboard they create In special way so most on board chip can be programmed from os level.

One more thing is that the build OS might be in some level in debug state so that's why in some macs there are messages seen in some not.

Those messages all on PC/Macs and so but viewing them is enabled.

So any simple any massage which is non kernel panic is just a message.

You can be worried only if in front of message you is that its kernels panic

And it seems the 15" have their issues as well, and the issues are linked to powersaving/sleep mode as well.
http://support.apple.com/kb/DL1705

Broken NVIDIA chip? Needs to be replaced? Wouldn't want to hear what some senior tech gurus have said in the past to this ...

@Oli.S72,

1. If its true, please provide screenshot of the log message from your MBA 2010 with the "About this mac" windows which shows model and make year. Two windows must be overlap a little bit.

2. if its not a hardware issue, 15 inch MBP and the haswell MBA should have the same log message, especially the MBA, its targeting at long battery life market, why the MBA doesn't reported as much? and never had the keyboard lockup issue reported? Plus, there is no good explainion of why 15 inch MBP doesn't have the log message, it can't be "15 inch doesn't need long battery run time", this is a bad reason, 15 inch is still a laptop, Apple will want ot make all their laptop last as long as possible on battery and will do everything they can to beat other competitors.

3. You can't ingore the fact, the lock up issue only happen mainly in 13 inch, very rare reported on any other haswell device. and same as the log message thing only a unique feature to 13 inch MBP.

You have the face the fact, tyring to find execuse for 13 inch to comfort people is doing a damage to them.

The apple senior advisor is working for apple, and they dealing it day to day, if they said this is a HW issue, and the EFI update is just a work around to resolve software side of issue, you think you are better than them? and remember they are working for apple. um.. but i am start thinking, may be.. you are too. how much per post?

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.

@DSL_Steve

As i said, there are problem with the hardware. Believe me in 2 months later, they will release a new batch with hardware problem fixed.

Each motherboard has a revision number, the batch we currening getting might be Rev 01, they will have 02 to fix the problem.

i saw it earlier in the updates tab in appstore BUT i was having a problem with the internet connection but now it's not appearing, not even below the installed section. when i try to install the downloaded file from the like above it says that the it cannot be installed in my laptop or something. is this normal?

sTronic wrote:

 

@Oli.S72,

 

1. If its true, please provide screenshot of the log message from your MBA 2010 with the "About this mac" windows which shows model and make year. Two windows must be overlap a little bit.

 

2. if its not a hardware issue, 15 inch MBP and the haswell MBA should have the same log message, especially the MBA, its targeting at long battery life market, why the MBA doesn't reported as much? and never had the keyboard lockup issue reported? Plus, there is no good explainion of why 15 inch MBP doesn't have the log message, it can't be "15 inch doesn't need long battery run time", this is a bad reason, 15 inch is still a laptop, Apple will want ot make all their laptop last as long as possible on battery and will do everything they can to beat other competitors.

 

3. You can't ingore the fact, the lock up issue only happen mainly in 13 inch, very rare reported on any other haswell device. and same as the log message thing only a unique feature to 13 inch MBP.

 

You have the face the fact, tyring to find execuse for 13 inch to comfort people is doing a damage to them.

 

The apple senior advisor is working for apple, and they dealing it day to day, if they said this is a HW issue, and the EFI update is just a work around to resolve software side of issue, you think you are better than them? and remember they are working for apple. um.. but i am start thinking, may be.. you are too. how much per post?

You know, you are quite funny in a way ...

Anyway, no problem with the screenshot
Forgive me to gray out the name of my device, as my personal name is part of it. And there are really strange guys out there in the internet, you know?

Now, as you can see, I work on a late2010 MacBook Air. If I'd be working for Apple, I might have slightly newer hardware, what do you think?

Your hobby is to think of new conspiracy theories, right? Your neighbours wouldn't happen to work for NSA, CIA, KGB or anything alike?

Anyway, since you show so much effort in convincing everybody here that the hardware is broken, I wonder why? What is your interest that everybody should believe you (although you haven't proven yet even once to have any profound knowledge about software or hardware) that hardware is broken on that device?

If I'd be into the conspiracy hobby thing as you, my best bet would be, you get paid by some company in Redmond. But as I am not and prefer to stick to the facts, I keep on thinking you might be just a little bit bored maybe.

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.