iMac won't wake up from sleep using keyboard or mouse

Thanks for the reply iDrifter, I have made those adjustments and will see how it goes, I almost always do a forced sleep so I don't know if this will have an effect but I'll try anything at this point.

I just bought a new i3 before new year and have encountered the same problem twice so far. I force sleep and then the next day it won't wake up and requires holding the power for 10 secs and then restarting. I have looked at the logs. They seem to indicate that it went to sleep OK but then the logs also show that upon restarting the next day an "imporper" shut down has been detected and also a "Sleep: Drivers Failure - AC - EHC2".

Jan 25 22:15:06 XXs-iMac loginwindow[38]: loginwindow SleepWakeCallback WILL sleep
Jan 25 22:15:06 XXs-iMac kernel[0]: AFPSleepWakeHandler: going to sleep
Jan 26 20:00:34 localhost com.apple.launchd[1]: * launchd[1] has started up. *
Jan 26 20:00:38 localhost DirectoryService[11]: Improper shutdown detected
Jan 26 20:00:40 localhost blued[17]: Apple Bluetooth daemon started
Jan 26 20:00:49 localhost mDNSResponder[18]: mDNSResponder mDNSResponder-258.14 (Nov 18 2010 14:18:32) starting
Jan 26 20:00:50 localhost configd[15]: Sleep: Drivers Failure - AC - EHC2

Can anyone help me root out the sleep drivers failure?

Thanks in advance

do you have bluetooth keyboard and/or mouse? Did you check the issue of blue tooth disconnecting and the keyboard or mouse simply not communicating to the system upon waking up after sleep? That was my problem (apparently one of the only ones with this problem) that has fixed itself...Its been fine for the past month or so..no problems.... Just want to make sure you haven't missed this....

Still no fix, I am more than disappointed in this product and would be hard pressed to purchase another apple computer in the future, this problem is pervasive and apple continues to ignores it. Does anyone from apple actually read anything posted here?

I'd posted earlier about my case: 27" i7 late-2010 iMac that would sleep normally when booted from an external drive, but would fail to wake if it went to idle sleep when booted from the OWC SSD inside. It appears that the problem was indeed with the firmware from SandForce inside the drive. Using PleaseSleep to trap the idle timeout and force the sleep has made the machine completely stable for several weeks now. Perhaps this will help someone.

Best,
David

I suspect there are a series of issues that result in this problem. From my research on the web, this forum and my own experiences it appears likely that Bluetooth is responsible for a lot of this behavior.

