On Fri, 4 Jan 2002 17:53:05 +1000, Adrian Head <ahead@bigpond.net.au> wrote: >This is what I'm having trouble with at the moment. When the kernel Oops >occurs it drops me into kdb (kernel debugger). From here I can look at >current process status, do back traces on anything thats running etc.. but it >never shows me the full Kernel Oops and there is no record of it in the logs >either. I expect that a couple of backtraces, list of processes, register >values would be equivalent to a Kernel Oops report? If you type 'go' in kdb then the kernel will continue with the rest of the oops processing. The registers and backtrace from kdb are better data than oops can do, more detailed and more accurate. The oops report gives the failing code, use 'id %eip' in kdb to decode the current instructions.
