From: Mike Galbraith <efault@gmx.de>
To: Joe Smith <codesoldier1@gmail.com>
Cc: Randy Dunlap <rdunlap@infradead.org>, linux-kernel@vger.kernel.org
Subject: Re: crash binary for latest unreleased kernel
Date: Sun, 28 Jan 2018 11:00:24 +0100 [thread overview]
Message-ID: <1517133624.6669.22.camel@gmx.de> (raw)
In-Reply-To: <1517131246.6669.11.camel@gmx.de>
On Sun, 2018-01-28 at 10:20 +0100, Mike Galbraith wrote:
> On Sun, 2018-01-28 at 00:37 -0800, Joe Smith wrote:
> > I happen to look at the patches for the crash binary and came across
> > this log entry from Jan 19. I am also using 4.15-rc kernel. Not
> > knowing anything about crash it is hard to even attempt to fix it.
>
> It may not work all that well if box does something new/creative, but
> mundane manual crash, and live rummaging seem to work well enough.
And looking through my modified makedumpfile package, looks like I've
replaced everything I had ever done do it with backports from newer
versions, so you should be able to get kdump working with nothing more
than an update to makefumpfile, plus virgin upstream crash source.
-Mike
next prev parent reply other threads:[~2018-01-28 10:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-26 20:52 crash binary for latest unreleased kernel Joe Smith
2018-01-27 4:32 ` Mike Galbraith
2018-01-27 4:38 ` Randy Dunlap
2018-01-27 4:48 ` Mike Galbraith
2018-01-28 8:37 ` Joe Smith
2018-01-28 9:20 ` Mike Galbraith
2018-01-28 10:00 ` Mike Galbraith [this message]
2018-01-28 20:19 ` Joe Smith
2018-01-31 3:51 ` Mike Galbraith
2018-01-31 16:03 ` Mike Galbraith
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=1517133624.6669.22.camel@gmx.de \
--to=efault@gmx.de \
--cc=codesoldier1@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.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