found_drama

While I wouldn’t say that I spoke to soon (re: “Poor Malkovich“), perhaps the situation bears some additional prudence to fully explore the options for remedy and repair.  After all, it should not be necessary to replace that iMac G5.  So let’s put all the cards out there.  Firstly — what the hell is going on?

Malkovich^[1] has been shutting down at random intervals over the past week or so.  It’s a troubling trend because (a) there is no warning when the shutdown is about to happen and (b) it then takes several minutes before the iMac will turn on again (i.e., respond to someone pressing the power button) during which time (c) there is a whole lot of anxiety about whether it will turn on ever again^[2].  Thus far, no pattern has emerged.  Some days pass with no shutdowns whatsoever, others have one or two; we’ve been lucky in as much as no single 24-hour period has been marked by greater than two of these random shutdowns^[3].  So we’ve been digging through system logs and trying to cross-reference the symptoms with those described in forum posts and the Apple support site’s knowledge base articles.  From this research, three theories^[4] have emerged:

1. Over-heating; and/or
2. a failing power supply; and/or
3. a failing logic board.

Over-heating. If you’ve worked with an iMac before, you can see how this might easily be the case.  All the components are crammed into a thin, tight chassis that has little in the way of ventilation and cooling systems.  Over-heating seems to be a pretty common malady for iMacs (see also: here, here, and here).  From what I’ve found so far, unless you want to take drastic measures, there isn’t much you can do about the heating problem except periodically clean the dust out, keep the vents clear, and try to keep the room A/C-ified if you can.

If the problem turns out to be over-heating, I imagine I could try to just suck it up for a year or so.  But aside from my suspicions, there isn’t much to support the over-heating theory.  According to the discussion threads on the Apple site, if the shutdowns were due to over-heating then I should see something like this in system.log:

localhost kernel[0]: AppleSMU -- shutdown cause = -110

Instead, there are no lines matching “thermal” or “temperature” or “heat” and the only line matching AppleSMU or shutdown is:

localhost kernel[0]: AppleSMU -- shutdown cause = 1

…and seriously, WTF is that?

Failing power supply. I suspect that this is our most likely culprit, if only because Malkovich is already on its third power supply^[5].  In my research to date, I have been unable to identify specific steps to help diagnose a failing power supply.  As a Mac “civilian”, I’m left to some guess work.

That being said, I turn (naïvely or otherwise) to Apple’s support site to peruse the knowledge base articles looking for clues.  The most applicable kb article I’ve been able to find is this one:  iMac G5: Troubleshooting when your computer won’t turn on

If you care about semantics (like I do) then you’ve instantly picked up on the same quirk that I have:  my issue is not that the iMac has trouble turning on but that it randomly turns off.  Just the same, I did get a little value out of the article, namely (a) that I’m resetting the SMU every time that I unplug the iMac and that this should offer some relief from some of the symptoms and/but also (b) that I can in fact pull the cover off and do some diagnostic work, watching the flickering of some LEDs to get a sense of whether the issue lies with the power supply or (gasp) the logic board.

Failing logic board. I’m sad to say that with this scenario my optimism is reflected in the fact that I’m only throwing out the faulty logic board theory as a worst case scenario.  Based on the Apple kb article (re: reading LEDs and validating power supply vs. logic board issues; vide supra), it’s beginning to sound like the issue is that this third power supply is on its way out.  If the issue were with the logic board, the situation should be more dire.  Granted, I have yet to pull the cover off and examine the flicking of those little LEDs.  But at this stage, I think it’s still safe to make some guesses.

Not that I’m saying that a faulty logic board wouldn’t explain these random shutdowns or that they don’t explain them — I’m merely saying that there is not a stronger case to be made for the logic board explanation than the power supply explanation.  The system.log file really doesn’t show any messages that indicate a problem. What I’ve concluded from this (so far) is that whatever the issue is, it’s occurring in the hardware layer somewhere and that when it fails, it fails suddenly and totally and gives the software no opportunity to leave any trace evidence. Perhaps that sudden and total failure is happening in the labyrinthine circuitry of the logic board; or perhaps the power supply simply chokes on its own volts.

Again, as a Mac “civilian”, I’m left only with guesswork for now.

So what’s next? I’d really like to get to the bottom of this if I can. While I’d love a bright new shiny toy, I’d also love to solve this problem and stick to my original plans. I’m going to pop the hood and clean out Malkovich as a starter; it’s probably due to have the dust blown out anyway. That said, as I’ve already expressed my doubts about the over-heating theory, I don’t expect that this will get us terribly far.

