May 29th, 2004 • 5:30 am
It’s always the same, isn’t it? Just when I decided that I had enjoyed a long period of stability and started bragging about it here, bam! I get hit with another system-wide freeze.
The symptoms are exactly the same as in the last freeze a week ago. I leave my computer running doing various tasks. After 15 min, as expected, the displays go to sleep (I can verify this later when walking by the machine, without touching it). And then I come back to the machine about an hour later, press a key on the keyboard to wake the displays up from sleep. They do wake up, but the system appears frozen. The mouse can still move, but I can’t click anywhere. And things that are supposed to be changing on a constant basis (menu bar clock, AirPort status) are frozen as well. Only a hard reset brings the machine back to life.
The USB ports on my secondary display are still working, so there doesn’t appear to be a relation with that other chronic failure here. And I can no longer call this a “screen saver freeze”, as I did last week, because the screen saver was not involved. It’s now set to “never” and never comes into play.
There is absolutely no clue either on the screen itself when it was frozen or in the
system.log. It’s a mystery.
Of course, with my luck, the computer was in the middle of burning a CD when this happened. And one more coaster for the garbage…
I don’t suspect Toast (the CD burning application) here because it wasn’t involved in the previous freezes of a similar nature. And I can’t really suspect my hard drives either… So we’re pretty much back to square one. It’s got to be one of three things:
- a bug in Mac OS X 10.3 itself, which was not fixed in 10.3.4
- something in my hardware setup (computer, USB devices, FireWire devices)
- one of the processes that are running in the background while I am aware from the computer
My gut feeling is that it’s either #1 or #3 — and probably #1, especially if you consider all the processes running that are part of essential pieces of the Mac OS X environment, such as iCal, Mail, etc. I don’t really separate Apple’s applications from the OS system here, because there are so many interactions between the two, as demonstrated by the fact that most Mac OS X updates include improvements for the applications and not just for the system itself.
So now I am going to start calling these freezes “display sleep” freezes. That’s pretty much the only clear factor involved. I don’t get the freezes if the displays are not asleep. Whether the freezes happen when the displays go to sleep, while the displays are asleep, or when I wake the displays from sleep is another matter. I don’t think it’s when I wake them, because the menu bar clock is usually frozen on a earlier time, not on the time it is when I wake the displays up. I’ll have to try writing down the exact time when I stop working on the computer and leave it alone, and then compare this to the time of “death” as indicated by the frozen menu bar clock. Maybe it’ll give me some clue.