LockerGnomeTech news and nostalgia for today's technology professionals
Subscribe

Search

Hardware

IBM support revived a dead ThinkPad with ten power-button presses and a 30-second hold

Mike Masnick’s 2007 conference mishap preserves a recovery sequence, with a useful warning about what the account cannot diagnose.

Chris presses the power button on an open ThinkPad Z61t, its removable battery and disconnected power plug beside it.
Illustration: LockerGnome

Mike Masnick had a presentation coming up and a ThinkPad that had apparently resigned. Its lights stayed dark, the power button did nothing, and the sleeping machine was unexpectedly hot. IBM support offered a button sequence that sounded more suitable for unlocking a secret game level than preparing a conference talk.

In his September 7, 2007 account, the computer was a Lenovo ThinkPad Z61t. Removing and replacing its battery had already failed. The support agent then had him disconnect AC, remove the battery again, press the power button ten times at one-second intervals, and hold it for 30 seconds.

The machine started after Masnick reinstalled the battery and pressed power. The agent described the procedure as “static discharge,” but couldn’t provide a fuller explanation. The reported recovery and the explanation deserve different amounts of confidence. One happened in the account; the other stopped at a phrase on the phone.

This is a pleasingly human support story because Masnick actually asked why. A magic sequence had delivered the result, and the person offering it couldn’t completely explain the mechanism. The power button had become a support shortcut with its own little knowledge gap, preserved in public rather than smoothed over into certainty.

The original post is also the boundary of the evidence here. A particular laptop recovered after a particular sequence. That doesn’t prove every apparently dead ThinkPad has the same problem, and it doesn’t make a removable-battery instruction appropriate for a modern sealed machine. The easiest way to turn a helpful tip into a bad afternoon is to erase the model name.

A support note built from this episode would be most useful with spaces for the model, symptoms and result. That would let the next person distinguish a repeated pattern from a similar-looking failure. The button count is memorable; the qualifying details are what keep it usable.

There’s a difference between trying a documented recovery procedure and claiming to have repaired the underlying cause. The machine may need further attention if the same symptoms recur. A successful boot buys an opportunity to check its condition and protect the files, rather than permission to stop caring what happened.

Better support documentation could keep the working procedure while spelling out its limits. That would preserve the useful part of this story without forcing the next caller to choose between blind faith and a dead computer.

The presentation got its laptop back.

More Hardware

Every Hardware story →