Another symptom of this is trying to issue keyboard commands to OSX during boot-up (e.g. holding <option> to access the boot menu). The keyboard is unresponsive unless I repeatably bang on the key during boot (holding down doesn't work). Very occasionally the Bluetooth mouse looses connection for a fraction of a second.

Reseting PRAM and SMC are only short term solutions. In my opinion there is an issue with bluetooth hardware in these macs.

Hello Warrior102
This morning I had to reboot my iMac to get it out of sleep mode, very disheartening. However the frequency is not as much as yours by the looks of it. Arick77 and a few others are pointing to a Bluetooth problem and since I have both a bluetooth keyboard and mouse, they might be on to something. Don’t get discouraged, despite this foible, the iMac is still a fine computing machine.

I have a Bluetooth mouse & keyboard, with them set to wake up from sleep... but they are both showing as being connected and connect fine after reboot. That said I have had problem's with the mouse whilst the computer is in use. A couple of times the mouse has simply stopped working and will not connect [tried turning off and on again with no joy]. Somehow managed to navigate to Bluetooth settings via keyboard and was surprised to see that it stated the mouse was connected! Only fix was a reboot. Have now had to dig out my old usb mouse as a backup.

Also.. i can see in the logs that after a crash error reports are sent to Apple but I can't see what these reports contain. I have switched from Windows because I was fed up with the system instability... but at least with every crash it was clear a report had been sent to Microsoft and you often got a pop-up message stating a possible cause. Is there a way of generating a similar response from Apple? With the iMac when you turn on after this type of event it is as if nothing had ever happened.

I have also been wondering if the problem is related to the forced sleep... so am now just walking away from the pc and letting it going into sleep on its own... will see if the issue reappears...

Hi arirck77,

Sorry for your bad experiences lately. I have to say, that we have 5 computers in my family - all Mac's for the time - and I'm the only one who has had the not waking up issue, and actually I'm the only one here (out of five) who had any issues for the last couple of years here! That's not so bad I think.

As for the reporting, I do not know of any way of knowing what is sent from the computer to Apple, but some applications does indeed show it before they mail it. There is no feedback from Apple if they have received it or not, but could be a nice feature for them to consider.

As for these user forums, as for all those I know and have used in the past for large companies, we are completely on our own. The best you can do, is to call apple and/or establish a repair with them if you have an Apple Care agreement: https://selfsolve.apple.com/agreementWarrantyDynamic.do

Also remember to report this issue on their feedback pages. This is very important, as they might not read all what they receive on different issues, but I guess that they can count.

http://www.apple.com/feedback/

As many has reported in this tread, there seem to be issues related to different things or layers here: Some can't wake the computer at all, others gets the fireball and the computer gets stuck in a login loop.

As you also has issues with the mouse when working, it might be a good idea to change these external devices, and see if that changes anything. Can you do that?

Message was edited by: John Christiansen

Hi,

It seems that ECH is related to USB and other devices as indicated below.
I expect that you have tried to disconnect all peripheral devices unplugging cables and other things? Also trying another mouse and keyboard?

But: Since you have a brand new computer, I would suggest that you call Apple asap, and let them help you out, maybe going through some tests - as some have actually reported that failure in some part of the hardware (logic board/graphics card and even HD's has been reported) might in some instances explain your problems.
Good luck.

http://osxdaily.com/2010/07/17/why-mac-wakes-from-sleep/
OHC: stands for Open Host Controller, is usually USB or Firewire. If you see OHC1 or OHC2 it is almost certainly an external USB keyboard or mouse that has woken up the machine.
EHC: standing for Enhanced Host Controller, is another USB interface, but can also be wireless devices and bluetooth since they are also on the USB bus of a Mac.
USB: a USB device woke the machine up
LID0: this is literally the lid of your MacBook or MacBook Pro, when you open the lid the machine wakes up from sleep.
PWRB: PWRB stands for Power Button, which is the physical power button on your Mac
RTC: Real Time Clock Alarm, is generally from wake-on-demand services like when you schedule sleep and wake on a Mac via the Energy Saver control panel. It can also be from launchd setting, user applications, backups, and other scheduled events.

Message was edited by: John Christiansen

Hi John

Thanks for your replies, it is helpful to know that the driver failure is almost certainly bluetooth related. The only bluetooth peripherals I have connected are the keyboard and mouse. I have no other peripherals with either a wireless or usb connection to the mac. My back-up drive (WD myBook World) is connected into my router so all Time Machine backups are from iMac -> Router -> WD myBook World.

Given the size of the mac (27") and distance to the nearest Apple store I really want to avoid taking this in if I can help it. It really seems like a software issue that could be fixed via a patch. Unfortunately in the UK the Apple help line unhelpfully operates during the hours I am at work only! It is a shame there is no online 24hr support which a lot of vendors offer.

Don't want to muddy the waters further with other possible reasons, but I did run the Disk Repair to repair permissions as I thought this was the cause. Ran again yesterday and again there were loads of permissions it repaired. All seemed to be related to the Java library... though I don't see how this library would cause the driver problem...

iDrifter I would like to think its a blue tooth problem but I use the USB keypad keyboard thats physically connected to it and it still fails, I also tried your suggestions with the sleep settings and when that didn't work I restored defaults with the same outcome. I like the machine but its getting to be more trouble than its worth as every time I force a shutdown it tosses all my log in information and I have to answer challenge questions to log into my bank and have to log into all news and forums every time it restarts.

Hi arick77 ,

Understand your reluctance of moving it all to a repair shop, but with such a rather new piece of hardware, I do really hope that you will give Apple a call. I have myself over the years returned a couple of machines, that was replaced or repaired, and that was organized quite well, although one has to do without a computer for a week or so.

Repairing the disk permissions does no harm, and you could also try the free YASU application to clean up in other areas or get the TechTool disk that comes with an AppleCare agreement.

Some has argued here, that software errors in different parts might interfere in unpredicted ways. If you really want to repair the Mac OS as much as an normal user can do, I would suggest to insert the original system disk and run a repair and test from that.

Same problem for me, one month old iMac. I hear the machine wake up, the external drives light up etc., but the display is blank. Very poor. This machine was to replace a MacBook Pro that Apple couldn't fix either, this will be my last Mac. Nothing to do with the hardware, I've tried disconnecting everything and the problem is still there; when I go to wake the computer from the keyboard all the external drives come on but not the screen so you need to reboot the whole computer. Very disappointing.

After a month of not seeing the problem it has returned for me. Though perhaps not identical to the first time I suffered the issue here are my last observations.

- Screen would not awake from mouse click, Magic Trackpad click, or keyboard.
- Keyboard caps lock does NOT light up (engage) when pressed.
- If I switch a BT device off, when I turn it back on it fails to connect.

At this point I reach around and press the ON button briefly - Unlike the first time I witnessed this the screen came on. Thus perhaps its a different issue. the BT devices still do not interact with iMac.

- Using ssh I connect to imac from MBP.
- dtruss of blued does not seem to show anything happening.
- /var/log/system.log reports for last few hours:

Feb 1 06:03:04 iMac kernel[0]: AFPSleepWakeHandler: going to sleep
Feb 1 06:46:26 iMac configd[15]: PMConnection AirPort configd plug-in com.apple.powermanagement.applicationresponse.slowresponse 13786 ms
Feb 1 06:46:26 iMac configd[15]: PMConnection IPConfiguration com.apple.powermanagement.applicationresponse.slowresponse 13825 ms
Feb 1 05:51:25 iMac configd[15]: PMConnection mDNSResponder com.apple.powermanagement.applicationresponse.timedout 25423 ms
Feb 1 05:51:25 iMac configd[15]: PMConnection IPConfiguration com.apple.powermanagement.applicationresponse.timedout 25423 ms
Feb 1 05:51:30 iMac loginwindow[1316]: handleUnlockResult, Currenttime:2/1/2011 5:51:30.998 AM - Waketime:2/1/2011 5:50:46.000 AM = Deltatime:44.
997963965
Feb 1 05:51:36 iMac KernelEventAgent[43]: tid 00000000 received event(s) VQ_DEAD (32)
Feb 1 05:51:36 iMac KernelEventAgent[43]: tid 00000000 type 'afpfs', mounted on '/Volumes/Share', from 'afp_35BfsQ35BfsQ35BfsQ35BfsQ-2.2e000006',
dead
Feb 1 05:51:36 iMac KernelEventAgent[43]: tid 00000000 found 1 filesystem(s) with problem(s)


That is NAS that switches itself off - so no big surprise there.

Feb 1 05:51:36 iMac /System/Library/CoreServices/Finder.app/Contents/MacOS/Finder[1337]: BonjourBrowser::DNSServiceQueryRecord returned -65540
Feb 1 05:51:37: --- last message repeated 5 times ---
Feb 1 05:51:36 iMac loginwindow[1316]: AFP error -1 mapped to EIO

What's that? A quick look through logs shows that hasn't happend in last few days.
# (cat system.log; bzcat system.log.{0,1,2,3,4,5,6,7}.bz2) | grep 'AFP error'
Feb 1 05:51:36 iMac loginwindow[1316]: AFP error -1 mapped to EIO
#

Feb 1 05:51:37 iMac kernel[0]: afpfs_DoReconnect: max reconnect time reached 35 > 30 (Connecting 61) /Volumes/Share Feb 1 06:03:03 iMac loginwindow[1316]: loginwindow SleepWakeCallback WILL sleep
Feb 1 06:03:04 iMac kernel[0]: AFPSleepWakeHandler: going to sleep
Feb 1 06:46:26 iMac configd[15]: PMConnection AirPort configd plug-in com.apple.powermanagement.applicationresponse.slowresponse 13786 ms
Feb 1 06:46:26 iMac configd[15]: PMConnection IPConfiguration com.apple.powermanagement.applicationresponse.slowresponse 13825 ms
Feb 1 06:46:26 iMac configd[15]: network configuration changed.

Why does this keep changing - will take a look at new Virgin Super Hub
it seems to have a short IP lease.

Feb 1 06:46:28: --- last message repeated 1 time ---
Feb 1 06:46:28 iMac mDNSResponder[16]: RegisterInterface: Frequent transitions for interface en0 (192.168.0.4)
Feb 1 06:46:29 iMac mDNSResponder[16]: DeregisterInterface: Frequent transitions for interface en0 (192.168.0.4)
Feb 1 06:46:29 iMac configd[15]: PMConnection mDNSResponder com.apple.powermanagement.applicationresponse.slowresponse 2179 ms
Feb 1 06:46:32 iMac configd[15]: network configuration changed.
Feb 1 06:46:32 iMac configd[15]: arp clienttransmit(en0) failed, Network is down (50)
Feb 1 06:46:32 iMac configd[15]: bootp sessiontransmit: bpf_write(en0) failed: Network is down (50)Feb 1 06:46:32 iMac configd[15]: DHCP en0: INIT-REBOOT transmit failed
Feb 1 06:46:32 iMac configd[15]: DHCP en0: ARP detect ROUTER failed, arp clienttransmit(en0) failed, Network is down (50)Feb 1 07:40:29 iMac com.apple.launchd[1] (com.apple.newsyslog): Throttling respawn: Will start in 4 seconds
Feb 1 07:40:34 iMac ntpd[30]: bind() fd 25, family 30, port 123, scope 4, addr fe80::c62c:3ff:fe2e:f52e, in6 is_addrmulticast=0 flags=0x11 fails
: Can't assign requested addressFeb 1 07:40:34 iMac ntpd[30]: unable to create socket on en0 (29) for fe80::c62c:3ff:fe2e:f52e#123
Feb 1 07:40:42 iMac configd[15]: network configuration changed.
Feb 1 07:40:44 iMac ntpd[30]: time reset +1.346055 s

Wow! Is that right iMac lost over a whole second since the last network time, how often does that occur:
# grep 'time reset' system.log
Feb 1 02:14:01 iMac ntpd[30]: time reset +0.581813 s
Feb 1 03:08:08 iMac ntpd[30]: time reset +0.541685 s
Feb 1 04:02:27 iMac ntpd[30]: time reset +0.500688 s
Feb 1 04:56:36 iMac ntpd[30]: time reset +0.467584 s
Feb 1 05:51:02 iMac ntpd[30]: time reset +0.422586 s
Feb 1 07:40:44 iMac ntpd[30]: time reset +1.346055 s
Feb 1 07:49:51 iMac ntpd[30]: time reset +0.133139 s


Feb 1 07:40:44 iMac configd[15]: PMConnection IPConfiguration com.apple.powermanagement.applicationresponse.slowresponse 1642 ms
Feb 1 07:40:46 iMac configd[15]: PMConnection mDNSResponder com.apple.powermanagement.applicationresponse.slowresponse 3488 ms
Feb 1 07:40:50 iMac configd[15]: network configuration changed.
Feb 1 07:40:50 iMac configd[15]: arp clienttransmit(en0) failed, Network is down (50)
Feb 1 07:40:50 iMac configd[15]: bootp sessiontransmit: bpf_write(en0) failed: Network is down (50)
Feb 1 07:40:50 iMac configd[15]: DHCP en0: INIT-REBOOT transmit failedFeb 1 07:40:50 iMac configd[15]: DHCP en0: ARP detect ROUTER failed, arp clienttransmit(en0) failed, Network is down (50)
Feb 1 07:49:39 iMac loginwindow[1316]: loginwindow SleepWakeCallback will power on, Currenttime:2/1/2011 7:49:39.009 AM - Waketime:2/1/2011 7:49:
39.000 AM = Deltatime:0.009039104
Feb 1 07:49:39 iMac loginwindow[1316]: askForPasswordBuiltIn after makekey, Currenttime:2/1/2011 7:49:39.618 AM - Waketime:2/1/2011 7:49:39.000 A
M = Deltatime:0.618426085
Feb 1 07:49:44 iMac ntpd[30]: sendto(17.72.255.12) (fd=24): Network is unreachable
Feb 1 07:49:44 iMac ntpd[30]: bind() fd 25, family 30, port 123, scope 4, addr fe80::c62c:3ff:fe2e:f52e, in6 is_addrmulticast=0 flags=0x11 fails
: Can't assign requested address
Feb 1 07:49:44 iMac ntpd[30]: unable to create socket on en0 (32) for fe80::c62c:3ff:fe2e:f52e#123
Feb 1 07:49:51 iMac ntpd[30]: time reset +0.133139 s
Feb 1 07:49:52 iMac configd[15]: network configuration changed.
Feb 1 07:49:52 iMac configd[15]: Sleep: Success - AC - Maintenance Sleep
Feb 1 07:49:52 iMac configd[15]: Wake: Success - AC - PWRB
Feb 1 07:49:52 iMac configd[15]: Hibernate StatisticsFeb 1 07:49:52 iMac kernel[0]: AFPSleepWakeHandler: waking up
Feb 1 07:50:09 iMac loginwindow[1316]: handleUnlockResult, Currenttime:2/1/2011 7:50:09.755 AM - Waketime:2/1/2011 7:49:39.000 AM = Deltatime:30.755416095

Thas was me waking the machine, I presume from ON/OFF button?


Feb 1 07:51:14 iMac sshd[2167]: USER_PROCESS: 2169 ttys001
Feb 1 07:53:04 iMac sudo[2191]: stacey : TTY=ttys001 ; PWD=/Users/stacey ; USER=root ; COMMAND=/bin/ksh

MBP was a little slow to awake - must wake it first next time and see
if I can connect before pressing power button. I have tried that before without success!

Feb 1 07:55:06 iMac sshd[2199]: USER_PROCESS: 2201 ttys002
Feb 1 07:55:24 iMac sudo[2206]: stacey : TTY=ttys002 ; PWD=/Users/stacey ; USER=root ; COMMAND=/bin/kshFeb 1 07:55:30 iMac com.apple.launchd[1] (com.apple.blued[512]): Exited: Terminated

At this point I uttered 'dtruss -a -n blued' but only got:
PID/THRD RELATIVE ELAPSD CPU SYSCALL(args) = return
512/0xd8a: 24097 1412 32 workq_kernreturn(0x1, 0x101004B90, 0x0) = 0 0
512/0xd8a: 24117 1665 15 kevent(0x3, 0x0, 0x0) = 1 0
512/0xd776: 48 1388 11 thread_selfid(0x7FFF704C4640, 0x0, 0xFFFFFFFF) = 55158 0
512/0xd776: 103 7 3 kevent(0x3, 0x100680DB0, 0x1) = 1 0
512/0xd776: 125 1343 7 _disablethreadsignal(0x1, 0x0, 0x0) = 0 0
^C

CALL COUNT
_disablethreadsignal 1
bsdthread_terminate 1
thread_selfid 1
workq_kernreturn 2
kevent 3

As I suspect bluetooth I start a new dtruss and kill blued, and POW - keyboard works 🙂

Feb 1 07:55:30 iMac blued[2207]: Apple Bluetooth daemon started
Feb 1 07:55:30 iMac loginwindow[1316]: askForPasswordBuiltIn after makekey
Feb 1 07:55:30 iMac loginwindow[1316]: in pam smauthenticate(): Failed to determine Kerberos principal name.
Feb 1 07:55:31 iMac loginwindow[1316]: builtInAuthWindowDidResignKey
Feb 1 07:55:31 iMac loginwindow[1316]: handleUnlockResult
Feb 1 07:56:01 iMac loginwindow[1316]: no spins reported for this wake
Feb 1 07:56:01 iMac [0x0-0x142142].backupd-helper[2208]: Not starting Time Machine backup after wake - failed to resolve alias to backup volume

(Its that disk connected by USB cable - it keeps forgetting that too).

Feb 1 07:57:29 iMac fseventsd[46]: disk logger: failed to open output file /Volumes/iMac TM/.fseventsd/63657336dfdcb958 (No such file or directory). mount point /Volumes/iMac TM/.fseventsd
Feb 1 08:01:11 iMac com.apple.backupd-auto[2229]: Not starting scheduled Time Machine backup - time machine destination not resolvable.
Feb 1 08:02:36 iMac System Preferences[2236]: .scriptSuite warning for result type of command 'timedLoad' in suite 'SystemPreferences': the type NSNumber ('long') doesn't match the result Apple event code ('doub').

That's all for the messages....

What happened when launchd restarted blued.... you ask?
I have saved that to public dropbox http://dl.dropbox.com/u/8800767/blued.dtruss

I've then started a background dtruss:
# nohup dtruss -a -n blued >/var/tmp/blued&

Will look and see when next this happens.