[lkml]   [1999]   [Jun]   [11]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Profanity in the Linux Kernel?!?!?
On Fri, 11 Jun 1999, Horst von Brand wrote:

> > "fatal exception 0e" a fatal processor exception was trapped. the exception
> > code is 0x0e
> >
> > "at address nnnn" this describes where it happened.
> How do I find out what code 0x0E means? What use is the address? Sorry, I
> have bad memories of an IBM RT and its "error codes", some hex gibberish
> you had to look up in a manual, that very often simply wasn't at hand. And
> having the relevant manual on line isn't at all useful if the machine just
> crashed. This particular type of stuff is handled by Oopsen in Linux, quite
> well I might add.
> --

FYI, the usual "blue screen" is:

Microsoft (R) Windows NT (TN) Version 4.0 (Build 1381: Service Pack 3).
*** STOP: 0x00000078 (0x00000000,0x00000000,0x00000000,0x00000000)
CPUID:GenuineIntel 6.5.2 irql:1 SYSVER 0xf0000565
This sure tells one hell of a lot. I'd much rather have:

"qlogicfc.c: got a null value out of handle_ptrs, this sucks", actual
error message from a Linux SCSI driver.

Dick Johnson
Penguin : Linux version 2.2.6 on an i686 machine (400.59 BogoMips).
Warning : It's hard to remain at the trailing edge of technology.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:52    [from the cache]
©2003-2014 Jasper Spaans. hosted at Digital Ocean