Display didn't wake

I got up this morning and tried to check my mail while the coffee brewed, and at a touch of the space key, everything but the display tried to wake from sleep: then the screaming fans of death hit and I had to reboot.
Any ideas? I can't find anything in the logs that would indicate a problem. It makes me consider not allowing the box to sleep, as that seems the only time I have prolems since Apple kindly replaced my tart, citrusy rev. A with a rev. B.
Thanks!

This has happened to me twice now, on my 3 week old iMac, although most times it wakes up fine. The latest time was when I had turned it on from powered off and then left it at the log in screen. It fell asleep and when I went to wake it up, it seemed like it was trying to, the fans came on like normal, but the screen stayed blank and then the fans started going full blast. I had to hold in the power button to stop it and reset it. I have a USB scanner and printer but they were both switched off / unplugged at the time.
Running the Hardware Test showed no errors, and I am unable to reproduce it. Hopefully it won't happen when I have some important work open.
Perhaps this is the same issue as Ramesh Tipirneni, "More IMac G5 sleep issues", 04:00am Jul 3, 2005 CDT
This is what I have done, and I suggest you do this too:
1. Turn it off, and then unplug it from the wall. Leave it so for a couple of minutes then plug it back in. This resets the SMU.
See http://docs.info.apple.com/article.html?artnum=301733
2. Start it up while holding down the Command, Option, P and R keys. When you hear the startup chime for the second time, the PRAM and the NVRAM will have been reset and you can let go of the keys. I didn't notice any side-effects of this.
My iMac has not crashed on sleep awaking since this, but it has not been very long.

Similar Messages

Display won't wake up

