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

Just thinking further about this... I guess it would be nice to know some of the basic parameters about how these macbooks and the OS X manage power...

e.g. how long until the keyboard/trackpad/associated "system" goes into sleep to save power - is it 1 millisecond? 1 second? 3 seconds? 5 seconds? or what?

and yer.. basically what the log message "may have caused a wake my issuing a remote wakeup" means exactly!

if it issues a "remote wakeup" every time it's used, that doesn't necessarily imply the system is in a "sleep" state, it may just imply that it issues a "remote wakeup" so that IF the system is in a sleep state it wakes up.. shrug

again, i realise this sort of information may be beyond what a "normal" user may want/wish to know.. but i personally am interested

What I am worrying about is it is a hardware issue but Apple hides it using software.

Apple needs to give some explanation.

Just wondering if anyone with some technical knowledge can answer my question about power management.. after what duration does the keyboard/trackpad go into power saving?

I've never used a mac before but was just looking at some technical stuff in the mac developer library but don't have hours on end to school myself on technical details :-) It seems you can bring this sort of information up on screen in the I/O Registry Explorer? Does this I/O registry explorer still exist in Mavericks?

Funny story:  yesterday morning after constant freezes I decided to clean out the laptop and return to Bestbuy.  That was at about noon eastern time, just to come home a couple of hours later to see they released an update!  Murphy's Law for me! Chuckled after that, seriously should of returned a week ago for an earlier release! Anyway I looked today for available stock at Bestbuys in my area (there are at least 20) and incredibly there is NOT ONE AVAILABLE in the 13"!   I think Bestbuy pulled them all from their shelves to apply the update.  Pretty interesting! Anyway I'll be repurchasing once they're back in stock but I'm still going to follow this forum so PLEASE post if there are any issues, thanks for all the info!

Hi (used to be IPad3_screwdagain), soon to be CloudGT.  The thought police, finally caught up with me on that alias, after 1.5 years; they're a little slow, and apparently the blog scraper that determines what's acceptable and 'non-offensive' is a little buggy; see the picture I posted last night. 

The pre-EFI console messages may or may not, as it turns out, be related to the USB trackpad based freezes.  I consider the messages(apple calls them system.log messages), to be verbose because everytime you touch the trackpad it generates a log entry; and I know why so please don't anyone tell me why.  Why it's so verbose, only the mind of the developer(s), perhaps they compiled with the messages flag still set for a verbose debugging level, only they can know. The logs truncate and are gzipped on a regular basis, look in /var/log/ for system.log and it's rotation logs with a .gz extension.  These are the logs from the kernel, related to all things kernel.  Don't worry about them, other than perhaps how much precious and expensive SSD storage they are going to use over time; and that can can be addressed by deleting the ones with .gz extensions if it gets out of control for you.  After 10 days of having this 13" rMBP, my logs total about 2MB, I'm not going to lose sleep over that, or bother writing anymore about it!  Then again, I don't get as many because I use an Apple Bt mouse exclusively when at home or work.  The pre-EFI 13"rMBPs were stable when using an Apple Blutooth mouse, I posted this at least a dozen times, and no one paid much attention to the workaround.   Apple, firmware engineering in particular, worked their collective butts off and cranked out a fix yesterday at around high Noon PST.  I and several thousand others have installed the update and are having no further issues related to the original problem of apparent freezes, actually the machines were still running; the human interfaces(keybaord and trackpad) were unresponsive.  I like my rMBP, but I don't care for the censour that I've been experiencing on this forum by the forum thought police.  That is being addressed at a Sr. Mgt. level, since I've been assoicated with Apple in several ways since 1988.  Wozz and I used to enjoy breakfast toghether, occasionally, in Sartoga in the late '80s, great pancake joint, OPH.  And I was speaking with Steve Jobs and Peter Oppenheimer in 2009, regarding having the iPad equiped with active/passive RFID sensors for something my company, at the time, was engaged in; they didn't have the realestate in the iPad1 to do it.  As for the ghosting, I haven't seen this, and don't care to read about it, sorry.

<Edited By Host>

Yo, I'm back, this time with yet another ID.    How many does he have?  No one, paricularly the thought police, really knows for sure...  Someday Apple will have true SSO.  This post is to annoy the thought police only...  Go ahead and delete it, I double dare ya.  You know what's going on in Cupertino, right?!  I don't like being censored, as I have pointed out to them in terms their attorney's will understand very clearly.  It's un-American!  Oh yeah, and illegal.  Don't anyone point to the usage agreement.  No US based corporation or government entity may impose regulations or policies that violate Constitutional laws, period!

WOW, I'm slim shady btw ...

Net-net:  the 13" rMBP FIRMWARE (aka EFI update) is working well for me after 32 hours, no unresponsive trackpad.  I think they nailed it!  Good job f/w engineering and sustaining.  AND if you don't want to see your logs, who cares, fill up with USB kernel 'wakeup' messages, use a Bt mouse from Apple or others, anyone but MSFT.  K?

I am only going to say this one more time.  Firmware is specfically designed to be modified, since it's REEAALLY hard to go around and solder new components on the user's machines once they're in the wild.  Are you familair with FPGA technology, it is specifically designed to take on different base functions, on the fly, by flashing it with new f/w?   For example you can turn a CIFS head into an NFS head, or even a RESTful head, on the fly.  These USB chipsets are not FPGAs, that's for the trolls that were getting ready to pounce.  Point is, there IS NO HARDWARE BUG!!!!  See the picture I sent last night for further thoughts on this topic, now under a cute little anagram alias, Hindi actually, that someone with the thought police thought would be cute, I'm not amused BTW, see earlier post by me, zpimrdas.

I called two apple retail stores, 13inch are still selling, they won't open the package and do the upgrade, it once sealed and left the factory it will not be open until sold.

I also confirmed 13in MBP in the store also has the error log, lucky one of the MBP running under admin account so I able to see it.

Another mid 2013 13inch MBA haswell CPU doesn't has any similar log at all.

The log message is mainly happen in 13 MBP, someone report on theirs early MBA but it's only 1 or 2 entry which isn't look so unusual.

Their advisor suggested to return it and get a new one.

Your post is jibberish...  Does not compute....  interpreterd exiting (Code -1)  stack overlfow...

Looks like the thought police found my little picture of SLJ, AFTER I told them where it was...

What's this, the 13" rMBP has a trackpad that becomes unreponsive, clearly a h/w problem! 

Oh wait that guy dinoiphone seems to really know what he's talking about....

That sTronic guy, what's his problem?

glpfountz wrote:

 

I had the same problem (hanging at the create a computer account screen) with my new MBR 13".  Worked with Apple, they even sent me a new macbook, same problem.  Turns out, all I had to do was turn off wifi and everything worked fine.  Then afterwards, attach to wifi and put in my icloud and itunes credentials.  The tech suspect that my Verizon DSL was blocking a port / protocol causing the hang.

thanks for you post, i feel a bit less "cast away"