Excessive Wakeups

Sorry John, but this issue has been ongoing since Mavericks was released. It is only recently that people have known how to even diagnose the issue, much less articulate the jargon.It is entirely appropriate and helpful to continue the thread, rather than start up a new thread each and every time somebody has the exact same issue.

Model Identifier: MacBookPro10,1

System Version: OS X 10.9.4 (13E28)

Kernel Version: Darwin 13.3.0

Time since boot: 16 days 15:34

Log

Oct 1 08:35:59 IOPPF: Sent gpu-internal-plimit-notification last value 6 (rounded time weighted average 2)

Oct 1 18:51:05 process launchservicesd[70] caught causing excessive wakeups. Observed wakeups rate (per sec): 17914; Maximum permitted wakeups rate (per sec): 150; Observation period: 300 seconds; Task lifetime number of wakeups: 157797

Oct 1 18:52:01 Sound assertion in AppleHDAFunctionGroup at line 1057

Oct 1 19:00:49 process iPhoto[97546] caught causing excessive wakeups. Observed wakeups rate (per sec): 235; Maximum permitted wakeups rate (per sec): 150; Observation period: 300 seconds; Task lifetime number of wakeups: 67328

Oct 1 19:33:57 process iPhoto[97875] caught causing excessive wakeups. Observed wakeups rate (per sec): 199; Maximum permitted wakeups rate (per sec): 150; Observation period: 300 seconds; Task lifetime number of wakeups: 45010

Oct 1 20:52:06 IOPPF: Sent cpu-plimit-notification last value 17 (rounded time weighted average 17)

I thought this might be an older OS issue, but saw Evan McM's post, he is running Sierra. So this problem is pervasive across all of OS X version. I am running down the rabbit hole of Excessive Wakeups to see if it is the cause of the Sleep Wake problems I am having

kernel[0]: Restarting to collect Sleep wake debug logs

My Machine(s)

I am running a MBP (Mid-2015) with El Capitan 10.11.6 and Parallels 11. This machine is the only one of my three MBP that has this problem. The others are Mid-2012 and Mid-2014 running Sierra and Yosemite, respectively. All machines run Parallels.

Sleep Wake problem

My problems started about two weeks ago. I normally leave my machine in the office overnight. Now, I come in the mornings and find my machine black screen'd and unresponsive. Even the touchpad is dead. The machine is still ON, as I must push the power button for 5 seconds to get it o turn OFF.

Upon boot, I get the standard error popup noting the machine rebooted. I add a couple notes and send it on to Apple. This is their message content:

Date/Time: 2017-10-04 08:41:06 -0400

OS Version: Mac OS X 10.11.6 (Build 15G1611)

Architecture: x86_64h

Report Version: 22

Event: Sleep Wake Failure

Steps: 1

Hardware model: MacBookPro11,4

Active cpus: 8

[ extra blank lines are removed ]

================================================================

Code: 0x31000000

System Profile:

AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x152), Broadcom BCM43xx 1.0 (7.21.95.175.1a6)

Bluetooth: Version 4.4.6f1 17910, 3 services, 18 devices, 1 incoming serial ports

Thunderbolt Bus: MacBook Pro, Apple Inc., 27.1

Memory Module: BANK 0/DIMM0, 8 GB, DDR3, 1600 MHz, 0x80AD, 0x484D54343147533642465238412D50422020

Memory Module: BANK 1/DIMM0, 8 GB, DDR3, 1600 MHz, 0x80AD, 0x484D54343147533642465238412D50422020

USB Device: USB 3.0 Bus

USB Device: USB Flash Drive

USB Device: Apple Internal Keyboard / Trackpad

USB Device: Bluetooth USB Host Controller

USB Device: Hub

USB Device: SCR33xx v2.0 USB SC Reader

USB Device: Trackball

USB Device: Microsoft Natural Keyboard Pro

Serial ATA Device: APPLE SSD SM0256G, 251 GB

Model: MacBookPro11,4, BootROM MBP114.0172.B16, 4 processors, Intel Core i7, 2.2 GHz, 16 GB, SMC 2.29f24

Network Service: Wi-Fi, AirPort, en0

Graphics: Intel Iris Pro, Intel Iris Pro, Built-In

I have reviewed the System Logs and found that Excessive Wakeups is a recurring theme. I had found some middle of the night things like Chrome update, a couple time. But, am ruling them out as not appearing consistently.

Oct 4 01:33:54 61 kernel[0]: PM response took 2245 ms (813, prl_disp_service)

Oct 4 01:34:54 61 kernel[0]: process SystemUIServer[424] caught causing excessive wakeups. Observed wakeups rate (per sec): 433; Maximum permitted wakeups rate (per sec): 150; Observation period: 300 seconds; Task lifetime number of wakeups: 66901

Oct 4 01:34:54 61 com.apple.xpc.launchd[1] (com.apple.ReportCrash[47317]): Endpoint has been activated through legacy launch(3) APIs. Please switch to XPC or bootstrap_check_in(): com.apple.ReportCrash

