iMac won't return from snooze...

Question

Level 1

25 points

iMac won't return from snooze...

So now I have 10.8.2, and Yay! Way to go Apple, You've fixed Parental Controls, for the most part anyway...

However, now you've bust something else! Since installing it, I've had to hard reset my iMac 8 or so times over the past 4 days. Totally unacceptable.

So, the symptoms are, iMac is at the Login screen (I run multiple user accounts, 1 or more will be logged in), leave it a few hours, come back and try to wake up the iMac (hit keyboard, shake mouse etc...). The screen either remains black, or it has been known to wake up and go grey.

I can hear the hard drive being accessed. Sometimes I will even be streaming music from iTunes to remote Airport Express speakers, the music will continue, the remote application will be responsive (reasonably) just the darn iMac will not wake up to be used and has had to be power cycled, something I Hate doing with a passion, especially when I can hear the drive being accessed.

Looking in the Console, prior to the shutdown I always have entries like this:

22/09/2012 17:03:44.506 mdworker[3038]: Unable to talk to lsboxd

22/09/2012 17:03:44.511 mdworker[3040]: Unable to talk to lsboxd

22/09/2012 17:03:44.522 mdworker[3037]: Unable to talk to lsboxd

22/09/2012 17:03:44.531 mdworker[3041]: Unable to talk to lsboxd

22/09/2012 17:03:44.531 mdworker[3039]: Unable to talk to lsboxd

22/09/2012 17:03:44.628 sandboxd[3044]: ([3038]) mdworker(3038) deny mach-lookup com.apple.ls.boxd

22/09/2012 17:03:44.633 sandboxd[3044]: ([3040]) mdworker(3040) deny mach-lookup com.apple.ls.boxd

22/09/2012 17:03:44.638 sandboxd[3044]: ([3037]) mdworker(3037) deny mach-lookup com.apple.ls.boxd

22/09/2012 17:03:44.643 sandboxd[3044]: ([3039]) mdworker(3039) deny mach-lookup com.apple.ls.boxd

22/09/2012 17:03:44.649 sandboxd[3044]: ([3041]) mdworker(3041) deny mach-lookup com.apple.ls.boxd

22/09/2012 17:03:45.000 kernel[0]: Sandbox: sandboxd(3044) deny mach-lookup com.apple.coresymbolicationd

22/09/2012 17:05:54.679 mdworker[3059]: Unable to talk to lsboxd

22/09/2012 17:05:54.679 mdworker[3058]: Unable to talk to lsboxd

22/09/2012 17:05:54.759 sandboxd[3060]: ([3059]) mdworker(3059) deny mach-lookup com.apple.ls.boxd

22/09/2012 17:05:54.764 sandboxd[3060]: ([3058]) mdworker(3058) deny mach-lookup com.apple.ls.boxd

22/09/2012 17:05:55.000 kernel[0]: Sandbox: sandboxd(3060) deny mach-lookup com.apple.coresymbolicationd

What is this lsboxd and is it related to this issue?

I've repaired permissions - nothing was in need of repair.

I've turned off iTunes WiFi sync as it was causing endless problems on 10.6 iTunes, I don't think it's related but at least I know it's not that causing it!

I've read issues where CPU usage has gone up to high levels with this "Unable to talk to lsboxd" in the Console, but haven't found anything actually informative that could fix the problem. It MAY be that I have hit this same issue - I could hear the disk moving... I couldn't get any response, it's possibly something chewing up the CPU in a really bad way...

I am despairing at Apple recently, their QA is appalling. It's take to 10.8.2 to finally get the Parental stuff sorted out (kinda), but hey look, here's Facebook integration.. yeah, let's integrate more "features" and not actually get the bugs ironed out....

iMac, OS X Mountain Lion, 27" i5

Posted on Sep 22, 2012 12:35 PM

Reply

Answer 1

Sep 22, 2012 5:06 PM in response to Jemster

I am experiencing this same issue. I have been able to narrow my issue down to peripheral's plugged in via USB (USB mouse and USB keyboard). If I use the apple mouse and keyboard and unplug the USB keyboard and mouse I am able to wake up my iMac.

