OK, I’m really mystified. I cannot, absolutely cannot, get this Leopard (10.5.2, clean install and then reimport of all the old stuff) installation on my Powerbook 1.67GHz with 1GB RAM (see, this means nobody can complain I didn’t tell them what my system was) to stay up for any length of time.
I mean, the longest I’ve managed is not quite seven days. That’s really not very long, compared to what Tiger used to manage. That’s rubbish. That’s awful. And no, I’m not running any weird extensions or APE or that lot. It’s Leopard and some applications.
And it almost always happens on waking from sleep – and then on waking automatically from sleep. Particularly in the mornings, when it is set to wake from sleep at 0655. Then I come down, hoping to find it’s been sucking up email and web feeds and opening pages and so on, and what do I find? Frozen machine – no response from the GUI; only way back is to power off, power on.
Any clues in the Console, you ask? Yes, I ask that too. Here’s what we find. The machine wakes up at 06:55:00 (we assume); the first kernel note on the console is at 06:55:07 saying “System Wake”. Jolly good. One second later:
20/02/2008 06:55:08 Mail *** Error while selecting [Google Mail]/All Mail: (null)
Then a few things about Appleshare shutting down and starting up, and then it gets the Airport up (on interface
en1). Then two seconds later:
20/02/2008 06:55:32 mDNSResponder Note: Frequent transitions for interface en1 (192.168.0.4); network traffic reduction measures in effect
20/02/2008 06:55:33 mDNSResponder Note: Frequent transitions for interface en1 (FE80:0000:0000:0000:0211:24FF:FE28:18E9); network traffic reduction measures in effect
Ur, OK, so maybe there’s something about the Airport? But here’s the next thing, which is the killer, 20 seconds later.
20/02/2008 06:55:53 fseventsd callback_client: ERROR: d2f_callback_rpc() => (ipc/send) timed out (268435460) for pid 235
20/02/2008 06:56:03 fseventsd callback_client: ERROR: d2f_callback_rpc() => (ipc/send) timed out (268435460) for pid 235
20/02/2008 06:56:03 fseventsd client: 0x80f800 : USER DROPPED EVENTS!
Which just goes on and on and on until I come along and kill the thing. And the really strange thing? I can’t find a process id 235. On restarting the machine, there’s a 234 (which is Apple’s Activity Monitor, the second process to start on my login) and then a 237 (pmtool, the command-line program that feeds Activity Monitor).
I can’t find anything from Googling that explains what
callback_client might be, nor anything that looks even slightly like this. (There’s a discussion about iDVD on Apple’s support boards, but I don’t use it.) It’s totally perplexing. Come on, can anyone enlighten me even a little?