This is what I did based on your original comments. I slightly altered it
so that stuff will hopefully go to the maintainers first (reversed patch
sorry)
--- Documentation/oops-tracing.txt Fri Jan 1 00:29:55 1999
+++ Documentation/oops-tracing.txt~ Sun Nov 8 14:28:10 1998
@@ -1,24 +1,3 @@
-Quick Summary
--------------
-
-cd /usr/src/linux/scripts
-g++ -o ksymoops ksymoops.cc
-./ksymoops ../System.map < the_oops.txt
-
-and send the output the maintainer of the kernel area that seems to be
-involved with the problem. Don't worry too much about getting the wrong
-person. If you are unsure send it to the person responsible for the code
-relevant to what you were doing. If it occurs repeatably try and describe
-how to recreate it. Thats worth even more than the oops
-
-If you are totally stumped as to whom to send the report, send it to
-linux-kernel@vger.rutgers.edu. Thanks for your help in making Linux as
-stable as humanly possible.
-
-
-Full Information
-----------------
-
From: Linus Torvalds <torvalds@cs.helsinki.fi>
How to track down an Oops.. [originally a mail to linux-kernel]
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/