From: Jeff Moyer <jmoyer@redhat.com>
To: "shabanip" <shabanip@avapajoohesh.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: how to capture kernel panics
Date: Fri, 25 Feb 2005 10:48:56 -0500 [thread overview]
Message-ID: <16927.18664.299731.615826@segfault.boston.redhat.com> (raw)
In-Reply-To: <56349.69.93.110.242.1109346680.squirrel@69.93.110.242>
==> Regarding Re: how to capture kernel panics; "shabanip" <shabanip@avapajoohesh.com> adds:
shabanip> thanks for the help. does anything else left to configure?
On the log target system, you will probably want to run something similar
to netcat to capture the logs. To simply output to a terminal, you could
do something like this:
nc -l -p 6666 -u
-Jeff
shabanip> Payam Shabanian shabanip -at- avapajoohesh.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/
>>
prev parent reply other threads:[~2005-02-25 15:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-24 23:35 shabanip
2005-02-25 3:08 ` James Colannino
2005-02-25 13:26 ` Trond Hasle Amundsen
2005-02-25 14:17 ` Christian Borntraeger
2005-02-25 14:42 ` Jeff Moyer
2005-02-25 15:07 ` shabanip
2005-02-25 15:28 ` Jeff Moyer
2005-02-25 15:51 ` shabanip
2005-02-25 15:48 ` Jeff Moyer [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=16927.18664.299731.615826@segfault.boston.redhat.com \
--to=jmoyer@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=shabanip@avapajoohesh.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®