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

aniebyls wrote:

 

Here is an update from a store in Palo Alto, California. I have just exchanged my MacBook Pro retina 13 Haswell: 13"/2.4/8GB/256GB for a second time. My previous two experienced the hang/unresponsiveness problem and it's been 2 weeks since my last exchange.

 

The Geniuses are aware of the problem but say that it is not wide spread. Apple has solde hundreds of thousands of MacBook Pros and only 2 thousand have reported problems on this forum. Kind of puts it in perspective. Anyway, so far i have not experienced any problems. This Mac is from a new batch that this store received a few days ago. I will let you know if problem happens on my #3 Mac.

I asked in a mac forum to all owners of a 13" rMBP to please tell me whether they had a freeze or not.
10 reported, they own a new Haswell 13" rMBP.

8 have had freezes
2  had used USB devices a lot, so you can't count them in.
So you can count this as 8 out of 8.
And by the way: none of them had reported here in the forum.

I think, a guess that 1 out of 100 people who experiences this problem would actually come to this forum and report, it would be a quite optimistic guess. (Most people just call the support and do not bother with a forum) I believe 1 out of 200 would be a little more realistic. To be honest, I think it is even less than that.
But let's take 1 out of 100.

100 * 2.000 would equal 200.000 affected devices. Out of how many sold exactly?

Yeah, I see your point about the perspective and all that. Not wide spread. Yep. Now I know why they are called "Geniuses"

 

errrrmmmmm..... if you look at the views of this forum its over 100,000.....

 

and its not like every single person who ever bought a macbook pro retina 13 late 2013... checked this exact forum....

 

so yes i think its a problem with every one made so far...

Yes agreed, some people will not even google it but just call apple then return their rMBP hence this thread being left out of the equation, others will see this thread read it and then return their rMBP without even bothering to comment out of the sake of mindless repetition.

Apple will only ever downplay this issue, even if there was a recall they would still downplay it yet again, they would just say that only few were recalled, no company especially Apple, being so vain, would ever admit such a blunder as this for what it really is.

Got my rMBP a little over a week ago. Only encountered 3 hangup's so far ( used everyday since). I cant say that usb stick works since max i use the mbp is about 1- 1 1/2 hours. I can however, say it does stop the error message in the console. Other than this issue, my copy is flawless

13" 2.4Ghz/16GB/256

aniebyls wrote:

 

Here is an update from a store in Palo Alto, California. I have just exchanged my MacBook Pro retina 13 Haswell: 13"/2.4/8GB/256GB for a second time. My previous two experienced the hang/unresponsiveness problem and it's been 2 weeks since my last exchange.

 

The Geniuses are aware of the problem but say that it is not wide spread. Apple has solde hundreds of thousands of MacBook Pros and only 2 thousand have reported problems on this forum. Kind of puts it in perspective. Anyway, so far i have not experienced any problems. This Mac is from a new batch that this store received a few days ago. I will let you know if problem happens on my #3 Mac.

errrrmmmmm..... if you look at the views of this forum its over 100,000.....

and its not like every single person who ever bought a macbook pro retina 13 late 2013... checked this exact forum....

so yes i think its a problem with every one made so far...

I have to agree with this person, somewhat, it is not h/w specific to 13"rMBP late 2013.  Mine is that one, and is 9 days old, I use the Apple Bt mouse, no hangs, I use the trackpad, hangs when using Safari in less than two minutes.  See my previous post about use cases, and how to work around until 'they' release something.   It is most likely a driver in Mavericks, and/or corner case with keyboard/trackpad chipset and drivers.  Others are seeing this on non-13"rMBPs, older machines back to 2012 actually.  So I think the fix will come in the form of a kernel patch and maybe some firmware for certain platforms.  IMHO (Computer Engineer for 32 years)

I wonder if there's a list of bugs that Mavericks 10.9.1 will fix somewhere.

still haveing issues here. this is such a pain. has anyone of importance heard if there is a fix in production?

same problem, bought it on the fourth at Yorkdale. I'm assuming it was a new batch because all the apple stores were out of stock and I had to call several days and finally got one when they had new available.

late 2013 rMBP model (8gb ram version)

Hi Oli,

You must be right. Apple must be downplaying this issue to avoid major PR problems. I have just experienced a hang/unresponsiveness problem on my 3rd MacBook Pro 13" Retina. I don't need any more convincing. If this issues is not fixed in two weeks I am not exchanging but returning it this time.