That leaves the failing power supply vs. logic board theories to duke it out. I don’t expect that the diagnostic LEDs are really going to tell me much. I keep looking at “Step 12″ in that Apple kb article and shaking my head: the path to “logic board failure” is predicated on a computer that gets power but doesn’t turn on. Again, “turning on” isn’t my problem — randomly turning itself off is my problem. If it is in fact a faulty power supply…

Well, I admit that I’ll be disappointed. Even the PCs I had before this didn’t burn through power supplies this quickly. (This would make 4 power supplies in 4 years!)

Comparatively speaking, replacing the power supply is a cheap fix ($110 vs. $860 for the logic board^[6]) that could buy another year or two of useful life for this machine.  But then again…  ”Another year or two”?  Sounds like we’re expecting that power supply to fail after another 10-14 months just like its predecessors.  O! the conundrum…  The questions then become:  are we really being that rough on these power supplies?  (And if so, what’s the baseline level of activity or “abuse” that’s reasonable to expect of them?)  And is there anyone out there that has had a nice “good long run” with their iMac?  Or any other theories?

UPDATE: Since writing this there has not been another random shutdown.  So that’s good, though not exactly encouraging or mind-changing.  I popped the cover on Malkovich and went to town on the dust with a Giotto’s Rocket Blaster; the LED diagnostics were (predictably) inconclusive which lends evidence to the bogus power supply theory, if you ask me.  But at least it’s clean in there now.  —F_D (5/2/2009)

1. Malkovich is the hostname for our 20″ iMac (2.0 GHz G5 with ambient light sensor). [↩]
2. You can imagine how frustrating this is, especially when a copy of Barry Lyndon is trapped inside with 10 minutes left to go in the film. [↩]
3. This is not particularly comforting; poor ol’ BenNevis (my previous MacBook Pro) started off the same with its random shutdowns (a.k.a., b0rk!) — one or two at a time, one or two per day.  But over the course of a month or so that grew to approximately one per hour until it seemingly spiked at one per CPU clock cycle and stayed there. [↩]
4. A fourth theory developed when I saw this in system.log:

   Malkovich [0x0-0xf00f].com.apple.iTunes[121]: 2009-04-27 19:42:14.644 osascript[255:613] *** _NSAutoreleaseNoPool(): Object 0x130d30 of class NSCFData autoreleased with no pool in place - just leaking

   …but wouldn’t a memory leak just cause the system to get sluggish? and/or maybe just lock up?  I haven’t found any literature to support my theory that the memory leak is causing the shutdowns, so I’ve tossed it.  For now. [↩]

5. The first failed in April 2006 and was replaced by the good folks at Ormsby’s; that power supply then failed on July 4th 2008, two months after the AppleCare ran out (and just days after H. was born), and was replaced by the kindly folks at Small Dog Electronics.  This is not even to mention the hard drive issues we had in 2005. [↩]
6. For $860 you’re halfway to a 24″ iMac, or else maxing out a Mac mini. [↩]

some say “slow moving”
but instead ’tis action packed.
still, please be patient.

Seriously.  You need no additional evidence that Kubrick was a bat-shit insane genius than this film.

Anyone that says that describes it as “slow moving” is expecting entirely too many explosions for something set in the 18th century.  Or they’re not paying attention.  Every scene is dense with dialogue, imagery, narration, and plot-advancing actions.  It’s complex (no fooling there) but not so complex that it becomes difficult to follow.

That said, you do need to be paying attention.  And you do need to exhibit some patience to let all of the pieces come together.

Plus, the film is a technical masterpiece — even before you stop to consider the great pains to which Kubrick went to achieve all of those candle-lit shots without the aid of electric light.

• Cutting The Grocery Bill–How?
  at Al Dente
  (tagged: food groceries budget money essay todo )
• Gantter Does Project Management in Your Browser
  at LifeHacker
  (tagged: lifehacks productivity projectmanagement GTD projects )
• Polar Rose
  via LifeHacker: "Naming is sharing!" — face recognition for Flickr? on the web?
  (tagged: software tools photography flickr social todo )
• Ajax Experience Talks: Resig, Slocum, and Heilmann
  at Ajaxian
  (tagged: javascript webdev video css todo work )
• Tech Test Drive: Nothing small about Mac Mini’s media-center capabilities
  at TwinCities.com (via Apple News)
  (tagged: MacMini Apple hardware todo )
• 64 Things Every Geek Should Know
  at LaptopLogic.com — a couple of fun-looking projects on here.
  (tagged: hack todo )
• Confluence and JIRA – 5 users for $5
  at Atlassian Developer Blog — no catch!
  (tagged: Confluence JIRA Atlassian via:fogus )

Recently it became apparent that our trusty iMac G5 (a.k.a., “Malkovich”) may not be long in its continued operation.  The iMac seems to have shut itself off randomly on at least two occasions over the past week or so — one minute it’s chugging along, playing music and/or exporting photos from Aperture and the next minute it’s just… off.