Oct 4 01:34:54 61 ReportCrash[47317]: Invoking spindump for pid=424 wakeups_rate=433 duration=104 because of excessive wakeups

Oct 4 01:34:54 61 kernel[0]: process Spotlight[462] caught causing excessive wakeups. Observed wakeups rate (per sec): 214; Maximum permitted wakeups rate (per sec): 150; Observation period: 300 seconds; Task lifetime number of wakeups: 56730

Oct 4 01:34:54 61 ReportCrash[47317]: Invoking spindump for pid=462 wakeups_rate=214 duration=211 because of excessive wakeups

Oct 4 01:34:57 61 kernel[0]: process com.apple.Ambien[297] caught causing excessive wakeups. Observed wakeups rate (per sec): 265; Maximum permitted wakeups rate (per sec): 150; Observation period: 300 seconds; Task lifetime number of wakeups: 47844

Oct 4 01:34:57 61 com.apple.xpc.launchd[1] (com.apple.ReportCrash.Root[47318]): Endpoint has been activated through legacy launch(3) APIs. Please switch to XPC or bootstrap_check_in(): com.apple.ReportCrash.DirectoryService

Oct 4 01:34:57 61 ReportCrash[47318]: Invoking spindump for pid=297 wakeups_rate=265 duration=170 because of excessive wakeups

Oct 4 01:38:43 61 UserEventAgent[373]: event was XPC_ERROR_CONNECTION_INVALID

Oct 4 01:38:54 --- last message repeated 1 time ---

Oct 4 01:38:54 61 kernel[0]: Restarting to collect Sleep wake debug logs

Oct 4 08:41:02 localhost bootlog[0]: BOOT_TIME 1507120862 0

The above is an example of three processes that are causing the excessive wakeups. There are many other process doing the same.

The snippet also shows the machine Restarting to collect Sleep wake debug logs. And, the next thing is my boot of the machine. This is where the machine goes Zombie. I am convinced that the logs are never collected.

Where are the "Sleep wake debug logs" ?

The only other 'logs' I have found are the Diagnostic Message that are routinely sent to Apple (I do allow this.)

10/4/17 1:33:29.399 AM powerd[55]:

com.apple.message.domain: com.apple.sleepwake.type

com.apple.message.signature: Normal Sleep

com.apple.message.signature2: Maintenance Sleep

com.apple.message.signature3: Maintenance

com.apple.message.signature4: Maintenance

com.apple.message.result: pass

com.apple.message.summarize: YES

SenderMachUUID:

10/4/17 8:41:05.449 AM powerd[55]:

com.apple.message.domain: com.apple.sleepwake.failure

com.apple.message.signature3: Sleep

com.apple.message.signature: Darkwake Entry Failure

com.apple.message.value: 125

com.apple.message.summarize: NO

SenderMachUUID:

10/4/17 8:41:05.449 AM powerd[55]:

com.apple.message.domain: com.apple.sleep.failure

com.apple.message.signature: Darkwake Entry Failure

com.apple.message.summarize: YES

SenderMachUUID:

10/4/17 8:41:05.449 AM powerd[55]:

com.apple.message.domain: com.apple.sleepwake.type

com.apple.message.signature: Unknown

com.apple.message.signature3: Unknown

com.apple.message.signature4: Unknown

com.apple.message.result: fail

com.apple.message.summarize: YES

SenderMachUUID:

Things I have done

