Re: how to capture kernel panics

[Jeff Moyer <jmoyer@redhat.com>]

==> Regarding Re: how to capture kernel panics; "shabanip" <shabanip@avapajoohesh.com> adds:

shabanip> as i see netconsole is a kernel module.  so i just need to load
shabanip> netconsole module with server:port parameters.  am i right?

MODULE_PARM_DESC(netconsole, " netconsole=[src-port]@[src-ip]/[dev],[tgt-port]@<tgt-ip>/[tgt-macaddr]\n");

So, for example:

modprobe netconsole netconsole=6666@192.168.1.1/eth0,6666@192.168.1.100/00:40:95:9A:12:34

-Jeff


shabanip> Payam Shabanian shabanip -at- avapajoohesh.com

>> ==> Regarding Re: how to capture kernel panics; Christian Borntraeger
>> <linux-kernel@borntraeger.net> adds:
>> 
linux-kernel> shabanip wrote:
>>>> is there any way to capture and log kernel panics on disk or ...?
>>
linux-kernel> In former times, the Linux kernel tried to sync in the panic
linux-kernel> function. (If the panic did not happen in interrupt context)
linux-kernel> Unfortunately this had severe side effects in cases where
>> the
linux-kernel> panic was triggered by file system block device code or any
linux-kernel> other part which is necessary for syncing. In most cases the
linux-kernel> call trace never made it onto disk anyway. So currently the
linux-kernel> kernel does not support saving a panic.
>>
linux-kernel> Apart from using a serial console, you might have a look at
linux-kernel> several kexec/kdump/lkcd tools where people are working on
linux-kernel> being able to dump the memory of a paniced kernel.
>> Or netconsole, which will dump printk's do the server:port of your
>> choosing.
>> 
>> -Jeff
>> 

shabanip> - To unsubscribe from this list: send the line "unsubscribe
shabanip> linux-kernel" in the body of a message to
shabanip> majordomo@vger.kernel.org More majordomo info at
shabanip> http://vger.kernel.org/majordomo-info.html Please read the FAQ at
shabanip> http://www.tux.org/lkml/