From: Zac Medico <zmedico@gentoo.org>
To: "Robin H. Johnson" <robbat2@gentoo.org>, gentoo-project@lists.gentoo.org
Cc: gentoo-core@lists.gentoo.org
Subject: [gentoo-project] Re: [gentoo-core] woodpecker.gentoo.org outage post-mortem & request for somebody to package kdump
Date: Sun, 5 Feb 2017 13:21:20 -0800 [thread overview]
Message-ID: <a95f56b5-a531-0278-d1b4-38ede1003b6c@gentoo.org> (raw)
In-Reply-To: <robbat2-20170204T075145-152922337Z@orbis-terrarum.net>
On 02/03/2017 11:59 PM, Robin H. Johnson wrote:
> woodpecker was briefly unavailable again (2017/01/04 06:40-07:10 UTC),
> and was freshly booted to recover, as the VM host threw a kernel panic
> again (it's happened about once a month now, on 2 different boxes).
>
> I did have network console logging enabled on the VM host, but it didn't
> capture anything except the very start of the crash.
>
> Can somebody with time please package the Redhat/Ubuntu kdump tools, so
> that they can be used when the crashkernel boots (that side is already
> done on infra systems as well).
>
> You probably also want to improve this page:
> https://wiki.gentoo.org/wiki/Kernel_Crash_Dumps
>
It looks like debian has a well-maintained repository here, which
includes makedumpfile, and the kdump-tools stuff in the "debian"
subdirectory:
https://anonscm.debian.org/cgit/collab-maint/makedumpfile.git/tree/
Apparently they distribute makedumpfile as a separate package:
https://packages.debian.org/sid/kdump-tools
https://packages.debian.org/sid/makedumpfile
--
Thanks,
Zac
prev parent reply other threads:[~2017-02-05 21:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-04 7:59 [gentoo-project] woodpecker.gentoo.org outage post-mortem & request for somebody to package kdump Robin H. Johnson
2017-02-05 21:21 ` Zac Medico [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=a95f56b5-a531-0278-d1b4-38ede1003b6c@gentoo.org \
--to=zmedico@gentoo.org \
--cc=gentoo-core@lists.gentoo.org \
--cc=gentoo-project@lists.gentoo.org \
--cc=robbat2@gentoo.org \
/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