Here are the log file I captured from the moment of the freeze to when it woke up after I close the lid for 60 seconds or so:

11/6/13 2:53:50.000 PM 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/6/13 2:55:12.604 PM WindowServer[86]: _CGXSetWindowBackgroundBlurRadius: Invalid window 0xffffffff

11/6/13 2:55:12.604 PM loginwindow[64]: find_shared_window: WID -1

11/6/13 2:55:12.604 PM loginwindow[64]: CGSGetWindowTags: Invalid window 0xffffffff

11/6/13 2:55:12.604 PM loginwindow[64]: find_shared_window: WID -1

11/6/13 2:55:12.604 PM loginwindow[64]: CGSSetWindowTags: Invalid window 0xffffffff

11/6/13 2:55:12.924 PM WindowServer[86]: device_generate_desktop_screenshot: authw 0x7fbe32e42310(2000), shield 0x7fbe32ca08a0(2001)

11/6/13 2:55:12.961 PM WindowServer[86]: device_generate_lock_screen_screenshot: authw 0x7fbe32e42310(2000), shield 0x7fbe32ca08a0(2001)

11/6/13 2:55:20.000 PM kernel[0]: IOPMrootDomain: idle revert, state 21

11/6/13 2:55:20.936 PM WindowServer[86]: CGXDisplayDidWakeNotification [6185403281280]: posting kCGSDisplayDidWake

11/6/13 2:55:20.937 PM WindowServer[86]: handle_will_sleep_auth_and_shield_windows: Deferring.

11/6/13 2:55:27.154 PM WindowServer[86]: device_generate_desktop_screenshot: authw 0x7fbe32e42310(2004), shield 0x7fbe32ca08a0(2001)

11/6/13 2:55:27.191 PM WindowServer[86]: device_generate_lock_screen_screenshot: authw 0x7fbe32e42310(2004), shield 0x7fbe32ca08a0(2001)

11/6/13 2:55:36.608 PM loginwindow[64]: CoreAnimation: warning, deleted thread with uncommitted CATransaction; set CA_DEBUG_TRANSACTIONS=1 in environment to log backtraces.

11/6/13 2:55:47.000 PM kernel[0]: IOPMrootDomain: idle revert, state 21

11/6/13 2:55:47.879 PM WindowServer[86]: CGXDisplayDidWakeNotification [6212345979458]: posting kCGSDisplayDidWake

11/6/13 2:55:47.879 PM WindowServer[86]: handle_will_sleep_auth_and_shield_windows: Deferring.

11/6/13 2:55:56.130 PM WindowServer[86]: device_generate_desktop_screenshot: authw 0x7fbe32e42310(2000), shield 0x7fbe32ca08a0(2001)

11/6/13 2:55:56.171 PM WindowServer[86]: device_generate_lock_screen_screenshot: authw 0x7fbe32e42310(2000), shield 0x7fbe32ca08a0(2001)

11/6/13 2:55:59.000 PM kernel[0]: IOPMrootDomain: idle revert, state 21

11/6/13 2:55:59.512 PM loginwindow[64]: ERROR | -[LWBuiltInScreenLockAuthLion askForPasswordBuiltIn:] | Attempted to add an observer when already observing

11/6/13 2:55:59.862 PM WindowServer[86]: CGXDisplayDidWakeNotification [6224329019379]: posting kCGSDisplayDidWake

11/6/13 2:55:59.862 PM WindowServer[86]: handle_will_sleep_auth_and_shield_windows: Deferring.

11/6/13 2:56:05.616 PM loginwindow[64]: CoreAnimation: warning, deleted thread with uncommitted CATransaction; set CA_DEBUG_TRANSACTIONS=1 in environment to log backtraces.

11/6/13 2:56:05.666 PM WindowServer[86]: device_generate_desktop_screenshot: authw 0x7fbe32e42310(2004), shield 0x7fbe32ca08a0(2001)

11/6/13 2:56:05.705 PM WindowServer[86]: device_generate_lock_screen_screenshot: authw 0x7fbe32e42310(2004), shield 0x7fbe32ca08a0(2001)

11/6/13 2:56:15.562 PM loginwindow[64]: CoreAnimation: warning, deleted thread with uncommitted CATransaction; set CA_DEBUG_TRANSACTIONS=1 in environment to log backtraces.

