Thunderbolt on waking

Why is it that every time I close up my MacBook Pro [ spring 2011 ] the Thunderbolt won't open on next start up.  I have to take out the plug and return it.  Each time.
Also, the left side of the computer is awfully hot when the Thunderbolt is on.
Thanks,
Tzipora

Hey there Tzipora Ne'eman,
It sounds like you have a thunderbolt display that is not turning on automatically when you wake the computer and you need to reseat your connection. I would use these troubleshooting steps to help resolve the issue, from the following article:
Apple computers: Troubleshooting issues with video on internal or external displays
http://support.apple.com/kb/HT1573
If more than one video adapter is in use (or "daisy-chained"), troubleshoot by using only one adapter.
Example: A mini DisplayPort to DVI adapter connected to a DVI to HDMI adapter is an unsupported configuration because there is a series of adapters in use.
If available, try using a different display and or adapter (or use a different connector by using DVI instead of VGA, for instance).
Reset the system
You can reset the Mac's parameter RAM and SMC.
Reset the resolution
Start by resetting the Mac's parameter RAM. If the display does not come up, was previously set to an unsupported resolution, and still results in no video:
Start up in Safe Mode.
From the Apple () menu, choose System Preferences.
Choose Displays from the View menu to open the preferences pane.
Select any resolution and refresh rate that your display supports.
Restart your computer.
Thank you for using Apple Support Communities.
Take care,
Sterling

