patch-2.2.0-pre4 linux/Documentation/oops-tracing.txt

• Lines: 25
• Date: Sat Jan 2 10:02:04 1999
• Orig file: v2.2.0-pre3/linux/Documentation/oops-tracing.txt
• Orig date: Sat May 2 14:19:51 1998

diff -u --recursive --new-file v2.2.0-pre3/linux/Documentation/oops-tracing.txt linux/Documentation/oops-tracing.txt
@@ -1,3 +1,24 @@
+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]