11/6/13 2:56:24.000 PM kernel[0]: IOPMrootDomain: idle revert, state 21

11/6/13 2:56:24.666 PM WindowServer[86]: CGXDisplayDidWakeNotification [6249133164294]: posting kCGSDisplayDidWake

11/6/13 2:56:24.666 PM WindowServer[86]: handle_will_sleep_auth_and_shield_windows: Deferring.

11/6/13 2:56:33.559 PM loginwindow[64]: CoreAnimation: warning, deleted thread with uncommitted CATransaction; set CA_DEBUG_TRANSACTIONS=1 in environment to log backtraces.

11/6/13 2:56:43.008 PM WindowServer[86]: device_generate_desktop_screenshot: authw 0x7fbe32e42310(2000), shield 0x7fbe32ca08a0(2001)

11/6/13 2:56:43.049 PM WindowServer[86]: device_generate_lock_screen_screenshot: authw 0x7fbe32e42310(2000), shield 0x7fbe32ca08a0(2001)

11/6/13 2:56:55.480 PM WindowServer[86]: _CGXHWCaptureWindowList: No capable active display found.

11/6/13 2:56:57.102 PM WindowServer[86]: _CGXHWCaptureWindowList: No capable active display found.

11/6/13 2:56:57.593 PM loginwindow[64]: CoreAnimation: warning, deleted thread with uncommitted CATransaction; set CA_DEBUG_TRANSACTIONS=1 in environment to log backtraces.

11/6/13 2:57:07.000 PM kernel[0]: IOPMrootDomain: idle revert, state 21

11/6/13 2:57:07.238 PM loginwindow[64]: ERROR | -[LWBuiltInScreenLockAuthLion askForPasswordBuiltIn:] | Attempted to add an observer when already observing

11/6/13 2:57:07.587 PM WindowServer[86]: CGXDisplayDidWakeNotification [6292054745552]: posting kCGSDisplayDidWake

11/6/13 2:57:07.588 PM WindowServer[86]: handle_will_sleep_auth_and_shield_windows: Deferring.

11/6/13 2:57:30.784 PM loginwindow[64]: CoreAnimation: warning, deleted thread with uncommitted CATransaction; set CA_DEBUG_TRANSACTIONS=1 in environment to log backtraces.

11/6/13 2:57:36.112 PM WindowServer[86]: device_generate_desktop_screenshot: authw 0x7fbe32e42310(2004), shield 0x7fbe32ca08a0(2001)

11/6/13 2:57:36.154 PM WindowServer[86]: device_generate_lock_screen_screenshot: authw 0x7fbe32e42310(2004), shield 0x7fbe32ca08a0(2001)

11/6/13 2:58:06.000 PM kernel[0]: PM notification timeout (pid 1022, Messages)

11/6/13 2:58:06.000 PM kernel[0]: AppleCamIn::systemWakeCall - messageType = 0xE0000340

11/6/13 2:58:06.000 PM kernel[0]: AppleCamIn::systemWakeCall - messageType = 0xE0000340

11/6/13 2:58:07.000 PM kernel[0]: AppleCamIn::systemWakeCall - messageType = 0xE0000280

11/6/13 2:58:07.000 PM kernel[0]: ARPT: 6352.358727: AirPort_Brcm43xx::powerChange: System Sleep

11/6/13 2:58:07.000 PM kernel[0]: ARPT: 6352.358734: wl0: powerChange: *** BONJOUR/MDNS OFFLOADS ARE NOT RUNNING.

11/6/13 2:58:07.000 PM kernel[0]: AppleCamIn::systemWakeCall - messageType = 0xE0000340

11/6/13 2:58:07.000 PM 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/6/13 2:58:08.000 PM kernel[0]: **** [IOBluetoothHostControllerUSBTransport][SuspendDevice] -- Resume -- suspendDeviceCallResult = 0x0000 (kIOReturnSuccess) -- 0x5000 ****

11/6/13 2:58:08.000 PM kernel[0]: en0: BSSID changed to 74:9d:dc:ca:43:f9

11/6/13 2:58:08.000 PM kernel[0]: ARPT: 6352.943895: scanparams:

11/6/13 2:58:08.000 PM kernel[0]: ARPT: 6352.943897:   flags 0

11/6/13 2:58:08.000 PM kernel[0]: ARPT: 6352.943899:   active_time 0, passive_time 0

