From: Dave Jones <davej@codemonkey.org.uk>
To: Kazuhito Hagio <k-hagio@ab.jp.nec.com>
Cc: "kexec@lists.infradead.org" <kexec@lists.infradead.org>
Subject: Re: makedumpfile: ELF format issues (RE: makedumpfile: Fix divide by zero in print_report())
Date: Wed, 16 Oct 2019 11:29:32 -0400 [thread overview]
Message-ID: <20191016152932.GA25107@codemonkey.org.uk> (raw)
In-Reply-To: <4AE2DC15AC0B8543882A74EA0D43DBEC03591761@BPXM09GP.gisp.nec.co.jp>
On Wed, Oct 09, 2019 at 08:03:51PM +0000, Kazuhito Hagio wrote:
> In this case, was the "makedumpfile Completed." message emitted?
> It looks like the buffer of program headers was not written to the file..
>
> Anyway, a debugging patch attached below.
Our kdump tooling redirects makedumpfile output to dmesg, and unfortunately this debug
patch produces so much info it filled the ring buffer, so we didn't
catch the beginning.
I'll rework things so that it redirects to a file instead of dmesg, but
it's going to take me a while to get that deployed and tested.
Dave
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2019-10-16 15:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-09 20:03 makedumpfile: ELF format issues (RE: makedumpfile: Fix divide by zero in print_report()) Kazuhito Hagio
2019-10-09 21:38 ` Dave Jones
2019-10-28 15:18 ` Kazuhito Hagio
2019-11-07 16:12 ` Kazuhito Hagio
2019-11-13 19:36 ` Kazuhito Hagio
2019-11-22 20:37 ` Dave Jones
2019-10-16 15:29 ` Dave Jones [this message]
2019-10-17 20:55 ` Kazuhito Hagio
2019-10-18 4:36 ` Dave Jones
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=20191016152932.GA25107@codemonkey.org.uk \
--to=davej@codemonkey.org.uk \
--cc=k-hagio@ab.jp.nec.com \
--cc=kexec@lists.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