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

okay, now I understood that "in google" thing, too.
Yes, that is normal behaviour. The google website uses JavaScript in order to make this happen. It's not a bug, it's a feature. (by google)

bro let me know after checking your brothers 15inch , that everythings cool . i dont know if i should buy it straight or wait for a new batch.

i mean in the google search field. but that seems to be normal as some people here say the same.

anyone has a command for me to blow everything away from my ssd before giving it back tomorrow ?

and i am still not sure, i did some intensive typing to test my keyboards pushing points (sorry i am german) and the macbook was at sleep during that. and right after the wake up the keyboard failed. again, it has never happend before and after a reboot everything is working just fine.

i really hope that this is not another bug in mavericks and thats just mine.

one more thing:

guys check out your arrow buttons at the bottom right on your keyboard, touch them soft and play a little with them, lick them if you want but then tell me how they feel !!! mine feel a little cheapy and they rattle when you touch them.

maybe do the same with space button and others, they feel different in my eyes.

anyone else having the same ? think its normal too. (still want to keep my book)

haha , just found out that the late 2013 15in retina has a sleep/wake crash problem not the trackpad/keyboard

What does this mean? after the EFI update?

11/8/13 9:00:00.003 AM com.apple.time[160]: Interval maximum value is 946100000 seconds (specified value: 9223372036854775807).

11/8/13 9:00:12.000 AM 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)

11/8/13 9:00:27.000 AM 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)

11/8/13 9:01:04.000 AM 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)

11/8/13 9:01:25.000 AM 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)

11/8/13 9:01:38.000 AM 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)

11/8/13 9:01:56.000 AM 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)

11/8/13 9:02:04.000 AM 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)

11/8/13 9:02:34.000 AM 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)

11/8/13 9:02:53.000 AM 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)

11/8/13 9:03:08.155 AM Console[754]: setPresentationOptions called with NSApplicationPresentationFullScreen when there is no visible fullscreen window; this call will be ignored.

11/8/13 9:03:39.000 AM 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)

11/8/13 9:03:59.000 AM 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)

The same messages appaers on my Macbook Pro 15" from 2010 with Mavericks. I am certain that it can't only be a hardware problem. It might be a combination of an hardware and software issue on the 13" and that's why so many entries appear on the 13" retina with haswell. And just to clear things up a little bit ... the console messages indeed can have the same timestamp when they occure within the same second. I reckon that Apple fixed the hardware issue with the efi update but the issue in mavericks might still exist. Only Apple knows....

And no this picture was not photosshoped whatsoever. I only used Skitch to pixelate the serial number.

RIVERSTALKER wrote:

 

(still want to keep my book)

I wouldn't in your case. Sounds too strange. Take it back tomorrow and order a new one online asap. In 6, 7 or 10 days you will have a brandnew one, without any strange sounds and feelings of the keyboard, without freezes and without the doubts whether something is wrong or not. (The last one is the most important anyway)

Only problem might be that it will probably take Apple a few days to transfer your money back to your bankaccount or creditcard. So unless you can afford it, you'd have to wait a few days for that to happen before ordering a new one. Still - this is what I would do.

satpak wrote:

 

What does this mean? after the EFI update?

 

11/8/13 9:00:00.003 AM com.apple.time[160]: Interval maximum value is 946100000 seconds (specified value: 9223372036854775807).

11/8/13 9:00:12.000 AM 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)

11/8/13 9:00:27.000 AM 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)

11/8/13 9:01:04.000 AM 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)

11/8/13 9:01:25.000 AM 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)

11/8/13 9:01:38.000 AM 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)

11/8/13 9:01:56.000 AM 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)

11/8/13 9:02:04.000 AM 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)

11/8/13 9:02:34.000 AM 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)

11/8/13 9:02:53.000 AM 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)

11/8/13 9:03:08.155 AM Console[754]: setPresentationOptions called with NSApplicationPresentationFullScreen when there is no visible fullscreen window; this call will be ignored.

11/8/13 9:03:39.000 AM 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)

11/8/13 9:03:59.000 AM 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)

It means that the system was awakened from a sleeping state by you either touching the touchpad or hitting a key on the keyboard. For debugging information, this gets written into the system.log. Just as many other information as well.

The EFI update fixes a bug. What you see in the console is no bug. It's debugging information from the kernel.

RIVERSTALKER wrote:

ok my keyboard just failed !!! and yeah i did the update !!! tryed to type in my password after sleep mode then just the right keyboard side worked. i restarted my mac, now it seems to be ok. i do not know how to find the error message in console because there are thousand of it.

just called apple munich and they told me to bring it back tomorrow and i will get my money back because there are no more 13" / 8 / 256 models available at the moment. i bought my book 17 days ago. so its ok for me but i am totaly dissapointed now of my first mac. i really tried to keep it but there are so many crazy things going on that i am happy to get my cash back. maybe i wait a month or two and give it another try.

i hope for everyone here that this has nothing to do with the new update or that kernel logs.

i really dont know what to do. maybe its just a little bug aswell and i have to spend a whole day tomorrow to bring my book back and finally i do not have a notebook anymore.

________________________________________________________________________________ ___________

out of stock of a brand new macbook for a normal and popular model = we stop selling this product first and fix it = product recall, could it be?

Got the EFI update, looking good so far. *Fingers crossed*.

Krakatau7 wrote:

 

________________________________________________________________________________ _______

out of stock of a brand new macbook = we stop selling this product first and fix it = product recall, could it be?

I'd assume a "let's do the EFI update on all devices before giving them to the customers".
If I were responible at Apple, I'd sure do that.

The alternative would be: "Here you go, customer, here is your brandnew beautiful and amazing macbook pro. Please make sure to make the EFI update as soon as possible, so your keyboard and touchpad will not freeze." These two sentences just don't go together very well, do they?

or exchanging the faulty hardware.. i hope surely it is only EFI Update fix..but there is also a possibility.. get really confused ;(

Krakatau7 wrote:

 

or exchanging the faulty hardware.. i hope surely it is only EFI Update fix..but there is also a possibility.. get really confused ;(

As Oli said they will want to get all the firmware updated on the current ones being sold in order to minimize the chance of people having a 'freeze up' prior to doing the first 'Software Update' on their mac, unless the 'Software Update' check is an automated part of the initial boot-up/registration process in which case it wouldn't be necessary to de-shelve them at their stores to do the firmware update.

I have my new rmbp 13" since 2 days ago, no single freeze since them but console full of USB wakes, i have not installed the fix because i want to know if my mac comes with faulty hardware. I really don't know what to do, because if i return my macbook and buy one new i really don't know if it will come with new hardware or fixed by software, this is anoying