11/6/13 2:58:08.000 PM kernel[0]: ARPT: 6352.943901:   scan_start_delay 0

11/6/13 2:58:08.000 PM kernel[0]: ARPT: 6352.943903:   scan_cycle_idle_rest_time 0, scan_cycle_idle_rest_time_multiplier 0

11/6/13 2:58:08.000 PM kernel[0]: ARPT: 6352.943906:   max_scan_cycles 0, max_rest_time 0

11/6/13 2:58:08.000 PM kernel[0]: ARPT: 6352.943908: Scan Channels (0): None

11/6/13 2:58:08.000 PM kernel[0]: ARPT: 6352.943910: SSID (0): None

11/6/13 2:58:08.000 PM kernel[0]: ARPT: 6352.943912: SSID count = 0

11/6/13 2:58:08.000 PM kernel[0]: ARPT: 6352.943914: wl0: leaveModulePoweredForOffloads: Wi-Fi will turn off.

11/6/13 2:58:08.000 PM kernel[0]: Bluetooth -- LE is supported - Disable LE meta event

11/6/13 2:58:08.000 PM kernel[0]: AppleThunderboltNHI::prePCIWake - power up complete - took 1484 us

11/6/13 2:58:08.000 PM kernel[0]: AppleThunderboltHAL::earlyWake - complete - took 0 milliseconds

11/6/13 2:58:08.000 PM kernel[0]: wlEvent: en0 en0 Link DOWN virtIf = 0

11/6/13 2:58:08.000 PM kernel[0]: AirPort: Link Down on en0. Reason 8 (Disassociated because station leaving).

11/6/13 2:58:08.000 PM kernel[0]: **** [IOBluetoothHostControllerUSBTransport][SuspendDevice] -- Suspend -- suspendDeviceCallResult = 0x0000 (kIOReturnSuccess) -- 0x5000 ****

11/6/13 2:58:08.000 PM kernel[0]: IOThunderboltSwitch<0xffffff801d3b2a00>(0x0)::listenerCallback - Thunderbolt HPD packet for route = 0x0 port = 11 unplug = 0

11/6/13 2:58:08.000 PM kernel[0]: IOThunderboltSwitch<0xffffff801d3b2a00>(0x0)::listenerCallback - Thunderbolt HPD packet for route = 0x0 port = 12 unplug = 0

11/6/13 2:58:09.000 PM kernel[0]: AppleCamIn::systemWakeCall - messageType = 0xE0000340

11/6/13 2:58:09.000 PM kernel[0]: AppleThunderboltNHIType2::waitForOk2Go2Sx - retries = 9

11/6/13 2:58:09.000 PM kernel[0]: AppleThunderboltNHI::prePCIWake - power up complete - took 0 us

11/6/13 2:58:20.000 PM kernel[0]: Wake reason: EC.LidOpen (User)

11/6/13 2:58:20.000 PM kernel[0]: AppleCamIn::systemWakeCall - messageType = 0xE0000320

11/6/13 2:58:20.000 PM kernel[0]: AppleCamIn::systemWakeCall - messageType = 0xE0000340

11/6/13 2:58:20.000 PM kernel[0]: AppleCamIn::wakeEventHandlerThread

11/6/13 2:58:20.000 PM kernel[0]: Previous Sleep Cause: 5

11/6/13 2:58:20.000 PM kernel[0]: AppleThunderboltNHI::prePCIWake - power up complete - took 59836 us

11/6/13 2:58:20.000 PM kernel[0]: AppleThunderboltHAL::earlyWake - complete - took 1 milliseconds

11/6/13 2:58:20.000 PM kernel[0]: AppleUSBMultitouchDriver::validateChecksum - 64-byte packet checksum is incorrect (expected 0xac0, checksum bytes were 0x534)

11/6/13 2:58:20.000 PM kernel[0]: TBT W (2): 0x0040 [x]

11/6/13 2:58:20.000 PM kernel[0]: IOThunderboltSwitch<0xffffff801d3b2a00>(0x0)::listenerCallback - Thunderbolt HPD packet for route = 0x0 port = 11 unplug = 0

11/6/13 2:58:20.000 PM kernel[0]: IOThunderboltSwitch<0xffffff801d3b2a00>(0x0)::listenerCallback - Thunderbolt HPD packet for route = 0x0 port = 12 unplug = 0

