Messages in this thread | | | Date | Tue, 01 Jun 1999 09:36:39 +0000 | From | Studierende der Universitaet des Saarlandes <> | Subject | Re: Crashing linux 2.2.[4-6] - what to do |
| |
> Running through ksymoops doesn't yield very much > - at least not for a kernel illiterate person such > as I:
The oops report is incomplete: there should be some more lines with the stack dump and the call chain.
Note that sometimes klogd is unable to write the data to the harddisk before Linux crashes.
> I'd like a litte additional information, about > how to aid the debugging process.
1) upgrade to a newer kernel, perhaps the problem is already solved. DO NOT USE 2.2.8.
If you want to find the problem: 1) Do you have a second computer nearby? Use a null modem cable and enable the serial console. You can dump the oops report to the other computer, the complete report should be stored.
> Maybe it's becase it's standing next to a lot of NT's, but anyway... Yes you can use even NT to dump the oops.
2) If you are a developer and want to debug it yourself, then there are (AFAIK) 3 kernel debuggers. - remote GDB, you need 2 computers and a serial connection. www.gcom.com
- a kernel debugger from SGI (www.linux.sgi.com) You need only 1 computer, the complete debugger runs in kernel mode.
- the ikd kernel debugger. this is a combined user mode & kernel mode debugger: the kernel is interrupted, and switchted back into user mode. I think you'll have problems if you try to single step interrupts etc. (I never used this debugger, ftp://e-mind.com/...)
-- Manfred
- 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/
| |