Excessive Wakeups

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.

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

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 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 get the spin-messages on my iMac i7 with Mavericks 10.9.2 too. On a daily basis with Fusion - every day once after resuming a Win 7 virtual machine. Some times Plex "hangs" too and the Zinio reader does always. I assume this massive wakeups are a bug in 10.9.2 - hopefully it will be fixed in 10.9.3. The Mac and the described programs are working besides of these waleups absolutely fine here and I dont notice any additional stall. Only the daily accumulation of the 25 KB message on the HD is a little annyoing.

I had the same problem. I tried a much older EyeTV 3.3.3 and then I had very few (3 or 4 each day) of these spindumps caused by file:///.file/id=6571367.12367914/"... execssive wakeups ...". So I think Elgato goofed up with their updates somewhere.

I have late 2013 iMac running )SX 10.9.2 and the ancient (it's from 2010!) works fine. I sse little differences.

All I see are these 2 lines:

17-05-14 13:45:24,000 kernel[0]: process EyeTV[579] caught causing excessive wakeups. Observed wakeups rate (per sec): 1970; Maximum permitted wakeups rate (per sec): 150; Observation period: 300 seconds; Task lifetime number of wakeups: 12641595

17-05-14 13:45:27,497 spindump[1116]: Saved wakeups_resource.spin report for EyeTV version 3.6.5 (7310) (3.6.5 (7310)) to /Library/Logs/DiagnosticReports/EyeTV_2014-05-17-134527_iMac.wakeups_resource.s pin

and this report. How do I sent it whereto?

Date/Time: 2014-05-17 13:45:01 +0200

OS Version: 10.9.3 (Build 13D65)

Architecture: x86_64

Report Version: 18

Command: EyeTV

Path: /Applications/_EyeTV/EyeTV.app/Contents/MacOS/EyeTV

Version: 3.6.5 (7310) (3.6.5 (7310))

Parent: launchd [171]

PID: 579

Event: wakeups (microstackshots only)

Wakeups: 1970 wakeups per second for 23 seconds

Duration: 23.00s

Steps: 24

Hardware model: Macmini6,2

Active cpus: 8

Fan speed: 1804 rpm

Powerstats for: EyeTV [579]

Start time: 2014-05-17 13:45:02 +0200

End time: 2014-05-17 13:45:24 +0200

Parent: launchd

Microstackshots: 24 samples (100%)

Primary state: 14 samples Frontmost App, Non-Background Priority, Kernel mode

User Activity: 0 samples Idle, 24 samples Active

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

20 thread_start + 34 (libsystem_pthread.dylib) [0x9afe1cf2]

20 _pthread_start + 130 (libsystem_pthread.dylib) [0x9afdc485]

20 _pthread_body + 144 (libsystem_pthread.dylib) [0x9afdc5fb]

9 ??? (EyeTV + 1137954) [0x116d22]

..........................................

.........................................

I have now OSX 10.9.3 & EyeTV 3.6.5 (7310) running for over 2 days non-stop and all I see is a handfull (scattered in time) of spindumps. If it remains like this then for me the problem is solved.

I am having the same problem (lots of times) with my MBP 15 2,3GHz i7 with 8GB and SSD disk. It simply hang with no apparent reason.

It´s very strange and I can´t understand why! Looking for a crash repot, I found this log line

21/5/14 17:10:03,330 ReportCrash[541]: Invoking spindump for pid=401 wakeups_rate=183 duration=246 because of excessive wakeups

I couldn´t find a reason but it seems that a lot of people complain about this problem!

I have the same issue as well. I have also noticed that when I open the lid on my laptop that it takes a VERY long time respectively to connect to my preferred WiFi network - sometimes it will never connect and I have to do it manually. Also my internet connection is very slow, and possible unrelated my magic mouse connection keeps bouncing. My wife has the same Mac Air and doesn't have this issue. We both have Mac Air 1.7GHz I5's with OS X 10.9.3.

I get the following in my dmesg log history from a number of applications. Below is from the log.

process Microsoft Lync[468] caught causing excessive wakeups. Observed wakeups rate (per sec): 249; Maximum permitted wakeups rate (per sec): 150; Observation period: 300 seconds; Task lifetime number of wakeups: 3017822

process WindowServer[94] caught causing excessive wakeups. Observed wakeups rate (per sec): 191; Maximum permitted wakeups rate (per sec): 150; Observation period: 300 seconds; Task lifetime number of wakeups: 643945

process firefox[1251] caught causing excessive wakeups. Observed wakeups rate (per sec): 187; Maximum permitted wakeups rate (per sec): 150; Observation period: 300 seconds; Task lifetime number of wakeups: 159919

And lot's of these in the kernel log:

Jun 22 22:56:16 Lloyds-MacBook-Air kernel[0] <Debug>: Wake reason: RTC (Alarm)

Jun 22 23:57:00 Lloyds-MacBook-Air kernel[0] <Debug>: Wake reason: RTC (Alarm)

Jun 23 00:57:44 Lloyds-MacBook-Air kernel[0] <Debug>: Wake reason: RTC (Alarm)

Jun 23 01:58:33 Lloyds-MacBook-Air kernel[0] <Debug>: Wake reason: RTC (Alarm)

Jun 23 02:59:23 Lloyds-MacBook-Air kernel[0] <Debug>: Wake reason: RTC (Alarm)

Jun 23 04:00:07 Lloyds-MacBook-Air kernel[0] <Debug>: Wake reason: RTC (Alarm)

Jun 23 05:00:51 Lloyds-MacBook-Air kernel[0] <Debug>: Wake reason: RTC (Alarm)

Jun 23 06:01:35 Lloyds-MacBook-Air kernel[0] <Debug>: Wake reason: RTC (Alarm)

Jun 23 07:02:19 Lloyds-MacBook-Air kernel[0] <Debug>: Wake reason: RTC (Alarm)

I have a similar problem when restarting. Each time about minute in I get the spinning beach ball for about 30 to 45 seconds. Console gives me the following info closest to the time the freeze begins:

7/1/14 11:28:44.000 AM kernel[0]: process VShieldScanManag[117] caught causing excessive wakeups. Observed wakeups rate (per sec): 393; Maximum permitted wakeups rate (per sec): 150; Observation period: 300 seconds; Task lifetime number of wakeups: 45983

It's more of an annoyance than a problem, but I hope it gets resolved in a future update.