This is a VERY NASTY bug!

I had no issues with these peripheral's prior to the 10.8.2 update.

Console logs:

9/22/12 4:58:59.000 PM kernel[0]: Sandbox: sandboxd(610) deny mach-lookup com.apple.coresymbolicationd

9/22/12 4:58:59.142 PM sandboxd[610]: ([608]) mdworker(608) deny mach-lookup com.apple.ls.boxd

9/22/12 4:58:59.146 PM sandboxd[610]: ([609]) mdworker(609) deny mach-lookup com.apple.ls.boxd

9/22/12 4:59:31.000 PM kernel[0]: No interval found for . Using 8000000

9/22/12 4:59:39.000 PM kernel[0]: No interval found for . Using 8000000

9/22/12 4:59:54.000 PM kernel[0]: USB-PS/2 Optical Mouse::terminate(kIOServiceSynchronous) timeout

9/22/12 4:59:54.000 PM kernel[0]: USBF: 5206.373 [0xffffff80564b0800] The IOUSBFamily is having trouble enumerating a USB device that has been plugged in. It will keep retrying. (Port 4 of Hub at 0xfa130000)

9/22/12 4:59:57.000 PM kernel[0]: USBF: 5208.629 [0xffffff80564b0800] The IOUSBFamily was not able to enumerate a device.

9/22/12 4:59:57.000 PM kernel[0]: USBF: 5209. 36 USB Device USB-PS/2 Optical Mouse is violating Section 9.3.5 of the USB Specification -- Error in GetConfigDescriptor( wLength = 4)

9/22/12 4:59:57.000 PM kernel[0]: No interval found for . Using 8000000

9/22/12 5:00:25.000 PM kernel[0]: No interval found for . Using 8000000

9/22/12 5:00:40.000 PM kernel[0]: USB-PS/2 Optical Mouse::terminate(kIOServiceSynchronous) timeout

9/22/12 5:01:31.815 PM mdworker[619]: Unable to talk to lsboxd

9/22/12 5:01:31.819 PM mdworker[621]: Unable to talk to lsboxd

9/22/12 5:01:31.825 PM mdworker[620]: Unable to talk to lsboxd

9/22/12 5:01:31.871 PM sandboxd[623]: ([619]) mdworker(619) deny mach-lookup com.apple.ls.boxd

9/22/12 5:01:31.875 PM sandboxd[623]: ([621]) mdworker(621) deny mach-lookup com.apple.ls.boxd

9/22/12 5:01:31.879 PM sandboxd[623]: ([620]) mdworker(620) deny mach-lookup com.apple.ls.boxd

9/22/12 5:01:32.000 PM kernel[0]: Sandbox: sandboxd(623) deny mach-lookup com.apple.coresymbolicationd

Reply

Answer 2

Jemster Author

Level 1

25 points

Sep 23, 2012 4:01 AM in response to Bullishpip

I'm not sure it's the same issue - I see some of those USBF failure messages, but interestingly only after the reboot, not beforehand.

However, I have definitely seen the issue where my USB keyboard has disappeared after wakeup - the bluetooth mouse clicks woke the machine up, but when I've gone to type in a password, nothing. Unplugging and re-plugging the USB keyboard has worked to bring it back to life. In these scenarios, the mouse has been responsive and I've been able to click around the screen to bring up the login box.

Does that sound similar to what you're getting? Either way, hard reboots are not good.

The problem I'm now experiencing is that the screen is either totally black, or only gets as far as waking up and going grey... no mouse cursor, etc...

I'm currently logging the top 5 lines of the top command to a text file every 10 seconds, of course, since writing that, the machine has woken up each time, but hopefully when it does require a hard reset, I'll have a log containing the processes that are consuming all the CPU (if that's what's happening...)

Reply

Answer 3

Sep 23, 2012 9:01 AM in response to Jemster

I have the same problem on my Macbook Pro 17" (early 2009) since upgrading to 10.8.2. It goes so sleep but when I come back later I can hear the fan running and it won't react to anything except a hard reset.

