| |||||||||||
Morse code kernel panicsMorse code kernel panicsPosted Feb 6, 2003 4:08 UTC (Thu) by egoforth (subscriber, #2351)Parent article: Morse code kernel panics Before people make fun of such an idea, I have encountered hardware which does something similar. With an HP ZX6000 (an Itanium2 box), there is a small port on the front of the case. When there's a hardware problem, in addition to the blinking LEDs (which diagnose to a subsytem), you can hold a phone up to the port and it will chirp to the listening system on the other end to diagnose to the component level. Unfortunately, I have had to use this more than once on this particular piece of hardware....
(Log in to post comments)
Morse code kernel panics Posted Feb 6, 2003 5:40 UTC (Thu) by cpeterso (guest, #305) [Link] My cable modem has various blinken lights. In the user manual, there is a glossary of all the long/short blink patterns to help you diagnose network problems. It's helpful on a monitor-less modem (but I always need to dig around to find the user manual). This seems pointless on a Linux box with a monitor, but if a headless system this might be useful.
Morse code kernel panics Posted Feb 6, 2003 19:28 UTC (Thu) by emkey (guest, #144) [Link] Back in the days of the Sun 3's and older Sun had something called a "Cylon" on the back of many of their systems. Basically it was a series of seven or so small red LED's. When things were going well they would cycle much like the Cylon's helmits on the old BattleStar Galactica series. When the system was haevily loaded the cycling would slow down. When the system crashed different LED's would remain lit depending on what the problem was. Later on Sun switched to using the keyboard LED's in a similer way, but it was never anywhere near as cool or useful.Sun's "cylon" lights were just another method of doing what this patch does, and from that experience I'm pretty sure this patch would be a useful one to have incorporated.
|
|||||||||||