11/6/13 2:58:20.000 PM kernel[0]: **** [IOBluetoothHostControllerUSBTransport][SuspendDevice] -- Resume -- suspendDeviceCallResult = 0x0000 (kIOReturnSuccess) -- 0x5000 ****

11/6/13 2:58:20.000 PM kernel[0]: AppleUSBMultitouchDriver::checkStatus - received Status Packet, Payload 2: device was reinitialized

11/6/13 2:58:20.305 PM hidd[69]: MultitouchHID: device bootloaded

11/6/13 2:58:20.403 PM WindowServer[86]: CGXDisplayDidWakeNotification [6354824734061]: posting kCGSDisplayDidWake

11/6/13 2:58:20.404 PM WindowServer[86]: handle_will_sleep_auth_and_shield_windows: Reordering authw 0x7fbe32e42310(2000) (lock state: 3)

11/6/13 2:58:20.404 PM WindowServer[86]: handle_will_sleep_auth_and_shield_windows: err 0x0

11/6/13 2:58:20.430 PM loginwindow[64]: ERROR | -[LWBuiltInScreenLockAuthLion askForPasswordBuiltIn:] | Attempted to add an observer when already observing

11/6/13 2:58:20.000 PM kernel[0]: ARPT: 6354.900588: si_survive_perst_war: bar0win before 18003000, bar0win after 18001000

11/6/13 2:58:20.000 PM kernel[0]: en0: 802.11d country code set to 'X0'.

11/6/13 2:58:20.000 PM kernel[0]: en0: Supported channels 1 2 3 4 5 6 7 8 9 10 11 12 13 36 40 44 48 52 56 60 64 100 104 108 112 116 120 124 128 132 136 140 144 149 153 157 161 165

11/6/13 2:58:20.000 PM kernel[0]: ARPT: 6354.904470: AirPort_Brcm43xx::powerChange: System Wake - Full Wake/ Dark Wake / Maintenance wake

11/6/13 2:58:20.000 PM kernel[0]: AppleCamIn::systemWakeCall - messageType = 0xE0000340

11/6/13 2:58:20.000 PM kernel[0]: AppleCamIn::wakeEventHandlerThread

11/6/13 2:58:20.000 PM kernel[0]: AppleCamIn::systemWakeCall - messageType = 0xE0000300

11/6/13 2:58:20.492 PM configd[18]: setting hostname to "Aleksanders-MacBook-Pro.local"

11/6/13 2:58:20.501 PM configd[18]: network changed: v4(en0-:192.168.1.82) DNS- Proxy-

11/6/13 2:58:20.502 PM UserEventAgent[11]: Captive: CNPluginHandler en0: Inactive

11/6/13 2:58:20.555 PM netbiosd[151]: network_reachability_changed : network is not reachable, netbiosd is shutting down

11/6/13 2:58:21.000 PM kernel[0]: en0: 802.11d country code set to 'US'.

11/6/13 2:58:21.000 PM kernel[0]: en0: Supported channels 1 2 3 4 5 6 7 8 9 10 11 36 40 44 48 52 56 60 64 100 104 108 112 116 120 124 128 132 136 140 144 149 153 157 161 165

11/6/13 2:58:21.000 PM kernel[0]: ARPT: 6356.345103: MacAuthEvent en0   Auth result for: 74:9d:dc:ca:43:f9  MAC AUTH succeeded

11/6/13 2:58:21.000 PM kernel[0]: wlEvent: en0 en0 Link UP virtIf = 0

11/6/13 2:58:21.000 PM kernel[0]: AirPort: Link Up on en0

11/6/13 2:58:21.000 PM kernel[0]: en0: BSSID changed to 74:9d:dc:ca:43:f9

11/6/13 2:58:21.000 PM kernel[0]: AirPort: RSN handshake complete on en0

11/6/13 2:58:22.007 PM UserEventAgent[11]: Captive: [CNInfoNetworkActive:1655] en0: SSID '2WIRE482' making interface primary (cache indicates network not captive)

11/6/13 2:58:22.008 PM configd[18]: network changed: DNS* Proxy

11/6/13 2:58:22.008 PM UserEventAgent[11]: Captive: CNPluginHandler en0: Evaluating

11/6/13 2:58:22.008 PM UserEventAgent[11]: Captive: en0: Not probing '2WIRE482' (cache indicates not captive)

11/6/13 2:58:22.009 PM UserEventAgent[11]: Captive: CNPluginHandler en0: Authenticated