Apparently the wake up call came from the 'Wake for network access' option (which I have disabled now), but after waking up, it is incapable of going back to sleep as mdworker kicks in every 4 mn and complains about not being able to talk to lsboxd.

23.09.12 11:17:26.000 kernel[0]: sleep

23.09.12 13:05:18.000 kernel[0]: Wake reason: RTC (Alarm)

23.09.12 13:05:18.000 kernel[0]: RTC: Maintenance 2012/9/23 11:05:17, sleep 2012/9/23 09:17:26

...

23.09.12 17:35:29.140 mdworker[1293]: Unable to talk to lsboxd

23.09.12 17:35:29.000 kernel[0]: Sandbox: sandboxd(1295) deny mach-lookup com.apple.coresymbolicationd

23.09.12 17:35:29.785 mdworker[1294]: Unable to talk to lsboxd

23.09.12 17:35:29.943 sandboxd[1295]: ([1293]) mdworker(1293) deny mach-lookup com.apple.ls.boxd

23.09.12 17:35:29.954 sandboxd[1295]: ([1294]) mdworker(1294) deny mach-lookup com.apple.ls.boxd

23.09.12 17:39:30.712 mdworker[1299]: Unable to talk to lsboxd

23.09.12 17:39:30.760 mdworker[1298]: Unable to talk to lsboxd

23.09.12 17:39:31.095 sandboxd[1300]: ([1299]) mdworker(1299) deny mach-lookup com.apple.ls.boxd

23.09.12 17:39:31.124 sandboxd[1300]: ([1298]) mdworker(1298) deny mach-lookup com.apple.ls.boxd

23.09.12 17:39:31.000 kernel[0]: Sandbox: sandboxd(1300) deny mach-lookup com.apple.coresymbolicationd

Quite annyoing...

Reply

Answer 4

Jemster Author

Level 1

25 points

Sep 23, 2012 9:22 AM in response to guy_moreillon

Lsboxd does seem to be a common part of these problems..

Ironic that its part of Sandboxing, a technology meant to make our machines more stable. Strangely I don't think my machine has ever been more stable than it was on Snow Leopard and that didn't have these darn security 'features'

:)

Reply

Answer 5

Sep 23, 2012 9:50 AM in response to Jemster

I am also having a problem with my iMac waking up. If I click the mouse or any key it takes 10 to 15 seconds to wake up, well most of the time, but if I click the power button it wakes up immediately. If you have not tried tapping the power button it might be woth a try. Or maybe you will find one more thing that does not work.

Dan

Reply

Answer 6

Sep 23, 2012 9:52 AM in response to shipwright

Tried it of course, pressing the power button does nothing... well unless I press it for more than 5 seconds of course, but then, that's a hard reset :-)

Reply

Answer 7

Jemster Author

Level 1

25 points

Sep 23, 2012 12:56 PM in response to Jemster

Something I've just noticed...

When I get the grey screen (rather than the black one) it has got a mouse cursor, just no way of doing anything. What's interesting is that this is happening upon returning to the Login Window, i.e. not sleep related.

That is, I click on my account user name (top right), then Login Window... the screen rotates, goes grey... but the wallpaper with all the user icons never appears, greyness just stays. I thought this was sleep related because I never noticed and, when I returned to the iMac a few hours later, waking it up it was just grey.

Second symptom still happens though (the black screen, no response after sleep).

I've just uninstalled Sizzling Keys as I was using the handy Cmd-Opt-L keystroke to get to the login window. Don't know if that'll have any effect though but it's worth a shot. I've also enabled remote SSH so when it next happens, perhaps I'll be able to SSH in from the iPad and see what's going on...

Reply

Answer 8

Sep 24, 2012 6:13 AM in response to Jemster

I've got the same issues since 10.8.2 on 2 machines (Mac Pro 2008 and MBA 2011).

Wake from sleep often fails with a black screen and the sandbox errors. On my Mac Pro, the throbbing white light suggests it's asleep, but the fans are still going.

I've also had issues with the mouse not working at random times. Switching USB ports will get it working again.

