iMac 27" 5k Beachball After Sleep

Discussion in 'OS X El Capitan (10.11)' started by altan, May 18, 2016.

  1. altan, May 18, 2016
    Last edited: May 18, 2016

    altan macrumors newbie

    Joined:
    May 18, 2016
    #1
    I saw this a few times prior to upgrading to 10.11.5, but it has happened twice now.

    iMac 27" (Retina 5K, 27-inch, Late 2015)) goes to sleep...

    I wake it up, it wakes up and presents me with the login (I need to select the user and enter the password).

    When I enter the password, it goes to "stuck beachball". One time it did this and recovered after 10 minutes, just recently it did it and after 45 minutes it was still balling... So I was forced to hard power it via the power button on the bottom left.

    While it is balling, I can ping it. It is also generating logs in the console. I can ever access the HD remotely.

    Ugh! Quite frustrating, Apple.

    Anyone have any thoughts?


    Oh, BTW, I got this Mac a few months ago have an intentionally not installed any crap on it. It doesn't have flash, it doesn't have VMware Fusion, it's basically clean with the exception of the Office suite and some other apps. No kernel extensions.


    Oh, when in this state there is usually an email notification in the upper right. I can move the cursor and the cursor moves (it is a ball). If I move it over the notification area, it turns into a regular pointer. However, clicking performs no action.
     
  2. JohnDS macrumors 65816

    Joined:
    Oct 25, 2015
    #2
    What is in the console logs for when it is beach balling?

    Also, can you access Activity Monitor?
     
  3. altan thread starter macrumors newbie

    Joined:
    May 18, 2016
    #3
    John, Thanks for following up. I didn't think the console showed anything interesting, but I should have included it.

    Around 6:03 was when I pressed a key on the keyboard. It was beach balling the entire time of this log (I provided about 25 minutes of the console)

    5/16/16 6:03:53.179 PM ntpd[201]: wake time set -0.631260 s
    5/16/16 6:04:35.000 PM kernel[0]: pci pause: SDXC
    5/16/16 6:04:50.000 PM kernel[0]: [AppleHSBluetoothDevice][getExtendedReport] Could not retrieve information for BatteryPercent feature
    5/16/16 6:04:50.000 PM kernel[0]: [AppleHSBluetoothDevice][updateBatteryLevel] Couldn't get battery percentage from device
    5/16/16 6:04:50.000 PM kernel[0]: [AppleHSBluetoothDevice][getExtendedReport] Could not retrieve information for BatteryPercent feature
    5/16/16 6:04:50.000 PM kernel[0]: [AppleHSBluetoothDevice][updateBatteryLevel] Couldn't get battery percentage from device
    5/16/16 6:05:04.008 PM Mail[448]: No worthy mechs found
    5/16/16 6:05:04.008 PM Mail[448]: No worthy mechs found
    5/16/16 6:05:04.594 PM Mail[448]: No worthy mechs found
    5/16/16 6:05:04.594 PM Mail[448]: No worthy mechs found
    5/16/16 6:06:17.000 PM kernel[0]: IOPMrootDomain: idle cancel, state 1
    5/16/16 6:06:50.465 PM Safari[556]: tcp_connection_tls_session_error_callback_imp 1134 __tcp_connection_tls_session_callback_write_block_invoke.434 error 22
    5/16/16 6:07:27.000 PM kernel[0]: PM response took 1005 ms (55, powerd)
    5/16/16 6:07:27.000 PM kernel[0]: ARPT: 257574.579734: AirPort_Brcm43xx::powerChange: System Sleep
    5/16/16 6:07:28.000 PM kernel[0]: ARPT: 257575.081853: IOPMPowerSource Information: onSleep, SleepType: Normal Sleep,
    5/16/16 6:07:28.000 PM kernel[0]: ARPT: 257575.081881: wl0: powerChange: *** BONJOUR/MDNS OFFLOADS ARE NOT RUNNING.
    5/16/16 6:27:05.000 PM kernel[0]: en1: channel changed to 1
    5/16/16 6:27:05.000 PM kernel[0]: AirPort: Link Down on awdl0. Reason 1 (Unspecified).
    5/16/16 6:27:05.000 PM kernel[0]: AppleThunderboltNHIType2::prePCIWake - power up complete - took 4 us
    5/16/16 6:27:05.000 PM kernel[0]: AppleThunderboltGenericHAL::earlyWake - complete - took 0 milliseconds
    5/16/16 6:27:05.000 PM kernel[0]: ARPT: 257576.268492: wl0: leaveModulePoweredForOffloads: Wi-Fi will stay on.
    5/16/16 6:27:05.000 PM kernel[0]: ARPT: 257576.268532: AirPort_Brcm43xx::syncPowerState: WWEN[disabled]
    5/16/16 6:27:05.000 PM kernel[0]: 257576.269436 HS04@14300000: AppleUSBHostPort::setPowerStateGated: kPowerStateOn -> kPowerStateSleep
    5/16/16 6:27:05.000 PM kernel[0]: 257576.269453 HS04@14300000: AppleUSB20XHCIPort::suspend:
    5/16/16 6:27:05.000 PM kernel[0]: 257576.269455 HS04@14300000: AppleUSBXHCIPort::suspend:
    5/16/16 6:27:05.000 PM kernel[0]: AppleBCM5701Ethernet [en0]: Link down (womp enabled, proxy 1069)
    5/16/16 6:27:05.000 PM kernel[0]: IOThunderboltSwitch<0>(0x0)::listenerCallback - Thunderbolt HPD packet for route = 0x0 port = 11 unplug = 0
    5/16/16 6:27:05.000 PM kernel[0]: AppleBCM5701Ethernet [en0]: 0 0 memWrInd fBJP_Wakeup_Timer
    5/16/16 6:07:30.000 PM kernel[0]: AppleThunderboltNHIType2::waitForOk2Go2Sx - intel_rp = 1 dlla_reporting_supported = 1
    5/16/16 6:27:05.000 PM kernel[0]: AppleThunderboltNHIType2::waitForOk2Go2Sx - retries = 4209
    5/16/16 6:27:05.000 PM kernel[0]: Wake reason: XHC1 GIGE (Network)
    5/16/16 6:27:05.000 PM kernel[0]: RTC: PowerByCalendarDate setting ignored
    5/16/16 6:27:05.000 PM syslogd[46]: ASL Sender Statistics
     
  4. JohnDS macrumors 65816

    Joined:
    Oct 25, 2015
    #4
    Looks like there may be a problem with a wireless keyboard or mouse. Are you using either? Perhaps a low battery?

    Check out the batteries on your wireless mouse and keyboard.

    Also, try resetting the SMC: https://support.apple.com/en-ca/HT201295

    Finally, leave Activity Monitor open and sort the column by the "% CPU" column. See if one particular activity shows a high CPU utilization when the beach ball appears.
     
  5. altan thread starter macrumors newbie

    Joined:
    May 18, 2016
    #5
    Thanks again.

    I cannot access activity monitor because the screen shows the login screen with the beachball.

    Keyboard and mouse work fine (I did see that odd message in the log thought). Both have battery > 50%.

    I hate resetting things randomly, but I suppose it cannot hurt.
     
  6. fbk macrumors newbie

    fbk

    Joined:
    May 22, 2017
    #6
    The log seems to indicate something related to Airport.
     

Share This Page