11/6/13 2:58:22.018 PM configd[18]: network changed: v4(en0!:192.168.1.82) DNS+ Proxy+ SMB

11/6/13 2:58:22.038 PM configd[18]: setting hostname to "unknownb8e85631396e"

11/6/13 2:58:22.000 PM kernel[0]: flow_divert_kctl_disconnect (0): disconnecting group 1

11/6/13 2:58:25.000 PM kernel[0]: AppleCamIn::handleWakeEvent_gated

11/6/13 2:58:25.000 PM kernel[0]: AppleCamIn::handleWakeEvent_gated

11/6/13 2:58:28.028 PM loginwindow[64]: CoreAnimation: warning, deleted thread with uncommitted CATransaction; set CA_DEBUG_TRANSACTIONS=1 in environment to log backtraces.

11/6/13 2:58:28.742 PM CalendarAgent[335]: [com.apple.calendar.store.log.ICS] [ICS Error for file: BEGIN:VTIMEZONE

TZID:America/Los_Angeles

X-LIC-LOCATION:America/Los_Angeles

BEGIN:DAYLIGHT

TZOFFSETFROM:-0800

TZOFFSETTO:-0700

TZNAME:PDT

DTSTART:19700308T020000

RRULE:FREQ=YEARLY;BYMONTH=3;BYDAY=2SU

END:DAYLIGHT

BEGIN:STANDARD

TZOFFSETFROM:-0700

TZOFFSETTO:-0800

TZNAME:PST

DTSTART:19701101T020000

RRULE:FREQ=YEARLY;BYMONTH=11;BYDAY=1SU

END:STANDARD

END:VTIMEZONE

]

11/6/13 2:58:28.743 PM CalendarAgent[335]: [com.apple.calendar.store.log.ICS] [ICS: Cal not a ICSCalendar *nil description*]

11/6/13 2:58:28.744 PM CalendarAgent[335]: [com.apple.calendar.store.log.ICS] [ICS Error for file: BEGIN:VTIMEZONE

TZID:America/Los_Angeles

X-LIC-LOCATION:America/Los_Angeles

BEGIN:DAYLIGHT

TZOFFSETFROM:-0800

TZOFFSETTO:-0700

TZNAME:PDT

DTSTART:19700308T020000

RRULE:FREQ=YEARLY;BYMONTH=3;BYDAY=2SU

END:DAYLIGHT

BEGIN:STANDARD

TZOFFSETFROM:-0700

TZOFFSETTO:-0800

TZNAME:PST

DTSTART:19701101T020000

RRULE:FREQ=YEARLY;BYMONTH=11;BYDAY=1SU

END:STANDARD

END:VTIMEZONE

]

11/6/13 2:58:28.744 PM CalendarAgent[335]: [com.apple.calendar.store.log.ICS] [ICS: Cal not a ICSCalendar *nil description*]

11/6/13 2:58:28.744 PM CalendarAgent[335]: [com.apple.calendar.store.log.ICS] [ICS Error for file: BEGIN:VTIMEZONE

TZID:America/Los_Angeles

X-LIC-LOCATION:America/Los_Angeles

BEGIN:DAYLIGHT

TZOFFSETFROM:-0800

TZOFFSETTO:-0700

TZNAME:PDT

DTSTART:19700308T020000

RRULE:FREQ=YEARLY;BYMONTH=3;BYDAY=2SU

END:DAYLIGHT

BEGIN:STANDARD

TZOFFSETFROM:-0700

TZOFFSETTO:-0800

TZNAME:PST

DTSTART:19701101T020000

RRULE:FREQ=YEARLY;BYMONTH=11;BYDAY=1SU

END:STANDARD

END:VTIMEZONE

]

11/6/13 2:58:28.745 PM CalendarAgent[335]: [com.apple.calendar.store.log.ICS] [ICS: Cal not a ICSCalendar *nil description*]

11/6/13 2:58:28.745 PM CalendarAgent[335]: [com.apple.calendar.store.log.ICS] [ICS Error for file: BEGIN:VTIMEZONE

TZID:America/Los_Angeles

X-LIC-LOCATION:America/Los_Angeles

BEGIN:DAYLIGHT

TZOFFSETFROM:-0800

TZOFFSETTO:-0700

TZNAME:PDT

DTSTART:19700308T020000

RRULE:FREQ=YEARLY;BYMONTH=3;BYDAY=2SU

END:DAYLIGHT

BEGIN:STANDARD

TZOFFSETFROM:-0700

TZOFFSETTO:-0800

TZNAME:PST

DTSTART:19701101T020000

RRULE:FREQ=YEARLY;BYMONTH=11;BYDAY=1SU

END:STANDARD

END:VTIMEZONE

]