Spotlight is re-indexing a lot, but I think that is due to the forced restarts I do to get the machines working again.

All in all a very sorry experience.

Reply

Answer 9

Sep 24, 2012 6:34 AM in response to Jemster

I'm seeing the same issue. My MacBook Pro goes to sleep and then appears to wake on its own but I cannot interact with it. Screen is black, none of the keys are working and clicking on the track pad does nothing. Have to do a hard power off restart to get it back. I've noticed the same messages described in original post and other replies in the system log. I don't normally see this during the day (short periods of sleep) but it is happening every night. Started just after installing 10.8.2.

Yesterday I tried a reinstall of Mountain Lion to see if that helped, but the hang occurred once during the day following the reinstall and then again overnight.

One thing I've noticed is the indicator light that pluses to show the machine is asleep is off when the problem occurs. I'm assuming that something woke the machine from sleep and then the problem happens. I don't know if some device connected through USB or a network event caused the laptop to wake.

Hope someone finds the problem soon so we can work around this.

Reply

Answer 10

Sep 24, 2012 6:39 AM in response to Rob Wheatley

I've got what looks like the same problem. Mac Pro 2008 on my LAN with a Macbook Pro 2012 Retina. Both running Mountain Lion. The Macbook is fine. The Mac Pro is scheduled to go to sleep at 11:30PM. Every morning since I installed Mountain Lion I've had to do a cold reboot to get the dispay back.

I can ssh to the Mac Pro from the Macbook. In the Finder on the Macbook I can connect to the directories but not Share Screen. I hear the DVD's clicking periodically in the Mac Pro.

The /var/log/system.log file shows the mdworker errors "unable to talk to lsboxd" and "deny mach-lookup com.apple.ls.boxd".

I see in system.log where the Mac Pro tries to go to sleep and then appears to wake up:

Sep 23 23:38:42 mac mdworker[2474]: Unable to talk to lsboxd

Sep 23 23:38:42 mac sandboxd[2476] ([2475]): mdworker(2475) deny mach-lookup com.apple.ls.boxd

Sep 23 23:38:42 mac sandboxd[2476] ([2474]): mdworker(2474) deny mach-lookup com.apple.ls.boxd

Sep 23 23:38:42 mac kernel[0]: Sandbox: sandboxd(2476) deny mach-lookup com.apple.coresymbolicationd

Sep 23 23:39:51 mac com.apple.time[11]: Next maintenance wake [Backup Interval]: <date: 0x7f9583100160> Mon Sep 24 00:15:32 2012 EDT (approx)

Sep 23 23:39:51 mac com.apple.time[11]: Requesting maintenance wake [Backup Interval]: <date: 0x7f9583100160> Mon Sep 24 00:15:32 2012 EDT (approx)

Sep 23 23:39:51 mac kernel[0]: hibernate image path: /var/vm/sleepimage

Sep 23 23:39:51 mac kernel[0]: sizeof(IOHibernateImageHeader) == 512

Sep 23 23:39:51 mac kernel[0]: kern_open_file_for_direct_io(0) took 0 ms

Sep 23 23:39:51 mac kernel[0]: Opened file /var/vm/sleepimage, size 12884901888, partition base 0x0, maxio 400000 ssd 1

Sep 23 23:39:51 mac kernel[0]: hibernate image major 1, minor 0, blocksize 512, pollers 5

Sep 23 23:39:51 mac kernel[0]: hibernate_alloc_pages flags 00000000, gobbling 0 pages

Sep 23 23:39:51 mac kernel[0]: hibernate_setup(0) took 0 ms

Sep 23 23:39:55 mac WindowServer[146]: post_notification : Time out waiting for reply from "Google Chrome Helper" for notification type 102 (CID 0x18203, PID 578)

Sep 23 23:39:55 mac WindowServer[146]: Created shield window 0xa4 for display 0x28da1900

Sep 23 23:39:55 mac WindowServer[146]: Created shield window 0xa5 for display 0x2a6823c1

