On Mondayen den 29 October 2001 12.13, Juan Quintela wrote: > >>>>> "oden" == Oden Eriksson <[EMAIL PROTECTED]> writes:
> oden> Is there a ML FAQ on kernel debugging somewhere? > > see Documentation/oops-tracing.txt Got it, thanks. > but if you found ever that situation, please, press bt, and send me > the output please, that is the easiest way to know what is the > problem, I know that if you don't have a serial console (see > /usr/src/linux/Documentation/serial_console.txt) you need to type it > by hand :( But that is the better info to know what is happening. I read this one too, and the easiest way to me seems to use a patch that dumps the oops info to a file (like nt does). Having a console on the serial interface is neat too, I need to test that. Thanks. -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- | Oden Eriksson, Deserve-IT Networks, Jokkmokk, Sweden. | Mandrake Linux release 8.2 (Cooker) for i586 | Current uptime with kernel 2.4.12-6mdksmp: 9:13 | cpu0 @ 814.28 bm, fan 4470 rpm, temp +30.0�C | cpu1 @ 815.92 bm, fan 4470 rpm, temp +28�C
