Gnarly Error Messages 1315
Veeru writes "In my career, I have run across some whopper error messages, but a call from the mainframe sysop one night beat them all: 'We are experiencing MVS processor spin loops, the programs are running while holding a disabled CPU. This is causing XCF communication delays to the point where we are losing VTAM RTP routing, are suffering OSPF adjacency failures on TCP/IP dynamic routing and MIM VCF failures. Whatever this code is, it should NOT be propagated to production or we run the risk of losing the development plex if XCF signaling is adversely impacted by processor disabled spin loops'. My friend once got an error message 'Error 2 while trying to report error 2'. I would be curious to hear from the Slashdot community on encounters with other bizarre error messages."
Interface Hall of Shame... (Score:5, Informative)
Obligatory Karma Whoring Links (Score:2, Informative)
Also, That Crazy Error Message in Latin [multicians.org].
kernel died. (Score:2, Informative)
Re:Error,Cannot Close Application, Click OK to clo (Score:3, Informative)
At the very least, the line number should be written to a log file, with as much data as you can pull together. A better thing to do is to write a stack trace to a log file, with a snapshot of the environment when it occurred (what you tried to do, locals, globals, etc).
Ellen Error (Score:3, Informative)
http://www.mixed-up.com/markb/humor/mpc.h
"Huh ?"
Re:SGI message - has anybody else had this? (Score:5, Informative)
If an SGI box kernel panics, it does exactly what you described, printing the message "KERNEL PANIC" at the top of the textport and spewing out lots of stack traces after it.
Now, kernel panics are, of course, handled by a handler. (Those panic messages don't happen by magic, you know.) If, on the off chance, your machine should panic, and then panic again inside the panic handler-- apart from meaning something is really, really wrong-- the system prints the message "DOUBLE PANIC" on the screen.
That's probably what you saw. I've seen this many times-- always due to faulty hardware.
Of course, I wouldn't put it past SGI to put a joke in their panic messages. This is, of course, the company that warned users in its workstation owner's guide not to "dangle the mouse by its cable or throw mouse at co-workers."
And there's always the ever-popular audiopanel -spinaltap gag. Running audiopanel with the -spinaltap flag makes the VU meters go to 11. Naturally.
Comment removed (Score:4, Informative)
Re:Interface Hall of Shame... (Score:5, Informative)
Go directly to their error messages page [iarchitect.com], rather than linking through their home page (which does, in all honesty, have a sizeable amount of interesting information on it).
Re:Linux errors are the best (Score:1, Informative)
Checking refrigerator for beer... Refrigerator does not have enough beer.
Or something like that. There's a switch to turn them off, but I never did.
Re:Keyboard error. (Score:3, Informative)
Tab to the button and press enter/space. Should work fine.
Windows media player 7 (Score:2, Informative)
Also of interestError message hall of shame [iarchitect.com]
Re:Keyboard error. (Score:5, Informative)
Re:Interface Hall of Shame... (Score:4, Informative)
eg. print error prints success because of second function.
Re:Printer on fire (Score:5, Informative)
See this linux kernel post [iu.edu].
Guru Meditation Mode (Score:3, Informative)
As an Amiga assembly-language programmer back in the 80's I had great admiration for the hardware architecture, especially the powerful "Blitter" and "Copper" chips which were responsible for doing "bit-plane" operations and displaying Copper Lists (i.e., Display Lists). Unfortunately, mucking around directly with the hardware registers resulted in countless appearances of the red-double-line-bordered screen of death with the ominous message "Guru Meditation Mode" followed by two long cryptic hexadecimal numbers indicating the machine address and the code of the error.
I almost miss those days. Now I'm stuck with a Mac that never crashes. *sigh*
Re:"Your system date is set to year 8192. (Score:4, Informative)
Re:Amiga: "User Stupidity Error" (Score:3, Informative)
I was going to mention this one, but you beat me to it. I always thought that error message was a riot. I got it when trying to rename a file to the same name as a directory (in the same directory).
And it was "Disk Man", or at least that's the name on the icon of my 2500. (Powered up for the first time on about 2 years!)
Milalwi
Re:Mac Bomb (Score:3, Informative)
Re:Linux errors are the best (Score:3, Informative)
Checking for mass_quantities_of_bass_ale in -lfridge...not found!
Checking for mass_quantities_of_any_ale in -lfridge...not found!
Re:Interface Hall of Shame... (Score:3, Informative)
Re:Read BSOD (Score:2, Informative)
Re:Turn the computer off (Score:4, Informative)
- most newer PS/2 keyboards can be hot plugged with no problem
- most older (AT-style) keyboards with a PS/2 adaptor will cause damage
- the damage is actually caused by a filter capacitor in the keyboard drawing too much juice initially for the poor little fuse on the PS/2 port to handle. If you look at any mbd with PS/2 ports (and you know what a surface mount fuse looks like) you'll see one each for the mouse and keyboard
- newer keyboards (anything made in the last 4 or 5 years) are better designed and have smaller filter capacitors, hence less risk (if any) of blowing the fuse
- if you do blow the fuse you can just bridge it with a carefully bent paperclip or a bit of careful soldering; I've never seen any other part of the circuit take any damage after bridging, even with repeated hot-plugs of the keyboard (or mouse) which toasted the fuse originally
But yeah, hot-plugging anything that isn't actually designed for it is kind of asking for trouble.
Re:Actually it's F1 (Score:2, Informative)
Plus, an 8 megabyte (you used little b, I assume you mean bits?) BIOS wouldn't surprise me. I don't know what the BIOS sizes on newer motherboards are now, though.
Re:Error,Cannot Close Application, Click OK to clo (Score:3, Informative)
An unexpected error has occurred. The details of the error have been recorded in the log file:
Log file name
Please email the above file to devteam@company.invalid.
Your currently-opened files have been saved as the files:
Filename 1
Filename 2
[Application name] will now quit.
and then quit as gracefully as possible.
This does a couple of things:
1. It saves the state in a logfile.
2. It tells the user what is going on, without confusing them.
3. It allows the user the option of opening the logfile and seeing what info they will be sending the developer.
4. It allows the user to recover their work (hopefully - not always possible).
Guru Meditation (Score:3, Informative)
The guru meditation errors told what operation was being executed, and the memory address, and it might have shown you the CPU state register or something, but I don't think so. As the 68000 (the least CPU AmigaDOS ran on) is a 16 bit CPU with 24 bit addressing this generated some extremely lengthy numbers for the time.
There were two types of guru meditation, one which rebooted your computer afterwards automatically, and a recoverable alert which you could click out of. There used to be a program whose name I do not remember which would capture alerts by inserting some code into the handlers for a whole bunch of interrupts.
See the Amiga had a cool feature, a "Patchlist" which you could use to patch a number of different functions without stepping on any already-installed patches. Kind of like vector tables, but without the suck. (In order to have DOS TSRs which don't step on each other, for example, you would have to look at the vector table manually, read the instruction currently in the table, which is probably a call, and record it, then append it to your own call in memory somewhere and replace the entry in the vector table with a different call. The Patchlist removes this kind of inanity. It wasn't always flawless but the Amiga forced programmers to be good to one another's memory spaces because it didn't have memory protection.
Anyway enough nostalgia. I still have an A1200 but unless I get an accelerator it's going to stay in storage.
Re:Keyboard error. (Score:2, Informative)
This instruction is used as a power management technique, and also helps cool the cpu down.
Anyway the hlt instruction should work, but for some reason was broken on some AMD K6 cpu's. The solution was to pass a special kernel parameter (I think) to get linux to not use that instruction. Either that or compile without APM support.. I forget now...
MVS messages in spin loops? No way no how! (Score:2, Informative)
You're confusing an error message with an operator's description of a problem. MVS can't display error messages while in disabled spin loops, the I/O interrupts are blocked by the "disabled" part!
You want a good example of bad error messages? How about anything except MVS messages? I'm serious - the MVS "Messages and Codes" manuals are huge, and list every message issued by the software complete with advice on what to do when you receive the message! How, one asks, can you find the right advice? Easy: every message begins with a "message identifier" - a short alphanumeric sequence that uniquely identifies it and points directly to the place where the doc lives.
Try that with your average Open Source project. Hell, try to just get a list of the errors reported, let alone advice on what to do when they are reported.