From: Bouchard Louis <louis.bouchard@canonical.com>
To: Vivek Goyal <vgoyal@redhat.com>
Cc: Bouchard Louis <louis.bouchard@canonical.com>,
"kexec@lists.infradead.org" <kexec@lists.infradead.org>
Subject: Re: [Bug] Kdump does not work when panic triggered due to MCE
Date: Tue, 10 May 2011 09:31:14 +0200 [thread overview]
Message-ID: <4DC8E9C2.3030801@canonical.com> (raw)
In-Reply-To: <20110509154606.GE5975@redhat.com>
Hello,
Le 09/05/2011 17:46, Vivek Goyal a écrit :
> Louis, is this "crashdc" an independent executable. Where is it packaged?
> What is the significance of name "crashdc" (Crash data collecor ?) Will it
> make sense to merge it with makedumpfile which does kernel filtering
> already and this could be one of the additional features.
>
> Thanks
> Vivek
crashdc is hosted no SF. You can have a look at it here :
http://crashdc.svn.sourceforge.net/viewvc/crashdc/trunk/and
Most of the work happens in /usr/bin/crashdc and the
run-crashdc-{distro}.sh scripts.
It does indeed means crash data collector. It basically is a set of
shell script that send a set of predefined commands to the crash utility
and gather the result in a text file that can be easily sent over email.
In one implementation, it makes use of the KDUMP_POST mechanism to run.
Another way to use it is through an init script upon reboot.
As for merging it with makedumpfile, it could be an interesting choice.
But that might add requirements to makedumpfile that you might not want
to have (dependencies on crash & the kernel-debuginfo packages which are
needed).
I have recently changed jobs, so I had to suspend my work on crashdc a
bit. I'm hoping to find time to work on it and adapt it to debian based
distro in the near future.
Kind regards,
...Louis
--
Louis Bouchard
Server Support Analyst
Canonical Ltd
Ubuntu support: http://landscape.canonical.com
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2011-05-10 7:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-06 16:54 [Bug] Kdump does not work when panic triggered due to MCE K.Prasad
2011-05-06 17:38 ` Andi Kleen
2011-05-09 16:35 ` K.Prasad
2011-05-10 1:28 ` Huang Ying
2011-05-09 12:39 ` Vivek Goyal
2011-05-09 15:21 ` Bouchard Louis
2011-05-09 15:46 ` Vivek Goyal
2011-05-10 7:31 ` Bouchard Louis [this message]
2011-05-09 17:03 ` K.Prasad
2011-05-10 7:19 ` Bouchard Louis
2011-05-10 10:21 ` WANG Cong
2011-05-09 16:53 ` K.Prasad
2011-05-09 17:05 ` Vivek Goyal
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=4DC8E9C2.3030801@canonical.com \
--to=louis.bouchard@canonical.com \
--cc=kexec@lists.infradead.org \
--cc=vgoyal@redhat.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