Similar Messages

  • Thunderbolt Display waking up issues

    Every time when Thunderbolt display and MacBook Pro goes to sleep, I have to manually disconnect and then reconnect the thunderbolt connection to my MacBook Pro in order for the Thunderbolt display to start working again. Anyone have an idea? Seems to be happening w/ Mavericks OS since it was installed.

    Joe,
    I've asked the Hosts to relocate your post to the Thunderbolt Display forum.
    There are a lot of folks there who've had the same problem - and there are som solutions posted there.
    Good luck,
    Clinton

  • After installing Yosemite, my macbook air crashes every time it wakes from 'longish' sleep

    I installed Yosemite.  All seemed to be fine.  But if my MacBook Air (mid 2012) goes to sleep due to inactivity (or if I close the lid), when I then wake it, it restarts and then gives me an error message saying that something went wrong and it had to be restarted.  If I choose 'Sleep' from the menu and then immediately wake it again, or close the lid and then open it within a few seconds, it's fine.  So perhaps it's a longer term sleep/wake period that is the problem?  Has anyone else experienced this?

    Further troubleshooting for my situation confirm that there is a conflict between having external three conductor 1/8" audio jack plug into my MBA at the same time when having thunderbolt HDMI cable plugged into external HP display going to sleep is fine however on wake there's a conflict between the audio assignment of these two devices causing an OS X crash where keyboard entry from the MacBook Air is no longer feasible to log into the system forcing a hard powerdown reset.
    Interesting tests prove if you plug-in Apple earbuds with the four conductor 1/8"'audio plug into the MBA audio port there is no problem as OS X likely sees these earbuds as a smart device versus a standard three conductor audio cable plug to external speakers or not. Several different Three conductor audio jacks/cables were tested and the crash upon sleep wake continued.
    After three conductor audio jack is plugged in but the HDMI is removed from thunderbolt then you wake the computer there is no conflict and it functions as intended No crash full functionality of all keyboards and mouse and put work correctly.
    Likewise conversely if you unplug the three conductor audio jack and just leave the thunderbolt HDMI external display plugged in upon wake everything functions as intended so it's not specifically related to external display or audio cable but when both are connected that the conflict crashes the system Upon sleep wake.
    Be reminded this configuration and scenario work perfectly fine prior to Yosemite OSX 10.10 update.
    Even went to the sound audio settings and forced audio output two headphone audio and crash and still consistent one HDMI is connected to thunderbolt port waking from sleep.
    Likely some trimming issues going on with the new Yosemite to do with audio assignment and potentially AirPlay. AiPlay was not being utilized however I have to Apple TVs that are in the background with AirPlay showing and the audio configuration settings but they were not being utilized at the time of these crashes.
    This issue has no variance regarding MBA screen is open or closed when putting to sleep and wake initiated by typing keyboard key.

  • Missing sound + missing USB power (sometimes) from Thunderbolt Display when waking from sleep

    Hi
    Two problems - one of which is driving med crazy!!
    Have the latest updates, and the display is connected to a MBA (mid 2011).
    The two are almost alwayes connected, and every time I wake the MBA from sleep, the Thunderbold Display does not "support usb sound" - the sound options are only MBA and headphones. Only a restart will give me the option to use Thunderbolt as sound output: WHAT TO DO!?!?!!
    Sometimes when waking from sleep the USB in the Display seems to be "off" - the will not charge my devices (iPhone, iPad etc.). Only reboot seems to fix this... I have seen this in other discussions but not found a permanent solution - any thoughts?

    Same here but reinstalling OSX is a bit drastic. I solved the problem by deleting a preference.
    Go to Macintosh HD then System then Library then Preference panes then Sound.prefPane
    Delete Sound.prefPane (you need to type your password).
    Logout or restart.
    This has happend twice this week so WHY is this suddenly occurring?
    Hi,
    I found this solution in the forum, but I can't find it again. I had cut and pasted it into a text file, because it solved my problem. I just don't want to take any credit for it. It did work for me. I had no problems for 3-4 weeks with the monitor, I have had the sound problem since last Friday. Very frustrating.
    BSGINC

  • Waking iMac has The disk was not ejected properly. I have OS 10.8.5 using My Book Thunderbolt Duo external HD.

    Waking iMac, since last OS10.8.5 update, gives "The disk was not ejected properly" message.  Western Digital sent a replacement drive to find out the problem doesn't go away. I have tried Option, Command, R and P at start up. This doesn't help. Anything else I might try to rectify the situation?

    The drive is malfunctioning.
    If the drive has more than one interface (USB, FireWire, Thunderbolt, eSATA), try one of the other interfaces.
    Check that the data cable is securely inserted at both ends.
    Try a different cable.
    If you're connecting the drive through a hub, connect it directly to a built-in port on the Mac.
    If you're connecting it directly, try a different port.
    Disconnect all other devices on the bus, or as many as possible.
    If the drive is bus-powered, but has an AC adapter, connect the adapter.
    If the drive doesn't work under any of the above conditions, it has to be replaced. You may be able to salvage the mechanism by removing it from the enclosure and installing it in another one, or in a drive dock.

  • Retina macbook pro with thunderbolt ethernet adaptor drops internet connection on open apps after waking

    I recently started using a thunderbolt ethernet adaptor and every time my comuter wakes from sleep, all the apps that were open no longer use the internet connection.  I have to restart each one of them for them to be able to use the present internet connection. any ideas?

    So I've noticed similar behaviour on my Macbook Air. It's a slightly different set of kit, since it's connected to a Belkin Thunderbolt Express Dock (http://www.belkin.com/uk/p/P-F4U055/). I'm on my second one of these because first one went back because it kept on dropping the internet connection (sounds familiar?) - and it *might* have been occurring when waking the system from sleep (I didn't make a mental note).
    Anyway the replacement was working perfectly, until today - when it's started to drop it's internet connection again, and this time I'm pretty certain that it's related to waking from sleep. The main difference now is that I *just* upgraded to Mavericks, and I wonder if the sleep problem has reared its ugly head again in the latest version of MacOS?
    All in all I have to say I'm pretty disappointed with the reliability of thunderbolt & the Belkin Dock thingie. Although it should be said that a single lead from my Macbook Air to the Express Dock is simultaneously carrying: video (1920x1200), Firewire800, 3xUSB3, gigabit ethernet and sound, so I'm not that surprised this technology is prone to the odd glitch, and the cables get really warm too!
    It would be great to have some solid information from Apple/Belkin about this.
    Cheers, Jon

  • Macbook not waking unless multiple thunderbolt displays are disconnected and reconnected

    My macbook not waking unless multiple thunderbolt displays are disconnected and reconnected

    Hello, mimmosan. 
    Thank you for visiting Apple Support Communities.
    Here are a couple troubleshooting steps that I would recommend.
    Intel-based Macs: Resetting the System Management Controller (SMC)
    http://support.apple.com/kb/HT3964
    About NVRAM and PRAM
    http://support.apple.com/kb/HT1379
    Cheers,
    Jason H..

  • High CPU load after waking with Thunderbolt Display connected

    I have a Mid-2013 MacBook Air 13" with Apple Thunderbolt Display connected. I use this setup mostly in a clamshell mode. Recently I've updated to OS X Mavericks. After that I've noticed that one of the cores is occupied by kernel_task to 100% after waking up from sleep. I've managed to isolate that to Apple Thunderbolt Display connected, without display there is a short CPU spike, but it comes down to normal levels in a couple of seconds.
    I've tried resetting SMC to no success. MacBook doesn't enter Safe Mode either (progress bar goes up to approx. 30% and it goes to reboot). Probably it's because of the Thunderbolt Display, I'm not really sure.
    That's not really a problem as this load doen't seem to impact CPU temp (fans are not spinning faster) and more of a activity monitor display glitch (?).
    Does anyone here encounter this?

    Hey Max,
    I also have one CPU core on my Air'13 to run 100% after a wake-up for about 1 minute (kernel_task).
    It is annoyingly like this after I upgraded to Maverics. Notice, I don't have a Thunderbolt monitor, just a laptop, no periphery.

  • Thunderbolt ethernet not waking after sleep

    I have the same problem with my MBP retina with Maverickks 10.9.1 losing connectivity after waking after sleep while on battery.
    People from apple support don't help in solving the problem.
    Does any one have the right solution? I would appreciate.
    Apple please fix this problem!!!

    Thanks for the link, Judy.
    As far as I know, I am up-to-date as far as OS updates are concerned. At least this is what the mac is telling me when I go to updates. The article you've linked here looks to be more specifically for OSX Lion and Snow Leopard, but not Yosemite.
    I would think that the likely fix here is to upgrade the firmware for thunderbolt, but I don't know how to check what macbook pro thunderbolt firmware or what thunderbolt display firmware is present. What I see in System Information doesn't match the firmware updates associated with your link.
    Here's what I have in System Information/Hardware/Thunderbolt Device Tree:
    Vendor Name:
    Apple Inc.
      Device Name:
    MacBook Pro
      UID:
    0x0001000A1
      Route String:
    0
      Firmware Version:
    20080d.0
      Domain UUID:
    F05339A8-AD68-2B57
      Port:
      Status:
    Device connected
      Link Status:
    0x2
      Speed:
    Up to 10 Gb/s x2
      Receptacle:
    1
      Port Micro Firmware Version:
    1.2.1
      Cable Firmware Version:
    0.1.18
      Cable Serial Number:
    C4M202701HCDNWFAG
    Thunderbolt Display:
      Vendor Name:
    Apple Inc.
      Device Name:
    Thunderbolt Display
      Vendor ID:
    0x1
      Device ID:
    0x8002
      Device Revision:
    0x1
      UID:
    0x00010001001
      Route String:
    1
      Firmware Version:
    22.2
      Port (Upstream):
      Status:
    Device connected
      Link Status:
    0x2
      Speed:
    Up to 10 Gb/s x2
      Port Micro Firmware Version:
    0.0.21
      Cable Firmware Version:
    0.1.18
      Cable Serial Number:
    C4M202701HCDN
      Port:
      Status:
    No device connected
      Link Status:
    0x7
      Speed:
    Up to 10 Gb/s x2
      Port Micro Firmware Version:
    0.0.21
    Do you know from this info if they need updating? It's not really made clear what to look for from the article. The article refers to Thunderbolt firmware v1.0, the Thunderbolt display firmware update is v1.1.
    Any ideas? Is there somewhere else I should look for this info?
    Regards
    Craig.

  • Thunderbolt Display has issue with weird washed-out colors after waking from sleep (after upgrade to Mavericks)

    I've got a Thunderbolt Display that I use with my Macbook Air (mid 2012) - usually in clamshell mode.
    When I let the computer go to sleep, and then wake it up by clicking the mouse, the monitor turns back on but the colors are washed out and purple looking. 
    The display goes back to normal when I unplug and replug it to my laptop.
    I first noticed this problem after upgrading to Mavericks.
    I made a video demonstrating the issue here:
    http://www.youtube.com/watch?v=19179-MVpWA&feature=youtu.be
    Any ideas?
    Thanks!
    Will

    Same thing for me too.  Late 2012 13" MBP Retina.  I have to unplug the Thunderbolt cable and plug it back in.
    This has only started for me in the last two days.  The first two weeks of Mavericks was ok.
    Update:  I just got back from a trip.  I was using the laptop separate from the Thunderbolt display.  I hadn't restarted since I returned and connected the monitor.  I've just rebooted, and put the computer to sleep.  After resuming from sleep, the display is ok.  Maybe try rebooting?  I'll update if it continues.

  • Thunderbolt display: devices not discovered after using Mini DisplayPort–to–VGA adapter

    I have an interested problem related to using my MacBook Air in clamshell (closed) mode, connected to a Thunderbolt display. The problem appears to be related to moving my MacBook air between my office and my home.
    At the office, I use the MacBook Air with an external VGA display, connected via the Mini DisplayPort–to–VGA adapter. At home, I use the MacBook Air together with a Thunderbolt display. An Apple USB keyboard is also connected to the display.
    Mini DisplayPort–to–VGA adapter implicated
    The following sequence of events causes the problem to occur:
    Use the MacBook air (open) together with a VGA display, connected via a Mini DisplayPort–to–VGA adapter (depicted at right);
    Put the MacBook Air to sleep by closing the lid, and disconnect the Mini DisplayPort–to–VGA adapter (I am not sure if the order of these two steps is significant—I usually perform them almost simultaneously when packing up my MacBook Air and getting ready to leave the office); and
    With the MacBook Air still closed, connect it to a Thunderbolt display with a connected USB keyboard.
    At this point, I would expect to be able to wake up the MacBook Air by tapping on the space bar of the keyboard. However, what I have observed is that this does not wake the MacBook Air.
    I can wake the MacBook however by moving or clicking a Bluetooth mouse that is paired with the MacBook Air.
    At this point, although the MacBook Air is awake, and the display is working, the USB keyboard connected to the display still does not work. This is the problem, in a nutshell.
    Unplugging the USB keyboard from the display, and plugging it back in causes the MacBook Air properly to identify the keyboard.
    I used Apple System Profiler to save a list of identified devices at two points in time:
    Immediately after waking the MacBook Air by moving the Bluetooth mouse (at which point the USB keyboard was not working); and
    After unplugging and plugging in again the USB keyboard (at which point the USB keyboard worked fine).
    Many devices are enumerated in the second list that are missing from the first. For example:
    Keyboard Hub@fe110000  <class IOUSBHubDevice, id 0x1000378ef, !registered, !matched, inactive, busy 3 (37993 ms), retain 6>
    AppleUSBHub  <class AppleUSBHub, id 0x1000378f2, !registered, !matched, inactive, busy 1 (37987 ms), retain 6>
    IOUSBInterface@0  <class IOUSBInterface, id 0x1000378f4, !registered, !matched, inactive, busy 1 (37986 ms), retain 6>
    Keyboard Hub@fe110000  <class IOUSBHubDevice, id 0x1000378f6, registered, matched, active, busy 0 (7 ms), retain 10>
    AppleUSBHub  <class AppleUSBHub, id 0x1000378f9, registered, matched, active, busy 0 (1 ms), retain 9>
    IOUSBInterface@0  <class IOUSBInterface, id 0x1000378fb, !registered, !matched, active, busy 0, retain 7>
    Apple Keyboard@fe112000  <class IOUSBDevice, id 0x1000378fd, registered, matched, active, busy 0 (112 ms), retain 11>
    and many child devices…
    Using the Mini DisplayPort–to–VGA adapter appears to be a necessary step to causing this problem to occur. If I merely disconnect the MacBook Air from the display, let it go to sleep, and then reconnect it again, the USB keyboard will work immediately and can be used to wake the computer from sleep.
    Some devices are discovered even when the computer is in sleep mode. This is how it should work.
    The problem appears to be that when a Mini DisplayPort–to–VGA adapter has been used since the last time the computer was connected to a Thunderbolt display, the MacBook air does not discover devices completely when it is again connected to the Thunderbolt display while in sleep mode.
    Can anyone else reproduce this problem?

    Hi glraczon.support,
    It sounds like the external display you are using (projector) operates at a smaller resolution than your MacBook Pro. You may want to configure the display preferences in System Preferences for the external projector.
    Here is an article that may help you with that process:
    OS X Mountain Lion: About the Display pane of System Preferences
    http://support.apple.com/kb/HT5369
    Thanks,
    Matt M.

  • Macbook Pro Mid 2012 w/ Thunderbolt built in display - Green light stays on constantly...

    Just recently this week,  the green light next to the isight/webcam built in on my Thunderbolt 27" monitor just stays on mostly all the time.  I have followed all of the troubleshooting steps of resetting the PRUM and MCU, placing the computer to sleep, waking it up, shutting it down, doing a hard shutdown (holding down the power button on the laptop itself)   Shutting down the computer, unplugging everything,  unplugging the power cords.  I have TRIED EVERYTHING..... and for whatever reason the green light next to the built in webcam on my Thunderbolt 27" monitor connected to my MacbookPro (I've always had the laptop lid closed)  the light stays on......   
    I beg anyone who has had this problem, please respond and help.    Also,  FYI   I have NOT downloaded any new software or uninstalled anything... I work from home and this is my WORK PC.  The only thing I tired doing when this started happening was join a google hangout.... and that's when it started
    since then,  I have uninstalled google chrome from my mac and also uninstalled the googlevoiceandtalk   application using a script from google that I ran in the Terminal with SUDO.
    I'm a owner of a Macbook Pro 15-Inch, Mid 2012 with OS X Mavericks Ver 10.9.1
    Processor  8 GB  1600 MHz DDR3
    Software OS X 10.9.1 (13842)
    Apple Thunderbolt Display with a built in HD webcam   2560x1440
    NVIDIA GeForce GT 650M 1024 MB Graphics
    MANY MANY Thanks,
    Ronnie 
    I hope to hear from someone.

    Took it to the apple store. The problem was my logic board. I sent it off to be replaced.

  • 10.9.3 - Display is black after waking up from sleep

    I have a Retina MacBook Pro that I connect to two monitors at work in clamshell mode, 1 via HDMI and 1 via the MiniDP -> DVI adapter. Typically, before leaving work I put the machine to sleep manually before unplugging everything.
    Since upgrading to 10.9.3, almost everytime I open the lid of my MacBook, the display is black and will never initialize. It's not off as I can see that the backlight is lit. I can't find any key combination that does anything other than just holding down the power button.
    This is a serious issue as it essentially prevents me from being able to continue any work from my desk to home.
    I've done the usual, cleared SMC, PRAM.
    Below are the logs prior to waking up the machine. It seems that it attempted to wake-up some 10 minutes before I opened the lid and didn't find any displays. It then goes into this weird mode.
    The 4:28 event is the "wake up" while it was still in my bag.
    At 4:41 is me actually opening the lid and getting the black screen.
    Any advice? This did not happen in 10.9.2, even once.
    5/21/14 4:28:35.000 PM kernel[0]: AirPort_Brcm43xx::powerChange: System Wake - Full Wake/ Dark Wake / Maintenance wake
    5/21/14 4:28:35.000 PM kernel[0]: Previous Sleep Cause: 5
    5/21/14 4:28:35.000 PM kernel[0]: AppleThunderboltNHI::prePCIWake - power up complete - took 0 us
    5/21/14 4:28:35.000 PM kernel[0]: IOPPF: Sent gpu-external-plimit-notification last value 0 (rounded time weighted average 0)
    5/21/14 4:28:35.000 PM kernel[0]: IOPPF: Sent gpu-internal-plimit-notification last value 0 (rounded time weighted average 0)
    5/21/14 4:28:35.000 PM kernel[0]: AppleThunderboltHAL::earlyWake - complete - took 1 milliseconds
    5/21/14 4:28:35.000 PM kernel[0]: Thunderbolt Self-Reset Count = 0xedefbe00
    5/21/14 4:28:35.000 PM kernel[0]: IOThunderboltSwitch<0xffffff802fed0e00>(0x0)::listenerCallback - Thunderbolt HPD packet for route = 0x0 port = 11 unplug = 0
    5/21/14 4:28:35.000 PM kernel[0]: TBT W (2): 0x0100 [x]
    5/21/14 4:28:35.000 PM kernel[0]: IOThunderboltSwitch<0xffffff802fed0e00>(0x0)::listenerCallback - Thunderbolt HPD packet for route = 0x0 port = 12 unplug = 0
    5/21/14 4:28:35.000 PM kernel[0]: en0: 802.11d country code set to 'X0'.
    5/21/14 4:28:35.000 PM kernel[0]: en0: Supported channels 1 2 3 4 5 6 7 8 9 10 11 36 40 44 48 52 56 60 64 100 104 108 112 116 120 124 128 132 136 140 149 153 157 161 165
    5/21/14 4:28:35.000 PM kernel[0]: AppleUSBMultitouchDriver::checkStatus - received Status Packet, Payload 2: device was reinitialized
    5/21/14 4:28:35.427 PM hidd[68]: MultitouchHID: device bootloaded
    5/21/14 4:28:35.932 PM UserEventAgent[11]: Captive: CNPluginHandler en0: Inactive
    5/21/14 4:28:35.933 PM configd[18]: network changed: v4(en0-:10.40.3.117) DNS- Proxy- SMB-
    5/21/14 4:28:35.933 PM vmnet-bridge[897]: Dynamic store changed
    5/21/14 4:28:35.934 PM vmnet-bridge[897]: Failed to read SCproperties for key: State:/Network/Global/IPv4
    5/21/14 4:28:35.000 PM kernel[0]: vmnet: VMNetDisconnect called for port 0xffffff80472b8a00
    5/21/14 4:28:35.000 PM kernel[0]: vmnet: bridge-en0: filter detached
    5/21/14 4:28:35.000 PM kernel[0]: vmnet: bridge-en0: down
    5/21/14 4:28:35.000 PM kernel[0]: vmnet: bridge-en0: detached
    5/21/14 4:28:35.000 PM kernel[0]: vmnet: Freeing hub at 0xffffff8036465000.
    5/21/14 4:28:35.934 PM vmnet-bridge[897]: Stopping bridge for: en0
    5/21/14 4:28:35.941 PM netbiosd[14396]: network_reachability_changed : network is not reachable, netbiosd is shutting down
    5/21/14 4:28:35.974 PM WindowServer[86]: _CGXHWCaptureWindowList: No capable active display found.
    5/21/14 4:28:36.004 PM WindowServer[86]: _CGXHWCaptureWindowList: No capable active display found.
    5/21/14 4:28:36.000 PM kernel[0]: en0: 802.11d country code set to 'US'.
    5/21/14 4:28:36.000 PM kernel[0]: en0: Supported channels 1 2 3 4 5 6 7 8 9 10 11 36 40 44 48 52 56 60 64 100 104 108 112 116 120 124 128 132 136 140 149 153 157 161 165
    5/21/14 4:28:36.000 PM kernel[0]: vmnet: VMNetSetopt: Set link state DOWN
    5/21/14 4:28:36.000 PM kernel[0]: vmnet: VMNetSetopt: Set link state UP
    5/21/14 4:28:37.000 PM kernel[0]: AirPort_Brcm43xx::powerChange: System Sleep
    5/21/14 4:28:37.000 PM kernel[0]: hibernate image path: /var/vm/sleepimage
    5/21/14 4:28:37.000 PM kernel[0]: efi pagecount 63
    5/21/14 4:28:37.000 PM kernel[0]: hibernate_page_list_setall(preflight 1) start 0xffffff825350a000, 0xffffff8253a1e000
    5/21/14 4:28:37.000 PM kernel[0]: hibernate_page_list_setall time: 443 ms
    5/21/14 4:28:37.000 PM kernel[0]: pages 2941765, wire 533839, act 1370647, inact 20672, cleaned 0 spec 4060, zf 242088, throt 0, compr 217633, xpmapped 81119
    5/21/14 4:28:37.000 PM kernel[0]: could discard act 93909 inact 189335 purgeable 46214 spec 223368 cleaned 0
    5/21/14 4:28:37.000 PM kernel[0]: hibernate_page_list_setall preflight pageCount 533839 est comp 46 setfile 1088506560 min 1073741824
    5/21/14 4:28:37.000 PM kernel[0]: VNOP_ALLOCATE(0) 14766080
    5/21/14 4:28:37.000 PM kernel[0]: [0x376c8fb000, 0x19000000]
    5/21/14 4:28:37.000 PM kernel[0]: [0x37bc8b4000, 0x27e15000]
    5/21/14 4:28:37.000 PM kernel[0]: [0x0, 0x0]
    5/21/14 4:28:37.000 PM kernel[0]: kern_open_file_for_direct_io(0) took 0 ms
    5/21/14 4:28:37.000 PM kernel[0]: Opened file /var/vm/sleepimage, size 1088507904, partition base 0x0, maxio 2000000 ssd 1
    5/21/14 4:28:37.000 PM kernel[0]: hibernate image major 1, minor 0, blocksize 4096, pollers 5
    5/21/14 4:41:01.000 PM kernel[0]: IOPPF: Sent cpu-plimit-notification last value 24 (rounded time weighted average 24)
    5/21/14 4:41:01.000 PM kernel[0]: IOPPF: Sent gpu-external-plimit-notification last value 12 (rounded time weighted average 8)
    5/21/14 4:41:01.000 PM kernel[0]: IOPPF: Sent gpu-internal-plimit-notification last value 12 (rounded time weighted average 8)
    5/21/14 4:41:01.000 PM kernel[0]: IOPPF: Sent gpu-external-plimit-notification last value 15 (rounded time weighted average 15)
    5/21/14 4:41:01.000 PM kernel[0]: IOPPF: Sent gpu-internal-plimit-notification last value 14 (rounded time weighted average 14)
    5/21/14 4:41:01.000 PM kernel[0]: IOPPF: Sent cpu-plimit-notification last value 29 (rounded time weighted average 29)
    5/21/14 4:41:01.000 PM kernel[0]: vm_compressor_flush - starting
    5/21/14 4:41:01.000 PM kernel[0]: IOPPF: Sent gpu-external-plimit-notification last value 8 (rounded time weighted average 10)
    5/21/14 4:41:01.000 PM kernel[0]: IOPPF: Sent gpu-internal-plimit-notification last value 13 (rounded time weighted average 13)
    5/21/14 4:41:01.000 PM kernel[0]: IOPPF: Sent cpu-plimit-notification last value 23 (rounded time weighted average 26)
    5/21/14 4:41:01.000 PM kernel[0]: pci pause: SDXC
    5/21/14 4:41:01.000 PM kernel[0]: IOPPF: Sent gpu-external-plimit-notification last value 3 (rounded time weighted average 5)
    5/21/14 4:41:01.000 PM kernel[0]: IOPPF: Sent gpu-internal-plimit-notification last value 8 (rounded time weighted average 10)
    5/21/14 4:41:01.000 PM kernel[0]: IOPPF: Sent cpu-plimit-notification last value 17 (rounded time weighted average 19)
    5/21/14 4:41:01.000 PM kernel[0]: vm_compressor_flush completed - took 22525 msecs
    5/21/14 4:41:01.000 PM kernel[0]: hibernate_flush_memory: buffer_cache_gc freed up 25099 wired pages
    5/21/14 4:41:01.000 PM kernel[0]: hibernate_alloc_pages act 241315, inact 211360, anon 56665, throt 0, spec 227275, wire 533994, wireinit 172255
    5/21/14 4:41:01.000 PM kernel[0]: hibernate_setup(0) took 55582 ms
    5/21/14 4:29:33.000 PM kernel[0]: AppleThunderboltNHIType2::waitForOk2Go2Sx - retries = 5
    5/21/14 4:41:01.000 PM kernel[0]: hibernate_page_list_setall(preflight 0) start 0xffffff825350a000, 0xffffff8253a1e000
    5/21/14 4:41:01.000 PM kernel[0]: hibernate_teardown started
    5/21/14 4:41:01.000 PM kernel[0]: hibernate_teardown: wired_pages 539094, free_pages 3537922, active_pages 69141, inactive_pages 13763, speculative_pages 5, cleaned_pages 0, compressor_pages 57
    5/21/14 4:41:01.000 PM kernel[0]: hibernate_teardown_pmap_structs done: last_valid_compact_indx 443303
    5/21/14 4:41:01.000 PM kernel[0]: hibernate_teardown: mark_as_unneeded_pages 8192, 61390, 32867
    5/21/14 4:41:01.000 PM kernel[0]: hibernate_teardown completed - discarded 102449
    5/21/14 4:41:01.000 PM kernel[0]: hibernate_page_list_setall time: 1108 ms
    5/21/14 4:41:01.000 PM kernel[0]: pages 1093183, wire 413176, act 69141, inact 13763, cleaned 0 spec 5, zf 0, throt 0, compr 57, xpmapped 82909
    5/21/14 4:41:01.000 PM kernel[0]: did discard act 131384 inact 192173 purgeable 46214 spec 227270 cleaned 0
    5/21/14 4:41:01.000 PM kernel[0]: hibernate_page_list_setall found pageCount 496142
    5/21/14 4:41:01.000 PM kernel[0]: IOHibernatePollerOpen, ml_get_interrupts_enabled 0
    5/21/14 4:41:01.000 PM kernel[0]: IOHibernatePollerOpen(0)
    5/21/14 4:41:01.000 PM kernel[0]: encryptStart 14010
    5/21/14 4:41:01.000 PM kernel[0]: bitmap_size 0x7f4e0, previewSize 0x0, writing 495805 pages @ 0x934f0
    5/21/14 4:41:01.000 PM kernel[0]: hibernate_rebuild started
    5/21/14 4:41:01.000 PM kernel[0]: hibernate_rebuild_pmap_structs done: last_valid_compact_indx 443303
    5/21/14 4:41:01.000 PM kernel[0]: hibernate_rebuild completed - took 115 msecs
    5/21/14 4:41:01.000 PM kernel[0]: booter start at 1283 ms smc 0 ms, [14, 0, 0] total 1743 ms, dsply 392, 0 ms, tramp 1396 ms
    5/21/14 4:41:01.000 PM kernel[0]: hibernate_machine_init: state 2, image pages 412973, sum was b3195d19, imageSize 0x3bbec000, image1Size 0x288e3000, conflictCount 7079, nextFree 1960
    5/21/14 4:41:01.000 PM kernel[0]: hibernate_newruntime_map time: 0 ms, IOHibernatePollerOpen(), ml_get_interrupts_enabled 0
    5/21/14 4:41:01.000 PM kernel[0]: IOHibernatePollerOpen(0) 6 ms
    5/21/14 4:41:01.000 PM kernel[0]: hibernate_machine_init reading
    5/21/14 4:41:01.000 PM kernel[0]: PMStats: Hibernate read took 659 ms
    5/21/14 4:41:01.000 PM kernel[0]: hibernate_machine_init pagesDone 495939 sum2 3e9b893c, time: 659 ms, disk(0x20000) 470 Mb/s, comp bytes: 126795776 time: 113 ms 1061 Mb/s, crypt bytes: 321949696 time: 129 ms 2375 Mb/s
    5/21/14 4:41:01.000 PM kernel[0]: Wake reason: EC.LidOpen (User)
    5/21/14 4:41:01.000 PM kernel[0]: AirPort_Brcm43xx::powerChange: System Wake - Full Wake/ Dark Wake / Maintenance wake
    5/21/14 4:41:01.000 PM kernel[0]: Previous Sleep Cause: 5
    5/21/14 4:41:01.000 PM kernel[0]: Previous Shutdown Cause: 0
    5/21/14 4:41:01.000 PM kernel[0]: IOPPF: Sent cpu-plimit-notification last value 0 (rounded time weighted average 0)
    5/21/14 4:41:01.000 PM kernel[0]: IOPPF: Sent gpu-external-plimit-notification last value 0 (rounded time weighted average 0)
    5/21/14 4:41:01.000 PM kernel[0]: IOPPF: Sent gpu-internal-plimit-notification last value 0 (rounded time weighted average 0)
    5/21/14 4:41:01.000 PM kernel[0]: AppleThunderboltNHI::prePCIWake - power up complete - took 0 us
    5/21/14 4:41:01.000 PM kernel[0]: AppleThunderboltHAL::earlyWake - complete - took 6 milliseconds
    5/21/14 4:41:01.000 PM kernel[0]: Thunderbolt Self-Reset Count = 0xedefbe00
    5/21/14 4:41:01.000 PM kernel[0]: TBT W (2): 0x0100 [x]
    5/21/14 4:41:01.000 PM kernel[0]: IOThunderboltSwitch<0xffffff802fed0e00>(0x0)::listenerCallback - Thunderbolt HPD packet for route = 0x0 port = 11 unplug = 0
    5/21/14 4:41:01.000 PM kernel[0]: IOThunderboltSwitch<0xffffff802fed0e00>(0x0)::listenerCallback - Thunderbolt HPD packet for route = 0x0 port = 12 unplug = 0
    5/21/14 4:41:01.772 PM loginwindow[63]: CoreAnimation: warning, deleted thread with uncommitted CATransaction; set CA_DEBUG_TRANSACTIONS=1 in environment to log backtraces.
    5/21/14 4:41:01.798 PM mDNSResponder[60]:  71: Could not write data to clientPID[18](configd)  because of error - aborting connection
    5/21/14 4:41:01.807 PM mDNSResponder[60]:  71: DNSServiceCreateConnection: 0 registered records, 14 kDNSServiceFlagsShareConnection operations PID[18](configd)
    5/21/14 4:41:01.807 PM mDNSResponder[60]:  ->  DNSServiceGetAddrInfo      v4v6 p03-streams.icloud.com. PID[18]()
    5/21/14 4:41:01.807 PM mDNSResponder[60]:  ->  DNSServiceGetAddrInfo      v4v6 c2s.triu.com.webexconnect.com. PID[18]()
    5/21/14 4:41:01.807 PM mDNSResponder[60]:  ->  DNSServiceGetAddrInfo      v4v6 1-courier.sandbox.push.apple.com. PID[18]()
    5/21/14 4:41:01.807 PM mDNSResponder[60]:  ->  DNSServiceGetAddrInfo      v4v6 www.apple.com. PID[18]()
    5/21/14 4:41:01.807 PM mDNSResponder[60]:  ->  DNSServiceGetAddrInfo      v4v6 www.apple.com. PID[18]()
    5/21/14 4:41:01.807 PM mDNSResponder[60]:  ->  DNSServiceGetAddrInfo      v4v6 talk.l.google.com. PID[18]()
    5/21/14 4:41:01.807 PM mDNSResponder[60]:  ->  DNSServiceGetAddrInfo      v4v6 1-courier.push.apple.com. PID[18]()
    5/21/14 4:41:01.808 PM mDNSResponder[60]:  ->  DNSServiceGetAddrInfo      v4v6 p03-streams.icloud.com. PID[18]()
    5/21/14 4:41:01.808 PM mDNSResponder[60]:  ->  DNSServiceGetAddrInfo      v4v6 c2s.triu.com.webexconnect.com. PID[18]()
    5/21/14 4:41:01.808 PM mDNSResponder[60]:  ->  DNSServiceGetAddrInfo      v4v6 1-courier.sandbox.push.apple.com. PID[18]()
    5/21/14 4:41:01.808 PM mDNSResponder[60]:  ->  DNSServiceGetAddrInfo      v4v6 www.apple.com. PID[18]()
    5/21/14 4:41:01.808 PM mDNSResponder[60]:  ->  DNSServiceGetAddrInfo      v4v6 talk.google.com. PID[18]()
    5/21/14 4:41:01.808 PM mDNSResponder[60]:  ->  DNSServiceGetAddrInfo      v4v6 www.apple.com. PID[18]()
    5/21/14 4:41:01.808 PM mDNSResponder[60]:  ->  DNSServiceGetAddrInfo      v4v6 1-courier.push.apple.com. PID[18]()
    5/21/14 4:41:03.649 PM AddressBookSourceSync[16521]: -[ABAddressBook save] failed. (<ABAddressBook: 0x7fb19342b420>)
    5/21/14 4:41:03.000 PM kernel[0]: IOBluetoothUSBDFU::probe
    5/21/14 4:41:03.000 PM kernel[0]: IOBluetoothUSBDFU::probe ProductID - 0x8286 FirmwareVersion - 0x0131
    5/21/14 4:41:04.000 PM kernel[0]: IOBluetoothUSBDFU::probe
    5/21/14 4:41:04.000 PM kernel[0]: IOBluetoothUSBDFU::probe ProductID - 0x8286 FirmwareVersion - 0x0131
    5/21/14 4:41:04.000 PM kernel[0]: **** [IOBluetoothHostControllerUSBTransport][start] -- completed -- result = TRUE -- 0xa000 ****
    5/21/14 4:41:04.000 PM kernel[0]: **** [BroadcomBluetoothHostControllerUSBTransport][start] -- Completed -- 0xa000 ****
    5/21/14 4:41:04.000 PM kernel[0]: [IOBluetoothHCIController][staticBluetoothHCIControllerTransportShowsUp] -- Received Bluetooth Controller register service notification -- 0xa000
    5/21/14 4:41:04.000 PM kernel[0]: [IOBluetoothHCIController::setConfigState] calling registerService
    5/21/14 4:41:04.000 PM kernel[0]: **** [IOBluetoothHCIController][protectedBluetoothHCIControllerTransportShowsUp] -- Connected to the transport successfully -- 0x8a00 -- 0x0800 -- 0xa000 ****
    5/21/14 4:41:04.420 PM digest-service[16542]: label: default
    5/21/14 4:41:04.420 PM digest-service[16542]:           dbname: od:/Local/Default
    5/21/14 4:41:04.420 PM digest-service[16542]:           mkey_file: /var/db/krb5kdc/m-key
    5/21/14 4:41:04.420 PM digest-service[16542]:           acl_file: /var/db/krb5kdc/kadmind.acl
    5/21/14 4:41:04.000 PM kernel[0]: **** [IOBluetoothHostControllerUSBTransport][SuspendDevice] -- Suspend -- suspendDeviceCallResult = 0x0000 (kIOReturnSuccess) -- 0xa000 ****
    5/21/14 4:41:04.508 PM digest-service[16542]: digest-request: uid=0
    5/21/14 4:41:04.706 PM digest-service[16542]: digest-request: netr probe 0
    5/21/14 4:41:04.707 PM digest-service[16542]: digest-request: init request
    5/21/14 4:41:04.710 PM digest-service[16542]: digest-request: init return domain: MACBOOKPRO-D6D5 server: AARONS-MACBOOK-PRO indomain was: <NULL>
    5/21/14 4:41:04.000 PM kernel[0]: AppleUSBMultitouchDriver::checkStatus - received Status Packet, Payload 2: device was reinitialized
    5/21/14 4:41:04.990 PM digest-service[16542]: digest-request: uid=0
    5/21/14 4:41:04.990 PM digest-service[16542]: digest-request: init request
    5/21/14 4:41:04.993 PM digest-service[16542]: digest-request: init return domain: MACBOOKPRO-D6D5 server: AARONS-MACBOOK-PRO indomain was: <NULL>
    5/21/14 4:41:07.462 PM eapolclient[14386]: en0 STOP
    5/21/14 4:41:08.939 PM CalendarAgent[191]: [com.apple.calendar.store.log.caldav.queue] [Account refresh failed with error: Error Domain=NSURLErrorDomain Code=-1009 "The Internet connection appears to be offline." UserInfo=0x7fbb0bf328b0 {NSUnderlyingError=0x7fbb0ef50540 "The Internet connection appears to be offline.", NSErrorFailingURLStringKey=https://longwa%[email protected]/calendar/dav/longwa%40gmail.com/user///longwa%[email protected]/calendar/dav/longwa%40gmail.com/user/, NSErrorFailingURLKey=https://longwa%[email protected]/calendar/dav/longwa%40gmail.com/user///longwa%[email protected]/calendar/dav/longwa%40gmail.com/user/, AccountName=Google, CalDAVErrFromRefresh=YES, NSLocalizedDescription=The Internet connection appears to be offline.}]
    5/21/14 4:41:08.940 PM CalendarAgent[191]: [com.apple.calendar.store.log.caldav.queue] [Adding [<CalDAVAccountRefreshQueueableOperation: 0x7fbb09d5fef0; Sequence: 0>] to failed operations.]
    5/21/14 4:41:08.942 PM CalendarAgent[191]: [com.apple.calendar.store.log.caldav.queue] [Account refresh failed with error: Error Domain=NSURLErrorDomain Code=-1009 "The Internet connection appears to be offline." UserInfo=0x7fbb09e229d0 {NSUnderlyingError=0x7fbb09c27a70 "The Internet connection appears to be offline.", NSErrorFailingURLStringKey=https://longwa%[email protected]/90451300/principal///longwa%[email protected]/90451300/principal/, NSErrorFailingURLKey=https://longwa%[email protected]/90451300/principal///longwa%[email protected]/90451300/principal/, AccountName=iCloud, CalDAVErrFromRefresh=YES, NSLocalizedDescription=The Internet connection appears to be offline.}]
    5/21/14 4:41:08.947 PM CalendarAgent[191]: [com.apple.calendar.store.log.caldav.queue] [Adding [<CalDAVAccountRefreshQueueableOperation: 0x7fbb0b9a0ba0; Sequence: 0>] to failed operations.]
    5/21/14 4:41:09.327 PM Calendar[16019]: [com.apple.calendar.ui.log] [An error exists on principal: [iCloud]]
    5/21/14 4:41:09.330 PM Calendar[16019]: [com.apple.calendar.ui.log] [An error exists on principal: [Google]]
    5/21/14 4:41:10.000 PM kernel[0]: MacAuthEvent en0   Auth result for: 90:84:0d:d6:3a:d2  MAC AUTH succeeded
    5/21/14 4:41:10.000 PM kernel[0]: wlEvent: en0 en0 Link UP virtIf = 0
    5/21/14 4:41:10.000 PM kernel[0]: AirPort: Link Up on en0
    5/21/14 4:41:10.000 PM kernel[0]: en0: BSSID changed to 90:84:0d:d6:3a:d2
    5/21/14 4:41:10.000 PM kernel[0]: AirPort: RSN handshake complete on en0
    5/21/14 4:41:11.083 PM vmnet-bridge[897]: Preferences changed called
    5/21/14 4:41:11.000 PM kernel[0]: flow_divert_kctl_disconnect (0): disconnecting group 1
    5/21/14 4:41:11.547 PM airportd[82]: _doAutoJoin: Already associated to “silver_arrow”. Bailing on auto-join.
    5/21/14 4:41:16.518 PM configd[18]: network changed: DNS* Proxy
    5/21/14 4:41:16.523 PM UserEventAgent[11]: Captive: [CNInfoNetworkActive:1655] en0: SSID 'silver_arrow' making interface primary (cache indicates network not captive)
    5/21/14 4:41:16.524 PM UserEventAgent[11]: Captive: CNPluginHandler en0: Evaluating
    5/21/14 4:41:16.526 PM UserEventAgent[11]: Captive: en0: Not probing 'silver_arrow' (cache indicates not captive)
    5/21/14 4:41:16.526 PM UserEventAgent[11]: Captive: CNPluginHandler en0: Authenticated
    5/21/14 4:41:16.528 PM configd[18]: network changed: v4(en0!:192.168.200.109) DNS+ Proxy+ SMB
    5/21/14 4:41:16.529 PM vmnet-bridge[897]: Dynamic store changed
    5/21/14 4:41:16.000 PM kernel[0]: vmnet: VNetUserIf_Create: created userIf at 0xffffff805131e000.
    5/21/14 4:41:16.000 PM kernel[0]: vmnet: VMNetConnect: returning port 0xffffff805131e000
    5/21/14 4:41:16.000 PM kernel[0]: vmnet: Hub 0 does not exist, allocating memory.
    5/21/14 4:41:16.000 PM kernel[0]: vmnet: Allocated hub 0xffffff8031954000 for hubNum 0.
    5/21/14 4:41:16.000 PM kernel[0]: vmnet: VMNET_SO_BINDTOHUB: port: paddr 00:50:56:f2:af:bd
    5/21/14 4:41:16.000 PM kernel[0]: vmnet: Hub 0
    5/21/14 4:41:16.000 PM kernel[0]: vmnet:           Port 0
    5/21/14 4:41:16.000 PM kernel[0]: vmnet: bridge-en0: media 80 dev 0xffffff8030aa6558 family 2
    5/21/14 4:41:16.000 PM kernel[0]: vmnet: bridge-en0: wireless interface detected.
    5/21/14 4:41:16.000 PM kernel[0]: vmnet: bridge-en0: up
    5/21/14 4:41:16.000 PM kernel[0]: vmnet: bridge-en0: attached
    5/21/14 4:41:16.000 PM kernel[0]: vmnet: VNetUserIfFree: freeing userIf at 0xffffff805131e000.
    5/21/14 4:41:16.547 PM vmnet-bridge[897]: Started bridge for 0, en0
    5/21/14 4:41:16.000 PM kernel[0]: vmnet: VMNetSetopt: Set link state DOWN
    5/21/14 4:41:16.000 PM kernel[0]: vmnet: VMNetSetopt: Set link state UP
    5/21/14 4:41:18.087 PM apsd[80]: Unrecognized leaf certificate
    5/21/14 4:41:19.254 PM ntpd[92]: ntpd: wake time set -0.423353 s
    5/21/14 4:41:19.267 PM com.apple.time[157]: Interval maximum value is 946100000 seconds (specified value: 9223372036854775807).
    5/21/14 4:41:19.270 PM com.apple.time[157]: Interval maximum value is 946100000 seconds (specified value: 9223372036854775807).
    5/21/14 4:41:19.654 PM com.apple.time[157]: Interval maximum value is 946100000 seconds (specified value: 9223372036854775807).
    5/21/14 4:41:20.239 PM Calendar[16019]: CoreData: warning: An NSManagedObjectContext delegate overrode fault handling behavior to silently delete the object with ID '0x60800020d810 <x-coredata://023D0C8A-A6F8-4E29-93C2-B88F12740C96/CalDAVError/p34>' and substitute nil/0 for all property values instead of throwing.
    5/21/14 4:41:20.240 PM Calendar[16019]: [com.apple.calendar.ui.log] [An error exists on principal: [Google]]
    5/21/14 4:41:22.799 PM com.apple.SecurityServer[14]: Session 100033 created
    5/21/14 4:41:45.000 PM kernel[0]: pci pause: SDXC
    5/21/14 4:41:46.000 PM kernel[0]: NVDA::setPowerState(0xe810a8351ab1fe07, 0 -> 2) timed out after 45415 ms
    5/21/14 4:42:17.000 PM kernel[0]: MacAuthEvent en0   Auth result for: 00:1b:63:2a:e8:f3  MAC AUTH succeeded
    5/21/14 4:42:17.000 PM kernel[0]: wlEvent: en0 en0 Link UP virtIf = 0
    5/21/14 4:42:17.000 PM kernel[0]: AirPort: RSN handshake complete on en0
    5/21/14 4:42:17.000 PM kernel[0]: wl0: Roamed or switched channel, reason #1, bssid 00:1b:63:2a:e8:f3
    5/21/14 4:42:17.000 PM kernel[0]: en0: BSSID changed to 00:1b:63:2a:e8:f3
    5/21/14 4:42:20.000 PM kernel[0]: MacAuthEvent en0   Auth result for: 00:1b:63:2a:e8:f3  MAC AUTH succeeded
    5/21/14 4:42:20.000 PM kernel[0]: wlEvent: en0 en0 Link UP virtIf = 0
    5/21/14 4:42:20.000 PM kernel[0]: AirPort: RSN handshake complete on en0
    5/21/14 4:42:20.000 PM kernel[0]: wl0: Roamed or switched channel, reason #8, bssid 00:1b:63:2a:e8:f3
    5/21/14 4:42:20.000 PM kernel[0]: en0: BSSID changed to 00:1b:63:2a:e8:f3
    5/21/14 4:43:50.000 PM bootlog[0]: BOOT_TIME 1400705030 0

    Ok, more information for anyone that might care. The wake-up seems to be the familiar dark wake in order to go into hibernate mode. Except now, it's a death wake. Looking at the logs, I see that it happens exactly 70 minutes after sleeping, even though hibernatemode = 0 (which shouldn't hibernate at all!)
    So my power settings look like this:
    Currently in use:
    standbydelay         4200
    standby              1
    halfdim              1
    hibernatefile        /var/vm/sleepimage
    darkwakes            0
    gpuswitch            2
    disksleep            10
    sleep                10
    autopoweroffdelay    14400
    hibernatemode        0
    autopoweroff         1
    ttyskeepawake        1
    displaysleep         2
    acwake               0
    lidwake              1
    standbymode is 70 minutes, what a coincidence. I'm going to try setting it to 0 and see what that does.

  • I'm booting from a new LaCie Thunderbolt SSD and it won't wake from sleep.

    As my boot drive I have a new 1TB LaCie Thunderbolt SSD Disk. It's connected to a 27" 2.7 GHz Intel i5 iMac (mid 2011). I'm running OS X 10.8.2. Nothing else is connected on Thunderbolt.
    Everything runs fine and very fast, with the one exception of not waking from sleep.
    When I try to wake it up, the screen illuminates and the desktop is not completely frozen: I can drag windows around, but I can't open applications or do anything with the Finder. I get a spinning beachball if I move the cursor over the menu bar at the top. The only option is to restart.
    I've contacted LaCie and they say their devices are "storage devices" and not "system drives". Yet I've been running my system from a 1TB LaCie D2 for at least a couple of years. I pointed out to LaCie support that nowhere on the box does it say their devices are for storage only.
    Any suggestions?

    @Kappy - not the most useful of replies mate to be honest.After all, there is a strong possibility that this has everything to do with the way OS X and the thunderbolt interface handle wake from sleep states.
    @kbrine:
    I am having exactly the same problem but with slightly different hardware:
    iMac 27 (mid-2011) with Mountain Lion 10.8.2
    Booting from a Crucial M4 SSD in an OWC SATA enclosure connected to a Lacie eSata thunderbolt hub (which is connected to the iMac).
    In normal use the drive is super fast and works really well.
    But my problem is exactly as you describe, put the machine into sleep, and on wake everything appears to come back ok however you can't open apps from the dock and the spinning beachball appears. You can't do anything else and you have to reboot.
    Now the interesting thing is that if I put the machine to sleep and then wake it up again within 1 minute everything works perfectly. After a longer period of time - and I'm presuming when the energy saving profile moves to a deeper sleep state (I don't know for sure so speculation from me here) - I get the problem we are having and I have to reboot.
    Here's what I've tried so far:
    Updated my SSD to the latest firmware.
    No firmware updates available for the OWC enclosure nor the Lacie eSata hub (at least, not that I could find)
    Turned off bluetooth (others on this forum had a problem with BT interfering with Thunderbolt displays coming back on after sleep)
    Turned off 'Automatic Brightness Adjust' (again, based on Thunderbolt Display problems that others have reported)
    I've tried out AutoEJECT and Jettison apps that unmount all external drives and re-mount them when waking from sleep. They've made absolutely no difference. Save yourself a few $$ and don't bother buying them from the App Store.
    I've tried unplugging and re-inserting the Thunderbolt cable connecting my eSata hub to the iMac. No effect.
    And that's as far as I've got. There are only two things left for me to try:: disable 'Power Nap' which - apparently - can also cause problems with Thunderbolt devices during sleep. But I'm not confident with that being the solution. Turn the power off to the Crucial M4 when the problem occurs and then re-power it in the hope that it causes some sort of refresh of the connection to happen. Again, not sure that's a good solution either as I don't want to be powering down my SSD every time I bring the iMac out of sleep!!!
    So I too am open to ideas and opinions on what might be causing these wake-from-sleep problems arising when Mac OS is booted from an external thunderbolt drive.

  • Problems after waking up

    Why does my MacBook Air (OS X) have trouble after waking up? Not every time, but say 3/10 times, after I wake it up from a short nap, it'll either fail to recognize my wireless network or won't come back on at all (unresponsive to all keys, requiring me to hold the power button for reset). I've noticed the likelihood of such an instance increases when I am using multiple displays via the thunderbolt to HDMI connection. Any thoughts?

    This Mac Pro is less than one week old so I shouldn't have tp reset the PRAM etc but I can give it a try.
    By the way, here is the screenshot taken by my digital camera:
    http://picasaweb.google.com/pse.no.spam/MacProDesktop/photo?authkey%3dJhw9Na8R6G axLfG9zUe92EA1AIs%234990364461229080594
    It ONLY happens when it my Mac Pro goes to sleep for the first time. All subsequent sleeps are okay. I need to Shut Down my Mac Pro and boot it up again to reproduce the problem which will happen after the first sleep.
    I can give rid of the lines simply by manually putting the Mac Pro back to sleep for a few seconds and waking it up.
    Also it would appear that communications to the monitor gets reset after 10 seconds or so. (I see the DVI Icon appear on my Monitor). When that happens the lines disappear.
    I also noticed that the lines will go away if I simply turn off my Dell 2407 WFP 24 inch widescreen LCD Monitor and Turn it back on. But I am not sure whether that is really fixing the problem or whether it would be fixed in any event simply by the passage of time as noted above.
    Do you think it is my Monitor?
    (i am using 1920x1200 resolution on a 24 inch Dell Widescreen Monitor)
    Rob

Maybe you are looking for