It's a brand new notebook.I've done nothing on it, other than installing Windows updates and creating recovery disks.I set the "Turn off display after" option to 1Minute.IMPORTANT: I set display brightness all the way to zero, the lowest setting possible, using either the keyboard keys, or the brightness option in Windows.Leave the notebook idle for a minute, the display sleeps like it should (the notebook is set to sleep after 30 minutes, it's only the display that sleeps, the notebook is still awake).Move the mouse, press keys on the keyboard, the screen does not come back up. The computer is still up and running-i can toggle keyboard backlight On/Off using the keys, but the display won't wake up.Press the "Brightness +" button on the keyboard, the display wakes up. This is the only way to wake it up. The other option is to press and hold the power button, force a shut down, and start the computer again.This happens ONLY when "brightess" is set to the lowest level. If brightness is set to even one level above the lowest, the issue cannot be reproduced. Moving the mouse or pressing any key on the keyboard will wake the display up in this situation.Both Intel HD graphics 5500 and GTX 850M drivers are up to date.BIOS is up to date as well.Battery/ Plugged in does not make a difference. If the display brightness is set to lowest, the screen will ALWAYS fail to wake up, irrespective of which power source is in use. What do I do? Please don't tell me it's a minor problem and I have to live with it.There are so many minor problems with this notebook, and all these are adding up to make it a total piece of cr.. My almost 5 years old probook with a second generation core i3 CPU and no discrete GPU, is better than this brand new 5th generation core i7+GeForce GTX notebook. I'm beginning to regret this purchase. I should have gotten another probook. Thought the Envy offers a better "bang for the buck", and now i think this was a huge mistake. Anyway, any idea how i can get this fixed? Looks like a driver problem right? Or is this a hardware problem? Can someone with an Envy notebook try this out and tell me if the issue can be reproduced on their rig? It can't be reproduced on my Probook.Thanks.

Thanks for your reply Avenger Well, I called up HP tech support.The lady took remote control of my notebook and tried numerous things in the registry (regedit).But the issue could not be solved. She then arranged for an on-site support engineer to visit my house.The Engineer showed up right on the next day, and tried the following:- Updated ALL drivers, even the ones which were already up to date!Checked with my desktop monitor, the issue cannot be reproduced on the external monitor- the external monitor will wake up on moving the mouse, but the notebook monitor stayed dim (no backlight).Opened the laptop, took out the display cable, cleaned it with some solution he had, put everything back together- issue not resolved, external monitor wakes up but notebook monitor stayes dimmed. This is not the only problem I was having with the notebook, the other problems are:Battery would stop charging when the notebook is switched OFF, and the charger is turned ON and OFF a couple of times.The battery lock doesn't "click" in place, it slides automatically to the "unlock" position, it's loose.There's a dead pixel on the display. He offered me two choices: 1> Replace motherboard (to solve battery not charging issue), replace chassis (to solve the battery lock issue), and replace display panel (to solve the dim display + dead pixel issue). =======OR======= 2> Return the whole notebook back to HP, and get a new notebook (same model) in exchange. I picked option 2. We shared a cup of coffee, and the tech left (he was very nice and friendly). The next day, I got an email from HP, with a PDF attachment, asking me to take my laptop, along with a hard copy of the email, and payment invoice, to the HP store. HP store took my computer back, but they didn't have a replacement ready, they asked me to come after 7 days to pick up a new notebook (same model). I really loved my Envy. It's a very nice looking laptop. Hope the replacement I get won't have these weird issues. I'll update the thread when I get the replacement. Thanks for your help

Thunderbolt Display Didn't Show Anything!

I recently got Boxee. I connected to Thunderbolt Display 2nd port, but it's not working! I connected like this:
Mac Mini (2011) --> Thunderbolt Display built-in port
Boxee --> (HDMI to mini DisplayPort cable) --> Thunderbolt Display 2nd port
The Thunderblt Display didn't display anything from Boxee! Am I doing right? Do I need any other intermediate devices to ge this config work?
Any help would be greatly appreciated.

The Thunderbolt display will only work with Macs that have a
Thunderbolt port. They are not compatible with any Mini Display Port
source.

My display will not wake when I remote in

I have an imac early 2009. I have recently updated various software from Apple. I have the engery prefrence at : 1hour Computer sleep and 15 mins Display sleep. I use Gotomypc to login to my home computer. Prior to the new updates i did not have an issue with with the computer not waking from sleep. But since the updates my display will not wake? They hardrive wake but the screen just does not. I do have a screen saver, however, this was not an issue prior to the new updates. Any help would greatly appreciated.
Thank you in advance,

After a lot of research it seems to be an issue with the last update. It appears to be an issue with several application and the developers are aware of the issue. Unfortunately the only fix to the issue currently is to keep your monitor on. I have adjusted my screen to only be on at various time to prevent burn out. I hope this helps.

IMac display won't wake up

I recently replaced the HD on my iMac Graphite 600mhz G3 and all was well until the other day it wouldn't wake up from sleep ... the light on the on/off button was not pulsing so the HD wasn't asleep. Now the display will not wake up whenever it goes to sleep and I have to restart with the power button every time. Also when I plug my iPod in it crashes from time to time and I get the message to 'restart by pressing on/off switch for 5 seconds' message. Is there a firmware update I need? I zeroed the new drive from the Panther install disc. Or is it something else. Please help!

If your Mac happily goes to sleep but won't wake up--Hold down the power switch to force-reboot your machine and get it running again.
Don't worry-your Mac isn't narcoleptic. Its Open Firmware system or NVRAM (nonvolatile RAM) is likely corrupt, and your Mac can't remember how to wake up.
Restart your Mac and immediately hold down the Command-Option-O-F key combo until you see a somewhat intimidating command-line display that ends with the Open Fimware prompt. Type the following lines:
reset-nvram
press Return on keyboard
set-defaults
press Return
reset-all
press Return
Your Mac will reboot. Once it's running, put it back to sleep to test. If the problem recurs your Energy Saver preferences may be the culprit. Delete the com.apple.PowerManagement.plist file (go to Finder/Hard drive/Library/Preferences/SystemConfiguration)--don't worry, your Mac will regenerate a new one--and then restart to see if that rights the wrong.
Still did'nt work? Might be time to call AppleCare or see an Apple Genius or a technician.
Cheers!
DALE

Qosmio X500-014 PQX33C-01400N display does not wake on reboot

Recently my Qosmio X500-014 PQX33C-01400N display does not wake on reboot. I can see the the HDD status light working but I don't see the BIOS boot process or the Windows login. It's just blank. I know it boots Windows as I hear the chime and the webcam lights up waiting for face recognition.
I can reboot and plug in an external display and see the whole boot process and it works, but when I log in, Windows does not detect the laptop display.
For the laptop display to work. I reboot and wait until I see the webcam lightup which I assume means Windows is already in login prompt. I close the built in LCD display down and wait for the laptop to go to sleep mode. Once in sleep mode, I prop up the screen and it awakes like normal. I now don't shut down my laptop because of this. I just close down the screen and put it on sleep so I can easily get to it by simply waking it up.
Is this a hardware problem? BIOS problem? display adapter problem? I've never seen this problem in any forum.
Any advice would help. Thanks!

As that's a Canadian model, you'll want to check their support site.
I'm not a tech support agent, but I doubt it's a driver issue because it's manifesting pre-Windows. Try checking for any relevant BIOS settings.
- Peter

My Thunderbolt Display will not wake up from sleep!

I have a 13" MacBook Pro on 10.8.4 Mountain Lion. When I hit the space bar to wake up my laptop, the Thunderboly Display stays black! Unplugging the display cable and plugging it back in solves the issue, but then it consolidates my open windows! REALLY ANNOYING!
There's also been 2 or 3 times when that didn't work and I had to shut the computer down and disconnect the power from the ThunderBolt display... Any cure for this nonsence?

I only had that problem once - and unplugging the Display from power and lugging it back in solved the problem for good.
Sine that's not working for you, you may be having a problem with the TB cable itself. If I were you, I would take the computer and Display to your local Apple Store/AASP and have them diagnose the problem. Again, I suspect that it's the TB cable, but I could be wrong...
Clinton

Display won't wake

I have a 13" Macbook pro. I am using a large WORD template to write a large document. Lately if I leave the computer on overnite, I can't get the display to wake up. I believe the computer is on because the white light is lit up. Is this something I can fix or do I need a genius? I just now changed the energy settings to never shut the computer off. If this does not work I will do the same for the display.

There have been a number of issues reported that have to do with usb devices. I have a usb card that sometimes will do the same thing, I never let my computer sleep because of it. If I log out and then put my G5 to sleep it'll wake up everytime. You might try disconnecting the printer and trying it that way for awhile even though that might be a pain for you. You might also try to create a new user and see if the problem persists, could be your user prefs are corrupt. Another thought while you're at it...reset your nvram.
Apple came out with a firmware update but it was for single processor models. I searched and didn't find any updates for your 1.8. There are however several threads about it, if you search "dual 1.8 wake from sleep" you'll find a buch of posts.

T440s display won't wake up from password-protected sleep mode

The display on my new T440s stays off and cannot be recovered, when it is in password-protected sleep mode (or when it has gone to sleep from password-protected screen saver mode). The only way to recover is to press the power button to shut down completely, and reboot the computer.
When I remove the password protection from sleep mode, the display turns on and off as expected during sleep/wake cycles.
Have any of you experienced this? Is there a fix? I do want to use password protection in sleep mode for security.
Thanks.

I posted this yesterday on another Mac site and thought I'd post it here, too, since my experience is similar to rmckillen's, and BobThe Developer has an explanation for it (thanks!). I've had my 15" MacBook Pro for almost 3 months, and it's been working fine until now. Tonight after it went to sleep while open, I tried to wake it up and the screen stayed dark, though you could faintly see what was on it. When I tried pressing the power button, I could see through the darkness that I was getting the usual message asking if I wanted to shut down. I waited for the approximately 2 minutes for that to happen, and then the machine appeared to shut down for a few seconds--only then the dark screen with faintly visible image of what was really there appeared again. I tried closing the machine and opening it again, but that didn't help, nor did clicking the mouse. The only thing that worked was forcing a quit by pressing command-control-power all at once. The machine shut down, and then when I turned it on again, everything was back to normal. My question now is, should I bring my machine in to Apple about this--will it be something they can fix, or is it just a problem I'll have to live with (or will the next operating system address it?)? Thanks...

Cinema Display won't wake from sleep

After reading lots in the forums I've concluded lots of people have the same problem that we are mistakenly thinking is specific to a particular monitor or Mac or behaviour.
Problem: Display suddenly does not wake from sleep - incidentally after an OS update and Cuda update.
Hypothesis: This definitely seems like a software problem as I've solved it in so many new ways. (Some people are replacing hardware!) Once fixed, the problem recurs the next time the display goes to sleep. However solutions rarely work a second time.
Solutions:
1. Zapping PRAM fixes it.
2. Deleting all displays preferences fixes it.
3. Safe boot and clear caches may have fixed it.
4. Pulling the Mini DisplayPort cable and blowing on it has fixed it. (I thought it was dusty since it worked. It may have just been pulling the cable.)
5. Deleting a power management preference in System/Library/SystemConfiguration/ fixed it.
6. Moving the power plug from one slot on a power bar to another fixed it. (***!?!)
7. Creating a new user account fixed it.
8. Now I'm stuck.
Please can help me think of a new way to fix it? If I can get it going again, I will simply keep the computer and 2nd display awake forever.

I have a new fix!
8. Launch Magic Bullet Looks app and fiddle with the display settings!!! Woohoo! I got it back again.
As long as the display never goes to sleep and is never unplugged (tried that) I can keep using the monitor. Sadly this means never lettting the new iMac sleep.

Display no longer wakes from sleep after latest updates

G4 Quicksilver 933, nVidia Ti, 1.5GB, 20in Cinema Display
I applied the latest updates that were pushed out recently (10.5.2 and the "Leopard Graphics Update") and now my Apple display will not properly come up when I wake the box from suspend.
That is, it starts and runs fine, but if it goes into sleep, upon waking it will (sometimes) flash the contents of the desktop, and then go black. The litte green light is on. Happens from a logged in session, or from the main login screen.
I have to hit the reset or power button (or login via SSH and issue a shutdown) to get it to work again.
I only have a single monitor.
I tried:
o Powering the monitor off and on, both from the switch and by pulling the power cable
o Pulling the DVI cable and reinserting it
o Resetting NVRAM
o Re-applying both the 10.5.2 combo installer and the Leopard Graphics Update 1.0 in order
o Waving a magic wand... I mean, fixing permissions
o Changing the display resolution a few times
o Running fsck a few times (only because all these unclean shutdowns are making me nervous)
o Hitting the "Detect Displays" button in the Displays Prefs panel...
Aha! Hitting that button causes the display to flash and then go dark. I have to power cycle the unit to get the monitor to come up again.
I do have the special build option of the faster video adapter which was available all those years ago. It's quaint now, sure, but it was a fast card back then.
I'm stumped. It's surprising how something like this can turn a perfectly reasonable desktop into a boat anchor.
Message was edited by: John Verne

mjelacic wrote:
This Discussion is marked as Answered, but with my apologies to the other respondents, it is NOT. There is a problem. The software/hardware do NOT work as they are supposed to. Apple needs to address this problem immediately. Mac Book Pro will not wake from sleep when connected to a Cinema Display 23". The problem lies in the most recent operating system updates. Before the update the products worked as advertised, since then they do not. Period.
With all due respect, I am the one who posted this, and I marked it "answered." Yes, there very well may be a problem with the Leopard Graphics Update 1.0 (what a mouthful! I dub it "LGU v1.0" from this point on.), but this is so far only a hypothesis.
I found an immediate workaround which suits my purpose. If this does not suit the purposes of completely foreign (to this discussion) symptoms related to Intel-based Apple laptops and external displays, then so be it. I recommend splitting off your own symptoms to a new thread.
Certainly, my reading of the symptoms described after I posted mine mostly do not sound like what I ran into at all. For example, I never once said that my computer had problems waking from sleep. I said the /display/ had problems waking/starting up after sleep, and this is probably related to the "detect displays" mechanism that the OS uses to find attached displays when it comes out of suspend. Even if this is my misunderstanding it does not matter, since this is how it comes across to a reader. This may indicate that someone may want to clearly and carefully describe /exactly/ what they are seeing, and the steps they took in order to come to any conclusions they might have.
This will help Apple, and it will certainly help others that search these threads with their own similar but different issues they need solved.
If there is a common reproducible issue related to displays and the most recent update(s), then Apple already knows about it, or soon will. As far as my immediate needs are concerned, this is answered.

Macbook pro retina display won't wake on windows 8.1

Hi,
I have installed windows 8.1 on my new Macbook Pro with retina with using bootcamp no problem there only issue is after my laptop goes to sleep it won’t wake up. It seems that the issue is with the display driver or something related to it because even when only display is off I have the same problem.

I am aware there are symbols. My technical issue is the MagSafe2 adapter. What people typically do is connect their laptops to the wall when they're battery dies off. No biggie. I can attach it to the outlet. Well, when I connect the adapter to the outlet, nothing happens. Nothing happens at home, at Starbucks, at McDonalds, at other people's home.
When I brought this up with technical support in August when I bought it, technical support person said I might have issues with my electrical wiring at home. I've never had issues with electrical wiring at home because my other Apple products work fine when connected to the outlet. My July 2011 MacBook Pro charged without a hitch.
And I was able to charge my Retina MBP only at night or very early in the morning.
But this weekend, I couldn't charge it at all. I'm starting to think it might be the MagSafe2 adapter problem.
I feel rather ridiculous buying the highest-end of the 15 inch Retina MBP. It cost me over $3000. Right now I'm working with my 5 year old Hewlett Packard laptop. At least my HP works, which can't be said about this top-of-the line Apple product.
Probably explains why Apple stocks are falling. At $3000 I shouldn't be having these type of problems.
Sheeeesh!!!

External Display doesn't wake from display sleep

My display is set to sleep after an idle period (computer itself set to not sleep), when I return to the computer and wake the displays the external display most of the time does not "wake" or come back with picture. I need to disconnect the adapter and plug it in again.
Anyone else experiencing this?

Guys, please read THIS thread:
http://discussions.apple.com/thread.jspa?threadID=1760586&tstart=0
EVERYONE is experiencing this bug if you're using your new MacBook Pro with an external display. In the thread above, I detail how to fix it without having to unplug the DisplayPort adapter.
The symptoms you're experiencing are:
1.) Bizarre interference all over the external display when either a) waking your notebook from sleep, or b) turning screen on if the screen is set to turn off after x minutes.
2.) External display not actually turning on at all after either a) waking your notebook from sleep, or b) turning screen on if the screen is set to turn off after x minutes.
The fix is listed in the above thread. It's only a temporary workaround, and Apple REALLY needs to address this issue ASAP.