11/6/13 2:58:28.746 PM CalendarAgent[335]: [com.apple.calendar.store.log.ICS] [ICS: Cal not a ICSCalendar *nil description*]

11/6/13 2:59:00.000 PM kernel[0]: **** [IOBluetoothHostControllerUSBTransport][SuspendDevice] -- Suspend -- suspendDeviceCallResult = 0x0000 (kIOReturnSuccess) -- 0x5000 ****

11/6/13 2:59:09.000 PM 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)

its now a software or a hardware issue?

I just got my mbp 13 a few days ago and had one freeze!

I connected my microsoft mouse and a few seconds later my keyboard and mouse were unresponsible,but Ableton Live didnt stop playing in the background.

Its better to give my mbp back or wait for an update?

Wait. All signs point towards software. I know you can't possibly read 125 pages...

Quick summary:

Plug in a USB 2.0 to a port. It takes away the error message in your console and you'll have no freezes (I've done this for the past 8 days with no freezes at all...)

Apple is aware and working. While they have not confirmed software officially, rumors are that "Dave from Apple" (ie. Senior Advisors) at Apple have made that statement via chat and on the phone.

Anyone who is claiming that it is an issue with the C1 Chip has old news and is essentially screaming that the sky is falling.

Also, click Oli.s72's username and go back and read his comments. It will give you a lot of information that will ease your mind.

gabry21

its now a software or a hardware issue?

I just got my mbp 13 a few days ago and had one freeze!

I connected my microsoft mouse and a few seconds later my keyboard and mouse were unresponsible,but Ableton Live didnt stop playing in the background.

Its better to give my mbp back or wait for an update?

@gabry21  Is your MSFT mouse and keybaord USB based or Bt?  If USB, thoughts are you wil see same issues as MBP keyboard/trackpad, they share the same USB busses.  Try a Bt mouse keybaord if you have one.  Temporary fix I have used is to close the lid, light sleep, for 30-60 secs. then re-open.  Machine will be un-frozen.  This is my experience with 1 week old 13" rMBP 8GB, 256GB SSD.  When I use a Bt APPLE mouse I have no hangs at all.  Use trackpad, and it hangs within a couple of minutes always in Safari.  Closing lid, wait 30-60 secs. clears the problem temporarily.

aniebyls wrote:

 

Hi Oli,

 

You must be right. Apple must be downplaying this issue to avoid major PR problems. I have just experienced a hang/unresponsiveness problem on my 3rd MacBook Pro 13" Retina. I don't need any more convincing. If this issues is not fixed in two weeks I am not exchanging but returning it this time.

 

Here are the log file I captured from the moment of the freeze to when it woke up after I close the lid for 60 seconds or so:

 

Haha I knew you'd be back soon, keep seeing people come on here all hyped as they've just got their replacement rMBP and they think all that plagued them before will have disappeared into thin air, I've been saying that Apple are downplaying it for the last week, just wish people would start to listen.

Send the piece of garbage back as the more send backs they get the faster they will be at sorting this out for those who haven't sent theirs back!

it looks to be software bug as people i know with old mac books and even imacs that updated had the same issue

my MBP no lock up for 3 days so far... but has the error messages in log.

I have a 13" Macbook, 256 GB, 16 GB, i7 in transit from China as we speak. It will be arriving on Friday. I have been following this thread since it started (yes, I've read all postings) and I must say that I am a bit disturbed that Apple has not released more specifics about the issue since Oct 30. I mean, when you do an Internet search regarding the new macbooks, a significant portion of the major players who usually show support for Apple are indicating that a fix is imminent while at the same time making note of glitches in several applications included with the Mavericks OS. If I was on the testing line of this product, I would be worried about a layoff.

Really too bad, as like most folks, I waited several months for this version of the Macbook Pro. I feel the longer Apple delays, the worst it is going to be for them to save face. I hope that by the time I pick up my notebook, there will be some more answers from Apple. In the meantime, I am really grateful for the information and testing the members in this discussion have done to try to remedy this issue.

Shepp...