Malkovich is coming up on its four year anniversary and has probably logged well over 25,000 hours of discontinuous uptime^[1] and it is probably reasonable to expect that it’s nearing the end of its useful life cycle.  I was hoping to get 4-5 years of total useful life out of this iMac during which time it would serve as the main computer in the home.  So we’re not too far off our target if we’re working from that estimate.  But I was really hoping to get through to next year before this came up.  These random shutdowns cast a pall on Malkovich though and I have more than a few doubts that we’ll make it to ’10.  As such, we’re trying to figure out what computer will take its place.

Read the rest of this entry »

1. Though it’s probably more like 7,000 hours of “active use” — i.e., playing music from iTunes, novel-writing, or processing pictures in iPhoto or Aperture. [↩]

A video interview with my Granddad, an Air Force F-4 pilot during the Vietnam War, from Timeless Voices of Aviation:

Link direct to the video

Goodreads calls its 5★ rating “Amazing”.  I don’t know if Midnight in the Garden of Good and Evil fits that specific superlative, but I would agree that it is approximately one of the most perfectly constructed and tightly written narratives I have encountered. First, a note about the book:

My feelings toward “creative non-fiction” are a bit on the love/hate end of things. I have nothing specifically against creative non-fiction but my inner would-be-novelist thinks that something about it seems like cheating. After all, you didn’t invent the story, even if you went to great pains to bring it to literary life. On the other hand, a good story deserves to be told — and as long as you’re talented enough to do it…

Well, John Berendt was certainly talented enough to do it. As I mentioned above, the narrative is almost perfectly paced and almost perfectly structured. It is instantly engaging and strikes all the right notes to cue you in on where the story is headed without telegraphing each next move. Savannah, Georgia, provides an instantly surreal and visceral back-drop for this story. I hate to give it all away but allow me at least mention that, though Kevin Spacey and John Cusack put on great performances in the film adaptation, the movie version is scarcely better than Cliffs’ Notes for this tapestry of grandeur, intrigue, and voodoo.

P.S.— don’t you think that “Midnight in the Garden of Good and Evil” is THE BEST TITLE EVER??

A version of this review appears on Goodreads.com.

Is there really a better, more apt, more semantically appropriate expression in modern English^[1] than “trophy wife”?  Consider it:

1. There is (perhaps) a hard-won battle in leading up to the “winning” of the trophy.
2. But once you have that trophy, all that’s left is the memory of that winning…
3. …the trophy itself is dead weight on the shelf that needs surprisingly frequent polishing to keep in any kind attractive state.
4. Certainly when your friends come over and see the trophy, they’re jealous; and consequently, you’re constantly looking over your shoulder wondering which one of them is going to try and sneak off with it.
5. And let’s face it, after your big win, the talk of the town will move on to whomever wins the next trophy.  And unless you’ve retired from the game, that means you’re itching to win, too.

1. Say what you will about the term’s potentially ancient origins; say what you will about whether the wife is herself accomplished in anything at all.  We’re talking about popular cultural phenomena, here. [↩]

Allegory for
spousal secrets, marriage woes
—but more explosions.

After a two years and about 200 hours^[1] of use, my Mad Rock Flashes climbing shoes finally gave up the ghost. They wore clear through at the toes. There was no saving them. The shoes had served me well and had always been pretty comfortable^[2], so with that in mind, I was sad to see them go. But after two years and 200 hours, I’d also proven to myself that I was committed enough to this sport that it was worth it to me to get what I wanted this time around.

So I went ahead and picked up a pair of Defy rock shoes by Evolv. So far? Loving these shoes after a couple of climbing sessions.

Coming from the Mad Rocks, I’m learning how nice it can be to have a stiffer sole. There seems to be a bit more grip and support in these shoes that I never even knew I was missing. Supposedly the synthetic material does not stretch — so the way it fits in the store is the way it will fit a year from now. The synthetic material definitely breathes well.

As far as the fit of the shoe goes, it seems to be slightly narrower in the toe than the Mad Rocks were but not so narrow as to be uncomfortable. Also, the Defys seem to run a full size smaller than the comparable Mad Rock shoes. I wore an 11 Mad Rock, stepped down to a 10.5 in the Defys and then after getting onto the wall discovered that it made more sense to step down even further to a size 10.

But so far, quite comfortable and very recommended.

1. Yes, I keep track. If you’re a regular here, you probably already knew that. [↩]
2. Where by “comfortable” I mean “extremely tight like I would want them to be but not so much so that I feel like a 19th century Chinese concubine”. [↩]

My life is now complete:

Image seen in gene_gene234′s photostream on Flickr.