Sep 23 23:39:55 mac WindowServer[146]: device_generate_desktop_screenshot: authw 0x0(0), shield 0x0(0)

Sep 23 23:39:55 mac WindowServer[146]: device_generate_lock_screen_screenshot: authw 0x0(0), shield 0x0(0)

Sep 23 23:39:55 mac WindowServer[146]: device_generate_desktop_screenshot: authw 0x0(0), shield 0x0(0)

Sep 23 23:39:56 mac kernel[0]: Intel82574L::setLinkStatus - not active 1face001, 0

Sep 23 23:39:56 mac kernel[0]: Intel82574L::setLinkStatus - not active 1face000, 0

Sep 23 23:39:57 mac configd[17]: network changed: v4(en0:192.168.1.149, en1-:139.99.113.149) DNS* Proxy SMB

Sep 23 23:39:57 mac configd[17]: network changed: v4(en0-:192.168.1.149) DNS- Proxy- SMB-

Sep 23 23:40:10 mac kernel[0]: hibernate_page_list_setall start 0xffffff8177e27000, 0xffffff8177e87000

Sep 23 23:40:10 mac kernel[0]: hibernate_page_list_setall time: 506 ms

Sep 23 23:40:10 mac kernel[0]: pages 1181319, wire 229165, act 389376, inact 1043, cleaned 0 spec 301, zf 6776, throt 0, could discard act 119240 inact 222546 purgeable 23659 spec 189213 cleaned 0

Sep 23 23:40:10 mac kernel[0]: hibernate_page_list_setall found pageCount 626661

Sep 23 23:40:10 mac kernel[0]: IOHibernatePollerOpen, ml_get_interrupts_enabled 0

Sep 23 23:40:10 mac kernel[0]: IOHibernatePollerOpen(0)

Sep 23 23:40:10 mac kernel[0]: encryptStart 13320

Sep 23 23:40:10 mac kernel[0]: writing 624945 pages

Sep 23 23:40:10 mac kernel[0]: encryptEnd 8410800

Sep 23 23:40:10 mac kernel[0]: image1Size 0x131e3e00, encryptStart1 0x13320, End1 0x8410800

Sep 23 23:40:10 mac kernel[0]: encryptStart 131e3e00

Sep 23 23:40:10 mac kernel[0]: encryptEnd 3cd9f600

Sep 23 23:40:10 mac kernel[0]: PMStats: Hibernate write took 10762 ms

Sep 23 23:40:10 mac kernel[0]: all time: 10762 ms, comp bytes: 2560098304 time: 2569 ms 950 Mb/s, crypt bytes: 838569184 time: 4660 ms 171 Mb/s,

Sep 23 23:40:10 mac kernel[0]: image 1020917248, uncompressed 2560098304 (625024), compressed 1009642928 (39%), sum1 9648a0ab, sum2 36599fee

Sep 23 23:40:10 mac kernel[0]: wired_pages_encrypted 83802, wired_pages_clear 143726, dirty_pages_encrypted 397496

Sep 23 23:40:10 mac kernel[0]: hibernate_write_image done(0)

Sep 23 23:40:10 mac kernel[0]: sleep

Sep 23 23:40:10 mac kernel[0]: Wake reason: RTC (Alarm)

Sep 23 23:40:10 mac kernel[0]: RTC: Maintenance 2012/9/24 05:39:51, sleep 2012/9/24 03:40:20

Sep 23 23:40:10 mac mDNSResponderHelper[2484]: do_mDNSInterfaceAdvtIoctl: ioctl call SIOCGIFINFO_IN6 failed - error (22) Invalid argument

Sep 24 01:39:52 mac kernel[0]: Intel82574L::setLinkStatus - not active 1face001, 0

Sep 24 01:39:52 mac kernel[0]: Intel82574L::setLinkStatus - not active 1face000, 0

Sep 24 01:39:52 mac kernel[0]: Previous Sleep Cause: 5

Reply

Answer 11

BFDill

Level 1

4 points

Sep 24, 2012 5:43 PM in response to Tarheelinwalden

I'm having the same problem :-(

