5 Replies Latest reply: Apr 8, 2012 9:27 PM by Dimitri B
qball12 Level 1 Level 1 (0 points)

I've got a problem on an iMac 27" end of 2009. When i put it to sleep it either wakes up straight away or goes black but HDD is running. Only keyboard is plugged in via USB and Magic Mouse is on bluetooth. The only suspicious console line after waking up is :

 

05.03.2012 15:15:39,000 kernel: Sound assertion "0 == fAudioEngineArray" failed in AppleHDADriver at line 3047 goto Exit

 

I disabled all internet sharing and WOL.

 

If i disable Wi-Fi and bluetooth nothing changes.  Please help! :-\


iMac, Mac OS X (10.7.3)
  • qball12 Level 1 Level 1 (0 points)

    ... when I logout and login as guest and try to put the machine to sleep - it wakes straight up as well.

  • X423424X Level 6 Level 6 (14,215 points)

    Look at the kernel log for likes that say "Wake reason =".  You will see a code.  Go to the following to find the meaning of the codes:

     

    Determine Why Your Mac Wakes Up From Sleep

     

    That may help shed light on why you machine is waking up.

     

    If you cannot figure it out there's always utilities like PleaseSleep which try to force the system to obey the Energy Saver preferences.

     

    Also, with respect to the Energy Saver preferences, make sure you don't have wake for network access checked.

  • qball12 Level 1 Level 1 (0 points)

    Thanks for your reply, but as I stated above: Wake On Lan is OFF and there is no sign of "Wake reason" the only Error-like line is the:

     

    kernel: Sound assertion "0 == fAudioEngineArray" failed in AppleHDADriver at line 3047 goto Exit

     

    And Im not sure if I want to install 3rd party software to do the job that system tools should do. The whole thing started after the "No WIFI connection after waking up" update few days ago.


  • qball12 Level 1 Level 1 (0 points)

    Ok, I found out what the couse was - My old printer did not finish the printing process and coused my iMac to stay awake even after couple of hard resets. And the console did not informed me of this. Herby I consider this problem as Solved! :-)

  • Dimitri B Level 1 Level 1 (0 points)

    Thank you for the tip!

    I got the same problem a few days ago, called Apple Support, spend an hour on the phone deleting .plist files, got transferred to a 'seniour consultant' who got me to re-install Lion, which fixed the problem for half-a-day.

    After reading the printer story, I remembered that my 5-year old recently developed a facsination for hitting a print button whenever there is one, so I had to switch the printer off half-way through one of his 'print jobs'.

    All I had to do now is to switch the printer on and let it go through to complete the queued printing, and the problem is gone!