-
All replies
-
Helpful answers
first
Previous
Page
12
of 39
last
Next
-
Feb 1, 2011 2:03 AM in response to Jon Israelby alls0rts,After a month of not seeing the problem it has returned for me. Though perhaps not identical to the first time I suffered the issue here are my last observations.
- Screen would not awake from mouse click, Magic Trackpad click, or keyboard.
- Keyboard caps lock does NOT light up (engage) when pressed.
- If I switch a BT device off, when I turn it back on it fails to connect.
At this point I reach around and press the ON button briefly - Unlike the first time I witnessed this the screen came on. Thus perhaps its a different issue. the BT devices still do not interact with iMac.
- Using ssh I connect to imac from MBP.
- dtruss of blued does not seem to show anything happening.
- /var/log/system.log reports for last few hours:
Feb 1 06:03:04 iMac kernel[0]: AFPSleepWakeHandler: going to sleep
Feb 1 06:46:26 iMac configd[15]: PMConnection AirPort configd plug-in com.apple.powermanagement.applicationresponse.slowresponse 13786 ms
Feb 1 06:46:26 iMac configd[15]: PMConnection IPConfiguration com.apple.powermanagement.applicationresponse.slowresponse 13825 ms
Feb 1 05:51:25 iMac configd[15]: PMConnection mDNSResponder com.apple.powermanagement.applicationresponse.timedout 25423 ms
Feb 1 05:51:25 iMac configd[15]: PMConnection IPConfiguration com.apple.powermanagement.applicationresponse.timedout 25423 ms
Feb 1 05:51:30 iMac loginwindow[1316]: handleUnlockResult, Currenttime:2/1/2011 5:51:30.998 AM - Waketime:2/1/2011 5:50:46.000 AM = Deltatime:44.
997963965
Feb 1 05:51:36 iMac KernelEventAgent[43]: tid 00000000 received event(s) VQ_DEAD (32)
Feb 1 05:51:36 iMac KernelEventAgent[43]: tid 00000000 type 'afpfs', mounted on '/Volumes/Share', from 'afp_35BfsQ35BfsQ35BfsQ35BfsQ-2.2e000006',
dead
Feb 1 05:51:36 iMac KernelEventAgent[43]: tid 00000000 found 1 filesystem(s) with problem(s)
That is NAS that switches itself off - so no big surprise there.
Feb 1 05:51:36 iMac /System/Library/CoreServices/Finder.app/Contents/MacOS/Finder[1337]: BonjourBrowser::DNSServiceQueryRecord returned -65540
Feb 1 05:51:37: --- last message repeated 5 times ---
Feb 1 05:51:36 iMac loginwindow[1316]: AFP error -1 mapped to EIO
What's that? A quick look through logs shows that hasn't happend in last few days.
# (cat system.log; bzcat system.log.{0,1,2,3,4,5,6,7}.bz2) | grep 'AFP error'
Feb 1 05:51:36 iMac loginwindow[1316]: AFP error -1 mapped to EIO
#
Feb 1 05:51:37 iMac kernel[0]: afpfs_DoReconnect: max reconnect time reached 35 > 30 (Connecting 61) /Volumes/Share Feb 1 06:03:03 iMac loginwindow[1316]: loginwindow SleepWakeCallback WILL sleep
Feb 1 06:03:04 iMac kernel[0]: AFPSleepWakeHandler: going to sleep
Feb 1 06:46:26 iMac configd[15]: PMConnection AirPort configd plug-in com.apple.powermanagement.applicationresponse.slowresponse 13786 ms
Feb 1 06:46:26 iMac configd[15]: PMConnection IPConfiguration com.apple.powermanagement.applicationresponse.slowresponse 13825 ms
Feb 1 06:46:26 iMac configd[15]: network configuration changed.
Why does this keep changing - will take a look at new Virgin Super Hub
it seems to have a short IP lease.
Feb 1 06:46:28: --- last message repeated 1 time ---
Feb 1 06:46:28 iMac mDNSResponder[16]: RegisterInterface: Frequent transitions for interface en0 (192.168.0.4)
Feb 1 06:46:29 iMac mDNSResponder[16]: DeregisterInterface: Frequent transitions for interface en0 (192.168.0.4)
Feb 1 06:46:29 iMac configd[15]: PMConnection mDNSResponder com.apple.powermanagement.applicationresponse.slowresponse 2179 ms
Feb 1 06:46:32 iMac configd[15]: network configuration changed.
Feb 1 06:46:32 iMac configd[15]: arpclienttransmit(en0) failed, Network is down (50)
Feb 1 06:46:32 iMac configd[15]: bootpsessiontransmit: bpf_write(en0) failed: Network is down (50)Feb 1 06:46:32 iMac configd[15]: DHCP en0: INIT-REBOOT transmit failed
Feb 1 06:46:32 iMac configd[15]: DHCP en0: ARP detect ROUTER failed, arpclienttransmit(en0) failed, Network is down (50)Feb 1 07:40:29 iMac com.apple.launchd[1] (com.apple.newsyslog): Throttling respawn: Will start in 4 seconds
Feb 1 07:40:34 iMac ntpd[30]: bind() fd 25, family 30, port 123, scope 4, addr fe80::c62c:3ff:fe2e:f52e, in6is_addrmulticast=0 flags=0x11 fails
: Can't assign requested addressFeb 1 07:40:34 iMac ntpd[30]: unable to create socket on en0 (29) for fe80::c62c:3ff:fe2e:f52e#123
Feb 1 07:40:42 iMac configd[15]: network configuration changed.
Feb 1 07:40:44 iMac ntpd[30]: time reset +1.346055 s
Wow! Is that right iMac lost over a whole second since the last network time, how often does that occur:
# grep 'time reset' system.log
Feb 1 02:14:01 iMac ntpd[30]: time reset +0.581813 s
Feb 1 03:08:08 iMac ntpd[30]: time reset +0.541685 s
Feb 1 04:02:27 iMac ntpd[30]: time reset +0.500688 s
Feb 1 04:56:36 iMac ntpd[30]: time reset +0.467584 s
Feb 1 05:51:02 iMac ntpd[30]: time reset +0.422586 s
Feb 1 07:40:44 iMac ntpd[30]: time reset +1.346055 s
Feb 1 07:49:51 iMac ntpd[30]: time reset +0.133139 s
Feb 1 07:40:44 iMac configd[15]: PMConnection IPConfiguration com.apple.powermanagement.applicationresponse.slowresponse 1642 ms
Feb 1 07:40:46 iMac configd[15]: PMConnection mDNSResponder com.apple.powermanagement.applicationresponse.slowresponse 3488 ms
Feb 1 07:40:50 iMac configd[15]: network configuration changed.
Feb 1 07:40:50 iMac configd[15]: arpclienttransmit(en0) failed, Network is down (50)
Feb 1 07:40:50 iMac configd[15]: bootpsessiontransmit: bpf_write(en0) failed: Network is down (50)
Feb 1 07:40:50 iMac configd[15]: DHCP en0: INIT-REBOOT transmit failedFeb 1 07:40:50 iMac configd[15]: DHCP en0: ARP detect ROUTER failed, arpclienttransmit(en0) failed, Network is down (50)
Feb 1 07:49:39 iMac loginwindow[1316]: loginwindow SleepWakeCallback will power on, Currenttime:2/1/2011 7:49:39.009 AM - Waketime:2/1/2011 7:49:
39.000 AM = Deltatime:0.009039104
Feb 1 07:49:39 iMac loginwindow[1316]: askForPasswordBuiltIn after makekey, Currenttime:2/1/2011 7:49:39.618 AM - Waketime:2/1/2011 7:49:39.000 A
M = Deltatime:0.618426085
Feb 1 07:49:44 iMac ntpd[30]: sendto(17.72.255.12) (fd=24): Network is unreachable
Feb 1 07:49:44 iMac ntpd[30]: bind() fd 25, family 30, port 123, scope 4, addr fe80::c62c:3ff:fe2e:f52e, in6is_addrmulticast=0 flags=0x11 fails
: Can't assign requested address
Feb 1 07:49:44 iMac ntpd[30]: unable to create socket on en0 (32) for fe80::c62c:3ff:fe2e:f52e#123
Feb 1 07:49:51 iMac ntpd[30]: time reset +0.133139 s
Feb 1 07:49:52 iMac configd[15]: network configuration changed.
Feb 1 07:49:52 iMac configd[15]: Sleep: Success - AC - Maintenance Sleep
Feb 1 07:49:52 iMac configd[15]: Wake: Success - AC - PWRB
Feb 1 07:49:52 iMac configd[15]: Hibernate StatisticsFeb 1 07:49:52 iMac kernel[0]: AFPSleepWakeHandler: waking up
Feb 1 07:50:09 iMac loginwindow[1316]: handleUnlockResult, Currenttime:2/1/2011 7:50:09.755 AM - Waketime:2/1/2011 7:49:39.000 AM = Deltatime:30.755416095
Thas was me waking the machine, I presume from ON/OFF button?
Feb 1 07:51:14 iMac sshd[2167]: USER_PROCESS: 2169 ttys001
Feb 1 07:53:04 iMac sudo[2191]: stacey : TTY=ttys001 ; PWD=/Users/stacey ; USER=root ; COMMAND=/bin/ksh
MBP was a little slow to awake - must wake it first next time and see
if I can connect before pressing power button. I have tried that before without success!
Feb 1 07:55:06 iMac sshd[2199]: USER_PROCESS: 2201 ttys002
Feb 1 07:55:24 iMac sudo[2206]: stacey : TTY=ttys002 ; PWD=/Users/stacey ; USER=root ; COMMAND=/bin/kshFeb 1 07:55:30 iMac com.apple.launchd[1] (com.apple.blued[512]): Exited: Terminated
At this point I uttered 'dtruss -a -n blued' but only got:
PID/THRD RELATIVE ELAPSD CPU SYSCALL(args) = return
512/0xd8a: 24097 1412 32 workq_kernreturn(0x1, 0x101004B90, 0x0) = 0 0
512/0xd8a: 24117 1665 15 kevent(0x3, 0x0, 0x0) = 1 0
512/0xd776: 48 1388 11 thread_selfid(0x7FFF704C4640, 0x0, 0xFFFFFFFF) = 55158 0
512/0xd776: 103 7 3 kevent(0x3, 0x100680DB0, 0x1) = 1 0
512/0xd776: 125 1343 7 _disablethreadsignal(0x1, 0x0, 0x0) = 0 0
^C
CALL COUNT
_disablethreadsignal 1
bsdthread_terminate 1
thread_selfid 1
workq_kernreturn 2
kevent 3
As I suspect bluetooth I start a new dtruss and kill blued, and POW - keyboard works
Feb 1 07:55:30 iMac blued[2207]: Apple Bluetooth daemon started
Feb 1 07:55:30 iMac loginwindow[1316]: askForPasswordBuiltIn after makekey
Feb 1 07:55:30 iMac loginwindow[1316]: in pamsmauthenticate(): Failed to determine Kerberos principal name.
Feb 1 07:55:31 iMac loginwindow[1316]: builtInAuthWindowDidResignKey
Feb 1 07:55:31 iMac loginwindow[1316]: handleUnlockResult
Feb 1 07:56:01 iMac loginwindow[1316]: no spins reported for this wake
Feb 1 07:56:01 iMac [0x0-0x142142].backupd-helper[2208]: Not starting Time Machine backup after wake - failed to resolve alias to backup volume
(Its that disk connected by USB cable - it keeps forgetting that too).
Feb 1 07:57:29 iMac fseventsd[46]: disk logger: failed to open output file /Volumes/iMac TM/.fseventsd/63657336dfdcb958 (No such file or directory). mount point /Volumes/iMac TM/.fseventsd
Feb 1 08:01:11 iMac com.apple.backupd-auto[2229]: Not starting scheduled Time Machine backup - time machine destination not resolvable.
Feb 1 08:02:36 iMac System Preferences[2236]: .scriptSuite warning for result type of command 'timedLoad' in suite 'SystemPreferences': the type NSNumber ('long') doesn't match the result Apple event code ('doub').
That's all for the messages....
What happened when launchd restarted blued.... you ask?
I have saved that to public dropbox http://dl.dropbox.com/u/8800767/blued.dtruss
I've then started a background dtruss:
# nohup dtruss -a -n blued >/var/tmp/blued&
Will look and see when next this happens. -
Feb 1, 2011 9:22 AM in response to Jon Israelby Alistair Haimes,This might sound obvious, but a lot of people buy Macs to keep things simple, this all sounds very complicated! -
Feb 4, 2011 12:39 PM in response to Jason Goldenby Jason Golden,Is anyone else noticing this issue when their iPad is docked? Everything works normally unless the iPad is connected -
Feb 6, 2011 6:47 AM in response to Jason Goldenby dagored,Add my wife's iMac to the list. Will follow up after doing some of the troubleshooting ideas in this thread. -
Feb 7, 2011 3:00 AM in response to dagoredby imode,Took my iMac in for repair. Turns out to be a bad backlight board. This is a frequent problem with new iMacs according to the technician. So far, after 2 days no issues with screen backlighting not turning on after sleep. -
Feb 7, 2011 6:15 AM in response to Jon Israelby HRMIII,Add me to the list as well. Brand new 21.5" imac that only occasionally wakes up from sleep properly by using the keyboard to wake it up. Using the power button to put it button to send it back to sleep and then using the power to wake it up, works most every time. I haven't even had the thing a week. Started noticing sleep problem on day 2. headed to Apple Store tomorrow. -
Feb 7, 2011 5:14 PM in response to Jon Israelby mattd313,Mine hasn't done it in a long time, a few weeks or so.
I don't know what is different, but this morning it wouldn't wake up.
Some people have said they can see the screen is on, but the backlight isn't or something- this is not the case with mine. Nothing happens at all. Almost as if it were off.
This is the first Mac I've had that has had issues.
The first issue I had was with iDVD. After hours of talking with AppleCare I decided to re-install iDVD- and it fixed it. What a pain in the butt. -
Feb 10, 2011 6:12 PM in response to Jon Israelby artist3d,I'm having the same problem too. My computer goes to sleep and I can't wake it up with my wireless keyboard or mouse. I try using the power button and I end up having to unplug the power strip from the wall! -
Feb 12, 2011 6:04 AM in response to Jon Israelby applefishtune,I got my iMAC 27" in November, and just this week the "no wake up" syndrome started. At first I though we had had a power failure, so I touched the power button. Viola!! it came on and did NOT go through all the start up screens. In other words, the power button is now acting as my wake up button. It has happened several times now, and touching the power button wakes it up every time.
I have Apple Care, so I am going to go through the help desk now, but found this post to be very interesting and to know that I am not alone.
Only other observation was the periodically the Shift light on the keyboard would not light up?? Right after that, my problem started. -
Feb 14, 2011 2:18 PM in response to applefishtuneby arick77,I had stopped forcing sleep and hadn't suffered from this for a few weeks... but back again this evening.. Mac won't wake from sleep with bluetooth keyboard or mouse!! Plugged in a USB mouse in the hope this may work... but the light did not turn on.. basically no power is going to the USB device. So, the Mac is not simply sleeping but actually appears to be turned off. However, it would not turn on simply by pressing the power button. Had to hold the button 5 secs for a reset, and then press again to turn on the Mac.. looks like the crash has been recorded in the log.. but then even the crash exception handler is failing!
----
14/02/2011 21:38:49 com.apple.launchd[1] (com.apple.netauth.sysagent[22448]) Exited with exit code: 255
14/02/2011 22:05:53 com.apple.launchd[1] * launchd[1] has started up. *
14/02/2011 22:06:20 com.apple.WindowServer[69] Mon Feb 14 22:06:20 arick77s-iMac.local WindowServer[69] <Error>: kCGErrorFailure: Set a breakpoint @ CGErrorBreakpoint() to catch errors as they are logged.
14/02/2011 22:06:30 com.apple.UserEventAgent-LoginWindow[85] ALF error: cannot find useragent 1102
14/02/2011 22:06:30 com.apple.UserEventAgent-LoginWindow[85] plugin.UserEventAgentFactory: called with typeID=FC86416D-6164-2070-726F-70735C216EC0
14/02/2011 22:06:30 com.apple.launchd.peruser.501[97] (com.apple.ReportCrash) Falling back to default Mach exception handler. Could not find: com.apple.ReportCrash.Self
14/02/2011 22:06:31 com.apple.launchd.peruser.501[97] (com.apple.Kerberos.renew.plist[120]) Exited with exit code: 1 -
Feb 15, 2011 3:17 PM in response to Jon Israelby hydve,I'm facing the same problem with my iMac I just got several weeks ago. I leave the iMac in the office overnight. When I come back in the morning, I can't wake it up with my bluetooth keyboard or mouse. But it seems like it's turned on but the screen display is black. I eventually hit the power button for several seconds to shut it off, and then turn it on again. What a pain. I'm guessing if I leave the screen saver on always, then it would work. But I don't want to waste all that energy. Has anybody figured this out? -
Feb 15, 2011 3:25 PM in response to hydveby Stampguy,Based on the number of posts, it appears to still be outstanding. I had this problem when I got my 27" iMac a couple months ago. I either scared it by swearing at it or one of the settings I made (see below) have cured it. At any rate, it has not happened to me since the last time I made these settings, so maybe it has been cured - for me. Here are my settings:
Screen Saver turns on at 30 minutes
Computer goes to sleep in 3 hours
Display sleeps at 45 minutes -
Feb 17, 2011 4:31 PM in response to Jon Israelby mattd313,Got another update, sorta. It happened again today. Instead of turning it off with the power button, I tried using the keyboard to use the computer, blindly. I couldn't get too far. I was able to turn the volume up and down and I could hear the clicky noises it makes. So it was definitely awake and functioning. Nothing on the screen, not at all. I managed to get it to sleep, and wake it back up, thinking maybe that'd kick the screen back on. Didn't work.
Had to reboot. I know this doesn't solve anything- but it shows that my computer does in fact wake up, but the screen doesn't turn on at all. This is very disappointing to have a 2 thousand dollar Mac and have a problem like this. -
Feb 18, 2011 1:16 AM in response to mattd313by Ontwerpzaamheden,Mattd313: I'm struggling with exactly the same issue here.. with a bright light I'm actually able to see what is going on in the screen.. (is a bit tricky to see, but works in a 45 degree angle).. Might be the backlit panel (or the controller for that) that is buggy. I'm loaded with work so didn't see a chance to bring it in for repair yet. -
Feb 18, 2011 2:57 AM in response to Jon Israelby brybr,i have a similar problem the computer wont reboot with out holding power button in the problem only occurs intermitterly , also loose bluetooth connection . Has anyone any suggestion the cause of this fault.