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

I had an update this morning that should fix this problem.....

buy it after 2 months. current batch has fault and will be corrected in the next batch.

Could someone just clear up the log question for me please?  Forgetting this trackpad error, am I meant to have a log-full of various different things all the time?  Like about 4 or 5 a minute?  Or should this log be pretty much clear?

I installed the update, still have the same message in the console log!!

'The USB device Apple Internal Keyboard/Trackpad may have caused a wake by issuing a remote wakeup'

EsKlar wrote:

 

Oli,

 

Thanks for your thoughtful response. I do have one nagging question, and it looks like sTronic beat me to the punch in asking it.

 

How come when you leave a USB drive in the 13inch, the log message suddenly disappears? It all of a sudden starts to look exactly like the kernel log in the 15inch.

That is quite easy to explain.

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. Why? Because they are internally attached to the USB port, just as they were external devices. You can see this quite well inside the system information console, where both keyboard and touchpad are childs of the USB hub.

Now you plug in an USB device, like a memory stick or a external mouse. This new USB device gets registered inside the system. In other words, Mavericks now "knows" there is a device in the USB port. And Mavericks from there on will not put that USB hub into sleep mode.

Since the USB hub is not put to sleep anymore, of course there can't be any messages about the sleep mode being interrupted.

Why did Apple decide to stop th sleep mode as soon as something is externally connected to the USB port? I think that is the only way. Since you can't know, what this part of hardware is and what it does, it could be more than tricky to sleep on that port. There are devices that rely heavily on minimum latency. 2 milliseconds is a big timespan already. Putting the USB hub to sleep and waiting for the external device to wake it up would be a no-go here. So as it is better to be safe than sorry, the logic is simple: external USB device plugged in = no sleep mode for the USB hub.

I don't know why some people here try to talk people into the fear of having bad hardware. It's nonsense. The storys they make up about senior tech gurus from Apple, giving them secret inside information about the truth ... it does sound a little, well ... unrealistic ... to me. Maybe some real "experts" are having a beer together while exchanging conspiracy information? I don't know. But, please, always judge for yourself. Do what I did. Make some research. (ok I admit, if you happen to be an IT profesisonal and have good knowledge about operating systems, kernels and drivers, that will help a little.)

A few last words: The messages appear on other (older) devices as well. After upgrading to Mavericks. So this is not something absolutely unknown or unusal for this operating system to report.

As said before: it is a kernel message with the priority 7. (you can see for yourself inside console -> highlight one of theses messages -> klick "information" on the top -> See "level".
Compare it to this: https://developer.apple.com/library/mac/documentation/macosx/conceptual/bpsystem startup/chapters/LoggingErrorsAndWarnings.html and you will find:

"The lowest priority, and normally not logged except for messages from the kernel."
In other words: it's not an error. It is simple debug information. Just as millions of other lines inside the system.log

When I open my console on my late2010 MBA, the console is also full of messages.

Take any Mac, open up a terminal and type "tail -f /var/log/system.log" in it (hit "CTRL + c" to stop again) and watch this window, while working normally with that Mac. You will see tons of messages. Why? Because this is what UNIX based operating systems do all the time. The log files on our linux servers have many MB every day with that info stuff. Mavericks is based on Darwin. Darwin is a BSD, so in other, more simple, words, it is UNIX. Boot up a UNIX based operating system without a splash screen and you will see millions if lines of debug information scroll over the screen (and they all get written into the logs as well). It's absolutely normal.

HTH

<Edited By Host>

Very good comment!

thumbs up!

Guess what I just found inside the console of my late2010 MacBook Air (3 years old!) running Mavericks

08.11.13 09:15:22,000 kernel[0]: The USB device Keyboard Hub (Port 2 of Hub at 0x26000000) may have caused a wake by issuing a remote wakeup (2)

08.11.13 09:15:22,000 kernel[0]: The USB device Apple Keyboard (Port 2 of Hub at 0x26200000) may have caused a wake by issuing a remote wakeup (3)

As you can see, the hardware address (0x26000000) of the USB hub is different due to different hardware, but otherwise it is the same simple kernel information message.

Very well thought out, and well put Oli.S72

Can anyone comment on the battery life after the fix? Maybe I should start another thread?

Was going to buy the rmbp 13" a few weeks back when it first came out but then found out about this issue.

Now it seems that it is finally fixed but some people still says that the battery life might be compromised because it is not going to sleep properly. Anyone has real data to prove it? I woudl really appreacite some insight on this

Zekepao wrote:

 

Can anyone comment on the battery life after the fix? Maybe I should start another thread?

 

Was going to buy the rmbp 13" a few weeks back when it first came out but then found out about this issue.

 

Now it seems that it is finally fixed but some people still says that the battery life might be compromised because it is not going to sleep properly. Anyone has real data to prove it? I woudl really appreacite some insight on this

I do not have any information on this, too, but as the messages still appear, it means even with the new EFI the USB hub is still put to sleep mode. I expect no noticable difference in battery life. But let's wait what people report.

PLEASE can someone tell me if I should have a constant log-full of errors?  Or if it means I have a problem?

how do i know that it will be after two months? I realy mst have a new MBP soon, but I don't wont to buy a computer with hardware problems. It's ok if there just is a software issue.

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 !

Oli.S72 wrote:

 

Guess what I just found inside the console of my late2010 MacBook Air (3 years old!) running Mavericks

 

08.11.13 09:15:22,000 kernel[0]: The USB device Keyboard Hub (Port 2 of Hub at 0x26000000) may have caused a wake by issuing a remote wakeup (2)

08.11.13 09:15:22,000 kernel[0]: The USB device Apple Keyboard (Port 2 of Hub at 0x26200000) may have caused a wake by issuing a remote wakeup (3)

 

As you can see, the hardware address (0x26000000) of the USB hub is different due to different hardware, but otherwise it is the same simple kernel information message.

I've already stated this fact many many times on here!!

The console logs are not exclusive to the late 2013 rMBP 13" hence it's most likely just a mavericks power saving thing, been saying it for my last few posts, this was solved before, y'all people need to start to listen.