public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: ebiederm@xmission.com (Eric W. Biederman)
To: Venkappa Mala <Venkappa.Mala@lntinfotech.com>
Cc: "rmk+lkml\@arm.linux.org.uk" <rmk+lkml@arm.linux.org.uk>,
	<linux-kernel@vger.kernel.org>,
	Kexec Mailing List <kexec@lists.infradead.org>
Subject: Re: Linux kernel crash dumps for ARM
Date: Mon, 04 Jan 2010 21:20:23 -0800	[thread overview]
Message-ID: <m17hrx9lgo.fsf@fess.ebiederm.org> (raw)
In-Reply-To: <EB1A7C66AD0C92419BFFC785A947865A09EA8C9129@BLRINMSMBX01.bglrodc.lntinfotech.com> (Venkappa Mala's message of "Tue\, 5 Jan 2010 10\:19\:31 +0530")

Venkappa Mala <Venkappa.Mala@lntinfotech.com> writes:

I have added the kexec list and corrected the lkml addresses.
In principle it should not be too hard to use kexec on panic
support on arm.

I don't do any arm development so I don't have a clue what the status
of the support is on arm.

> Hi,
>
> With respect to "Linux kernel crash dumps for ARM", i have some doubts which are described as below.
>
> If the machine has crashed so badly that you cannot enter commands or
> the disk is not available then you have three options :-
>
> (1) Hand copy the text from the screen
>
> (2) capture crash logs using Minicom.
>
> (3) save the crash data to a floppy disk or video rom or a swap partition or reserved memory.
>
> In the above three options, 1 & 2 are known and works as well.
>
> Regarding 3 option,
> ----------------------------
> i would like to support for ARM11.
>
> As far as i know, the supported linux kernel crash dumps are
> "lkcd, netdump,diskdump, mini kernel dump and kdump/kexec".
> These are supported for x86 and PowerPC architectures with some constrains.
>
> i have some queries with respect to ARM supports, these are
>
> 1.) kexec is supported in latest kernels
>         example: 2.6.29 kernel
>         File: arch/arm/kernel/machine_kexec.c
>
>     - is this working well or is there any constraints?
>
> 2) As per kexec supports, kexec-tool is required and this allows you to load directly
>    to a new kernel from the currently running one
>
>     As from my side, i am not able to find arm implementation support in kexec-tools/crash sources.
>
>    - is kexce-tool supported for ARM or not?
>
> 3) In lkcd, netdump,diskdump, mini kernel dump and kdump/kexec tools,
>
>    - which is the best choice for ARM or are there any best crash dump tool for ARM?
>
> Please clarify my queries.
>
> Best Regards,
> Venkappa

Eric


  parent reply	other threads:[~2010-01-05  5:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <EB1A7C66AD0C92419BFFC785A947865A09EA8C9129@BLRINMSMBX01.bglrodc.lntinfotech.com>
2010-01-05  4:51 ` Linux kernel crash dumps for ARM Venkappa Mala
2010-01-05  5:20 ` Eric W. Biederman [this message]
2010-01-05  8:30   ` Bernhard Walle
2010-01-05  8:48   ` Paul Mundt
2010-01-05  9:16     ` Simon Horman
2010-01-05 19:00       ` Russell King
2010-01-05 22:02         ` Simon Horman

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=m17hrx9lgo.fsf@fess.ebiederm.org \
    --to=ebiederm@xmission.com \
    --cc=Venkappa.Mala@lntinfotech.com \
    --cc=kexec@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rmk+lkml@arm.linux.org.uk \
    /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