All of lore.kernel.org
 help / color / mirror / Atom feed
From: Baoquan He <bhe@redhat.com>
To: Philip Prindeville <philipp@fedoraproject.org>
Cc: Pratyush Anand <panand@redhat.com>, kexec@lists.infradead.org
Subject: Re: Questions about kexec-tools (resend to list)
Date: Sat, 11 Mar 2017 08:16:42 +0800	[thread overview]
Message-ID: <20170311001642.GA12734@x1> (raw)
In-Reply-To: <5FF5ABAA-DA98-472E-8598-3122D4B1B55B@fedoraproject.org>

On 03/10/17 at 01:20pm, Philip Prindeville wrote:
> 
 
> 
> The above memory ranges look highly suspect.
> 
> Anyone have any ideas where I should start digging to figure out where things are going sideways?
> 
> I’m using 2.0.14 on a Linux 4.4.19 kernel, with gcc 5.3.0 and MUSL 1.1.16.

Hi,

This is user space program and using in 1st kernel. I really suggest you
should start a gdb to track what's going on when your real /proc/iomem
is different with the debug printing of kexec. Honestly, it won't be too
difficult, I really like this kind of debugging. If happened in kdump
kernel, even in user space tools like makedumpfile, you have to add
debug printing again and again.

Thanks
Baoquan
> 

_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

  reply	other threads:[~2017-03-11  0:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-04 23:26 Questions about kexec-tools (resend to list) Philip Prindeville
2017-03-07 14:53 ` Pratyush Anand
2017-03-07 23:34   ` Philip Prindeville
2017-03-08 11:33     ` Pratyush Anand
2017-03-08 17:29       ` Philip Prindeville
2017-03-09  5:29         ` Pratyush Anand
2017-03-10 19:09           ` Philip Prindeville
2017-03-10 20:20         ` Philip Prindeville
2017-03-11  0:16           ` Baoquan He [this message]
2017-03-11  3:14             ` Philip Prindeville

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=20170311001642.GA12734@x1 \
    --to=bhe@redhat.com \
    --cc=kexec@lists.infradead.org \
    --cc=panand@redhat.com \
    --cc=philipp@fedoraproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.