Macbook Pro Thunderbolt and HDMI displays switch on wake up

Hi there,
Currently using a late 2013 15" Macbook Pro., latest version of Mavericks. I have one display hooked up through Thunderbolt->DVI, with a second set up through HDMI->DVI.
There seems to be an issue where on waking the monitors up from sleep mode (about 10 minutes inactivity time) the displays will turn on, immediately go black (inlcuding the Macbook Pro screen), and then switch such that all windows on one are now on the other.
I can't really repliate this, as it seems to just happen randomly. All I can say in my detective work, is that the HDMI->DVI hooked-up monitor tends to take a little more time to turn on after sleep, whereas the Thunderbolt->DVI monitor comes up immediately.
Any help would be greatly appreciated.
Thanks.

I've noticed that the HDMI connection seems to lag the Thunderbolt on wake as well. I haven't had the switching issue, though. I use my Thunderbolt display as the primary (menu bar in the preferences) - maybe try doing that if you're using your HDMI out as the primary.
You can always try resetting the SMC and PRAM as well.

What is "Wake Reason: UHC2"? My Mac Pro woke up this morning at 6:08a. I'd rather it didn't wake up on its own. Thanks.

I have an April 2009 Mac Pro 2 x 2.26 Quad Core Xeon with 28GB of 1066 MHz DDR3 and a 240GB SSD, running OS X 10.9.4. None of the boxes are checked in my Energy Settings (Wake from LAN is not checked), and wake for Bluetooth is not checked.
Thanks.
Steven
Here's what's in the console
8/12/14 1:33:59.000 AM kernel[0]: 0x1face001, 0x00000000 Intel82574L::setLinkStatus - not active
8/12/14 1:34:00.000 AM kernel[0]: Wake reason: UHC1
8/12/14 6:08:16.000 AM kernel[0]: RTC: PowerByCalendarDate setting ignored
8/12/14 6:08:16.000 AM kernel[0]: Previous Sleep Cause: 5
8/12/14 6:08:16.000 AM kernel[0]: 0x1face000, 0x00000000 Intel82574L::setLinkStatus - not active
8/12/14 6:08:16.000 AM kernel[0]: 0x1face001, 0x00000000 Intel82574L::setLinkStatus - not active
8/12/14 6:08:16.000 AM kernel[0]: The USB device Smart-UPS 1500 FW:COM 02.1 / UPS.05.D (Port 1 of Hub at 0x1d000000) may have caused a wake by issuing a remote wakeup (2)
8/12/14 6:08:16.000 AM kernel[0]: 0x1face000, 0x00000000 Intel82574L::setLinkStatus - not active
8/12/14 6:08:16.000 AM kernel[0]: 0x1face001, 0x00000000 Intel82574L::setLinkStatus - not active
8/12/14 6:08:16.448 AM configd[18]: network changed: v4(en0-:10.0.1.2) DNS- Proxy- SMB-
8/12/14 6:08:16.601 AM netbiosd[117]: network_reachability_changed : network is not reachable, netbiosd is shutting down
8/12/14 6:08:19.000 AM kernel[0]: Ethernet [Intel82574L]: Link up on en0, 1-Gigabit, Full-duplex, Symmetric flow-control, Debug [796d,af08,0de1,0200,cde1,3800]
8/12/14 6:08:19.000 AM kernel[0]: 0x1face000, 0x0000000b Intel82574L::setLinkStatus - active
8/12/14 6:08:19.449 AM configd[18]: network changed: v4(en0+:10.0.1.2) DNS+ Proxy+ SMB+
8/12/14 6:08:19.845 AM apsd[360]: Unrecognized leaf certificate
8/12/14 6:08:25.000 AM kernel[0]: 0x1face001, 0x00000000 Intel82574L::timeoutOccurred - no link - reset the chipset once
8/12/14 6:08:25.000 AM kernel[0]: 0x1face001, 0x00000000 Intel82574L::setLinkStatus - not active
8/12/14 6:08:25.000 AM kernel[0]: 0x1face001, 0x00000000 Intel82574L::setLinkStatus - not active
8/12/14 6:08:26.000 AM kernel[0]: 0x1face001, 0x00000000 Intel82574L::setLinkStatus - not active
8/12/14 6:08:26.665 AM osascript[25618]: Initializer-based scripting additions are no longer supported. "/Library/ScriptingAdditions/LCC Scroll Enhancer Loader.osax" not loaded.
8/12/14 6:08:29.877 AM gkbisd[218]: Unable to collect cdhash for /Library/Application Support/Adobe/OOBE/PDApp/UWA/AAM Updates Notifier.app (error code 100024)
8/12/14 6:08:29.954 AM com.apple.launchd.peruser.501[250]: (com.realvnc.vncserver_service_agent.282160[25624]) assertion failed: 13E28: launchd + 43184 [364E35A7-9FA7-3950-8494-40B49A2E7250]: 0xffffffffffffffff
8/12/14 6:08:30.252 AM com.apple.SecurityServer[15]: Session 100039 created
8/12/14 6:08:31.536 AM osascript[25628]: Initializer-based scripting additions are no longer supported. "/Library/ScriptingAdditions/LCC Scroll Enhancer Loader.osax" not loaded.
8/12/14 6:08:31.552 AM com.apple.launchd.peruser.501[250]: (com.shirtpocket.backupbytime[25628]) Exited with code: 1
8/12/14 6:08:32.210 AM com.apple.dock.extra[410]: <NSXPCConnection: 0x7f7f80747b20>: received an undecodable message (no exported object to receive message). Dropping message.
8/12/14 6:08:34.802 AM WindowServer[161]: disable_update_timeout: UI updates were forcibly disabled by application "Microsoft Outlook" for over 1.00 seconds. Server has re-enabled them.
8/12/14 6:08:34.856 AM WindowServer[161]: common_reenable_update: UI updates were finally reenabled by application "Microsoft Outlook" after 1.05 seconds (server forcibly re-enabled them after 1.00 seconds)
8/12/14 6:08:40.003 AM AirPlayUIAgent[4555]: 2014-08-12 06:08:40.002986 AM [AirPlayUIAgent] Changed PIN pairing: no
8/12/14 6:08:40.027 AM AirPlayUIAgent[4555]: 2014-08-12 06:08:40.026624 AM [AirPlayUIAgent] Changed PIN pairing: no
8/12/14 6:08:44.574 AM mds[118]: (Warning) QueryTask: Haven't sent anything for 60 seconds; try despite not having received RTS notification.
8/12/14 6:08:44.604 AM mds[118]: (Warning) QueryTask: Haven't sent anything for 60 seconds; try despite not having received RTS notification.
8/12/14 6:08:45.176 AM fseventsd[76]: read_disk_log: problems with history file: /Volumes/Main/.fseventsd/000000000ff8e61a (fd -1, errno 5 ; is_reg 0; uid 0/0 gid 0/0)
8/12/14 6:09:09.451 AM WindowServer[161]: _CGXHWCaptureWindowList: No capable active display found.
8/12/14 6:09:17.000 AM kernel[0]: 0x1face000, 0x00000000 Intel82574L::setLinkStatus - not active
8/12/14 6:09:17.000 AM kernel[0]: 0x1face001, 0x00000000 Intel82574L::setLinkStatus - not active
8/12/14 6:09:17.000 AM kernel[0]: Wake reason: UHC2
8/12/14 7:14:33.000 AM kernel[0]: RTC: PowerByCalendarDate setting ignored
8/12/14 7:14:33.000 AM kernel[0]: Previous Sleep Cause: 5

The USB device Smart-UPS 1500 FW:COM 02.1 / UPS.05.D (Port 1 of Hub at 0x1d000000) may have caused a wake by issuing a remote wakeup

Display didn't wake

Similar Messages

Maybe you are looking for