diff options
| author | Ralf Baechle <ralf@linux-mips.org> | 1999-02-15 02:15:32 +0000 |
|---|---|---|
| committer | Ralf Baechle <ralf@linux-mips.org> | 1999-02-15 02:15:32 +0000 |
| commit | 86464aed71025541805e7b1515541aee89879e33 (patch) | |
| tree | e01a457a4912a8553bc65524aa3125d51f29f810 /Documentation/oops-tracing.txt | |
| parent | 88f99939ecc6a95a79614574cb7d95ffccfc3466 (diff) | |
Merge with Linux 2.2.1.
Diffstat (limited to 'Documentation/oops-tracing.txt')
| -rw-r--r-- | Documentation/oops-tracing.txt | 21 |
1 files changed, 21 insertions, 0 deletions
diff --git a/Documentation/oops-tracing.txt b/Documentation/oops-tracing.txt index 6e685aa64..108c3b645 100644 --- a/Documentation/oops-tracing.txt +++ b/Documentation/oops-tracing.txt @@ -1,3 +1,24 @@ +Quick Summary +------------- + +cd /usr/src/linux/scripts/ksymoops +make ksymoops +./ksymoops < 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] |