linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dave Young <dyoung@redhat.com>
To: CAI Qian <caiqian@redhat.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
	ltp-list <ltp-list@lists.sourceforge.net>,
	crash-utility <crash-utility@redhat.com>,
	kexec <kexec@lists.infradead.org>,
	kexec kdump redhat mailing list  <kexec-kdump-list@redhat.com>
Subject: Re: [RFC] autokdump - automated kdump testsuite
Date: Mon, 22 Sep 2014 17:07:16 +0800	[thread overview]
Message-ID: <20140922090716.GA23854@darkstar.nay.redhat.com> (raw)
In-Reply-To: <293476264.25264480.1411120345360.JavaMail.zimbra@redhat.com>

Hi,

On 09/19/14 at 05:52am, CAI Qian wrote:
> I plan to release an automated kdump testsuite that will be
> focus on testing kernel and the crash utility. It should work
> for all major distros since it will use none of distro-specific
> stuff, and also support different arches including x86, ARM,
> PPC64 and s390x.

It's a good idea to create a kdump test project. Maybe you can consider to
test kexec as well.

> 
> It does the following:
> 1) check if there is a memory reserved for kdump. If not,
>    reserve the memory and reboot the system.
> 2) once the system is back, load kexec on panic and
>    prepare a separate initramfs that including needed
>    modules to load a local filesystem and necessary utilities
>    in order to analyse /proc/vmcore in the 2nd kernel.
> 3) trigger the system crash using methods like sysrq-c, NMI,
>    and panic_on_hung_task etc.
> 4) in the 2nd kernel, mount a filesystem and use the crash
>    utility to analyse /proc/vmcore. Then, gather the analyse
>    logs, serial console output, dmesg etc into the filesystem.
> 5) reboot back into the 1st kernel.
> 
> implementation:
> It will setup a daemon to handle reboots.
> 
> plan:
> I might also to test the makedumpfile all together later.

For makedumpfile, IMO you can add several test cases and collect the dump
time, vmcore size data as test results besides of the dump status.

Thanks
Dave

  parent reply	other threads:[~2014-09-22  9:07 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <145412866.25258463.1411119061796.JavaMail.zimbra@redhat.com>
2014-09-19  9:52 ` [RFC] autokdump - automated kdump testsuite CAI Qian
2014-09-19 13:22   ` Vivek Goyal
2014-09-19 13:33     ` Vivek Goyal
2014-09-22 13:00     ` CAI Qian
2014-09-22 14:47       ` Vivek Goyal
2014-09-23  2:53         ` CAI Qian
2014-09-23 12:09           ` Vivek Goyal
2014-09-22  9:07   ` Dave Young [this message]
2014-09-22  9:12   ` Dave Young

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=20140922090716.GA23854@darkstar.nay.redhat.com \
    --to=dyoung@redhat.com \
    --cc=caiqian@redhat.com \
    --cc=crash-utility@redhat.com \
    --cc=kexec-kdump-list@redhat.com \
    --cc=kexec@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ltp-list@lists.sourceforge.net \
    /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;
as well as URLs for NNTP newsgroup(s).