Excessive Wakeups

Yep. My mid-2013 MBA is freezing up. After force-restarting the logs have the excessive wakeups message.

Did not last long,

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.

Have now v3.5.6 running for almost 24 hours. Ony a simgle spindump and no stuttering or missing frames.

Still no change with 10.9.3 - sad.

I have now 10.9.3 + EyeTV 3.6.5 (=latest!) and see a spindump about once an hour. But have been once playing recordings so must see howrecording will be.

Make a diagnostic report and send it directly to Apple, it seems to be a complex bug.

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.

I hope it gets resolved in a future update.

Apple will never resolve a problem caused by a garbage "anti-virus" program such as McAfee.

Writing an effective Apple Support Communities question

So I'm assuming by your curt reply that you'd suggest I disable McAfee?