9/24/12 8:26:25.710 PM mdworker[1966]: Unable to talk to lsboxd

9/24/12 8:26:25.715 PM mdworker[1967]: Unable to talk to lsboxd

9/24/12 8:26:25.797 PM sandboxd[1968]: ([1966]) mdworker(1966) deny mach-lookup com.apple.ls.boxd

9/24/12 8:26:25.803 PM sandboxd[1968]: ([1967]) mdworker(1967) deny mach-lookup com.apple.ls.boxd

9/24/12 8:26:25.000 PM kernel[0]: Sandbox: sandboxd(1968) deny mach-lookup com.apple.coresymbolicationd

9/24/12 8:26:48.000 PM bootlog[0]: BOOT_TIME 1348532808 0

Reply

Answer 12

Sep 24, 2012 6:15 PM in response to Jemster

After looking farther into this and getting some help from Linc Davis in another thread, this problem may be realted a maintance wake command that is being processed. My syslog shows:

Sep 24 14:37:14 ***machine name*** kernel[0]: Wake reason: OHC2

Sep 24 14:37:14 ***machine name*** kernel[0]: AirPort_Brcm43xx::powerChange: System Wake - Full Wake/ Dark Wake / Maintenance wake

Sep 24 14:37:14 ***machine name*** kernel[0]: The USB device BRCM2046 Hub (Port 1 of Hub at 0x6000000) may have caused a wake by issuing a remote wakeup (2)

Sep 24 14:37:14 ***machine name*** kernel[0]: The USB device Bluetooth USB Host Controller (Port 1 of Hub at 0x6100000) may have caused a wake by issuing a remote wakeup (3)

Sep 24 14:37:21 ***machine name***.local com.apple.backupd-helper[1705]: Not starting Time Machine backup after wake - less than 60 minutes since last backup completed.

Sep 24 16:04:40 ***machine name***.local com.apple.time[11]: Next maintenance wake [Backup Interval]: <date: 0x7f88b9e18480> Mon Sep 24 16:15:51 2012 EDT (approx)

Sep 24 16:04:40 ***machine name***.local com.apple.time[11]: Requesting maintenance wake [Backup Interval]: <date: 0x7f88b9e18480> Mon Sep 24 16:15:51 2012 EDT (approx)

Sep 24 17:52:42 ***machine name*** kernel[0]: Wake reason: RTC (Alarm)

Sep 24 17:52:42 ***machine name*** kernel[0]: AirPort_Brcm43xx::powerChange: System Wake - Full Wake/ Dark Wake / Maintenance wake

I found these entries by typing "wake" into the text search box on the console window.

I think I'm seeing a problem not with waking from sleep, but where a maintenance activity or some device has triggered a maintenance wake. Once the machine wakes, it doesn't go back to sleep normally and that's the problem.

Anyone else seeing the wake messages?

Reply

Answer 13

Sep 25, 2012 5:13 AM in response to Jemster

May have found a work around for this problem. Last night I turned off the "Wake for network access" option on the Engry Saver panel. This morning my MacBook woke normally. First time since I installed 10.8.2. Don't know what caused the problem, but turning off the wake-for-network-access seems to avoid the hang.

Reply

Answer 14

Sep 25, 2012 8:31 AM in response to Chet Rindfuss

Thanks for posting a workaround Chet!

Reply

Answer 15

oneivan

Level 1

0 points

Sep 28, 2012 1:28 AM in response to Jemster

I've same problem - my MBP2012 cant wakeup today.

Only hard restart with long press power btn help me. In log I see three message repeatedly:

28.09.12 8:19:04,903 sandboxd[12212]: ([12211]) mdworker(12211) deny mach-lookup com.apple.ls.boxd

28.09.12 8:19:05,000 kernel[0]: Sandbox: sandboxd(12212) deny mach-lookup com.apple.coresymbolicationd

28.09.12 8:21:05,886 mdworker[12214]: Unable to talk to lsboxd

and again again ..

well , I follow the advise from Chet Rindfuss (thanx!) , but I've note that messages still arrive continuously (per 1-2mins).

Ivan S.

Reply