• Reset the SMC (twice)
• Reset the VNRAM (once
• Many reboots

Any other suggestions?

Thanks,

Richard

timestamp":"2017-03-22 02:32:10.66 -0400","bug_type":"142","os_version":"iPhone OS 10.2.1 (14D27)","incident_id":"0BFB5382-E1C6-48D4-A4D5-CE14FE4A60B1"}

Date/Time: 2017-03-22 02:27:22 -0400

OS Version: iPhone OS 10.2.1 (Build 14D27)

Architecture: arm64

Report Version: 19

Command: amy

Path: /var/containers/Bundle/Application/A1224398-960F-440D-9829-0BDE10667449/amy.app /amy

Version: 3165 (3165)

Parent: launchd [1]

PID: 1415

Event: wakeups

Wakeups: 45001 wakeups over the last 288 seconds (156 wakeups per second average), exceeding limit of 150 wakeups per second over 300 seconds

Duration: 287.81s

Steps: 126

Hardware model: iPhone8,1

Active cpus: 2

Powerstats for: amy [1415]

UUID: 5E052756-E8AA-3251-9A30-7CB8C61B9EFF

Start time: 2017-03-22 02:30:57 -0400

End time: 2017-03-22 02:32:10 -0400

Parent: launchd

Microstackshots: 126 samples (100%)

Primary state: 77 samples Frontmost App, User mode, Effective Thread QoS User Interactive, Requested Thread QoS User Interactive, Override Thread QoS Unspecified

User Activity: 0 samples Idle, 126 samples Active

Power Source: 126 samples on Battery, 0 samples on AC

79 ??? (libdyld.dylib + 17848) [0x188c795b8]

79 ??? (+ 181424) [0x1000d44b0]

79 ??? (UIKit + 480564) [0x18fcd8534]

79 ??? (UIKit + 501756) [0x18fcdd7fc]

79 ??? (GraphicsServices + 49560) [0x18b74a198]

79 ??? (CoreFoundation + 37560) [0x189c962b8]

78 ??? (CoreFoundation + 898044) [0x189d683fc]

78 ??? (CoreFoundation + 907280) [0x189d6a810]

78 ??? (libdispatch.dylib + 23912) [0x188c4ad68]

78 ??? (libcorecrypto.dylib + 405948) [0x188c461bc]

78 ??? (libcorecrypto.dylib + 406012) [0x188c461fc]

78 ??? (

My phone has been doing weird things

Those messages have nothing to do with the functioning of your Mac or iPhone. Like virtually everything in the console, they are messages for developers so that they can optimize their apps.

Start a separate post in the iPhone community with details about the problem you are having, not what you think it might be causing the problems.

This is the first thing that came up in a search for excessive wakeups.

This is certainly a bug and not something to just toss aside as something "too advanced" for us dull, silly end-users.

For a couple months, I've been having extreme issues with my 2010 Mac Pro - 12 core 3.46 ghz Xeon, 128 gb/1 tb/GTX1080. Also have two internal 4tb storage drives and an external 4 tb Time Machine volume.

I've noticed some extreme lag in the UI if I let it sit for a few minutes without usage. To the point where even switching between apps might take a full minute as the image chops across the screen. In addition, I've had several full lockups, requiring a forced restart, and many times losing anything that wasn't autosaved. Latest one caused the screen to go all black. Even the screen saver will sometimes drop to only a frame or two a second, and if I wake it up while that's happening, it will take 5-7 minutes for the system to be usable again. Several apps are having a very hard time - Twitter, VMWare, Safari and iTunes are all extremely sluggish and even crash.

I've noticed that the window server as well as the above apps all generate excessive wakeup request reports, and I've gone back and looked at the time stamps and many seem to have happened during a particular bad slowdown/crash. OS X has a hard limit of 150 wakeups per second on a thread, some threads by the above apps (and others) are exceeding 45,000 a second. Quite obvious to anyone who understands how OS X works, this is a bug and will certainly cause problems.

By the way, I'm running 10.12 at the moment, so this bug is still apparently in the system. I will try an SMC reset and see if that solves the problem. Haven't done one in over a year on this machine so I suppose it was due for one anyway.

I feel it's far more helpful to actually analyze and troubleshoot this problem than to summarily dismiss it as something that's far too complex for us to possibly understand...I've lost work due to this bug and it has severely impacted my productivity. Not acceptable for a Pro machine running an up-to-date version of OS X with no questionable third-party software and obsessive-compulsive maintenance.

DaBugler,

it would be best if you created a new post of your own, and in it, post the kernel panic log.

Excessive Wakeups are nuisance log entries for developers to help fix their software. They are not related to sleep/wake kernel panics.

I ran across your post because my Mac Pro is freezing. When I look at the logs, I too find a number of entries about excessive wakeups (RetroISA). I too hope someone can provide more information because, unlike in your situation, these entries are either causing or indicating a problem. In the meantime, I'll try uninstalling Retrospect and see if that helps.

My MacPro is freezing as well. Twice today. I see similar errors, as well as the "unable to create kext cache under" error which I think I've now solved.

If anyone gets more info on the MacPro freezing and if these wakeups have anything to do with it I'd sure like to know.

I will add to this as well, not much on the web about this error in console.

Is this for debugging purposes, or a bad app.

Type this into terminal

syslog | grep -i "Wake Reason"

you can see the reasons the mac was awaken. Could be alarms (crontab entries), could be network access, could be keyboard/mouse/trackpad stuff.

I started getting problems after upgrading to 10.9.2 on a new MBP. When I open my laptop in the morning, I find that it has rebooted overnight. A quick check of the logs reveals:

3/13/14 9:50:05.000 PM kernel[0]: process SystemUIServer[182] caught causing excessive wakeups. Observed wakeups rate (per sec): 796; Maximum permitted wakeups rate (per sec): 150; Observation period: 300 seconds; Task lifetime number of wakeups: 115950

3/13/14 9:51:20.000 PM kernel[0]: Restarting to collect Sleep wake debug logs

Anybody got any ideas?

I found this,

Reset SMC

Shut down

Safe boot

Shut down

Reset PRAM.

Set pier options to defaults.

Helped with many apps.

Let's see if they come back.

I think there is a bug in sleep mode.

Correction reset power options to defaults.

Why can't I edit my post.