Messages in this thread Patch in this message | | | Date | Sun, 26 Dec 1999 19:50:23 +0100 | From | Manfred Spraul <> | Subject | [PATCH] Documentation/oops-tracking update |
| |
SMP kernel have a far lower chance to log an oops to the kernel log, because they often loose a spinlock. I think we should document that in the oops-tracking document: My patch is below, what do you think?
-- Manfred--- 2.3/Documentation/oops-tracing.txt Fri Nov 12 12:50:31 1999 +++ build-2.3/Documentation/oops-tracing.txt Sun Dec 26 19:48:49 1999 @@ -26,17 +26,21 @@ buffers and save it. Or you can cat /proc/kmsg > file, however you have to break in to stop the transfer, kmsg is a "never ending file". If the machine has crashed so badly that you cannot enter commands or -the disk is not available then you have three options :- +the disk is not available then you have four options :- -(1) Hand copy the text from the screen and type it in after the machine +(1) Compile the kernel for uni-processor: uni-processor kernels have a + higher chance to write the oops to the disk. + +(2) Hand copy the text from the screen and type it in after the machine has restarted. Messy but it is the only option if you have not planned for a crash. -(2) Boot with a serial console (see Documentation/serial-console.txt), +(3) Boot with a serial console (see Documentation/serial-console.txt), run a null modem to a second machine and capture the output there using your favourite communication program. Minicom works well. + You can also use a parallel printer. -(3) Patch the kernel with one of the crash dump patches. These save +(4) Patch the kernel with one of the crash dump patches. These save data to a floppy disk or video rom or a swap partition. None of these are standard kernel patches so you have to find and apply them yourself. Search kernel archives for kmsgdump, lkcd and
| |