From: lambertarthur22@gmail.com (Arthur LAMBERT)
To: linux-arm-kernel@lists.infradead.org
Subject: issue with kexec/kdump on imx6ull
Date: Tue, 20 Mar 2018 18:16:08 +0100 [thread overview]
Message-ID: <20180320171608.GB32282@arthur-bzh> (raw)
In-Reply-To: <20180320150723.GH2743@n2100.armlinux.org.uk>
Le Tuesday 20 Mar 2018 ? 15:07:23 (+0000), Russell King - ARM Linux a ?crit :
>
> Okay, I recommend that you (and everyone else) uses the tree at:
>
> git://git.armlinux.org.uk/~rmk/kexec-tools.git
>
> which is now up to date with mainline, plus includes the necessary
> fixes for the mis-merge, and subsequent fixes from a previous size-
> related problem from January.
>
> There's also a ti-keystone2 branch which contains an additional
> (hacky and untested) patch which allows reading the coredump
> generated by kexec on a crash.
Hi Russell,
Thanks for your answer. I run my test again with the userspace
kexec tool from git://git.armlinux.org.uk/~rmk/kexec-tools.git.
The result is always the same.
All the patch from your first answer seems to be integrated in
the master branch on this git. I also double check my test to
be sure that its was not an integration error.
Do I need to integrate other patches ? January related problem ?
Regards,
Arthur.
next prev parent reply other threads:[~2018-03-20 17:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-20 10:04 issue with kexec/kdump on imx6ull Arthur LAMBERT
2018-03-20 10:43 ` Russell King - ARM Linux
2018-03-20 15:07 ` Russell King - ARM Linux
2018-03-20 17:16 ` Arthur LAMBERT [this message]
2018-03-20 19:12 ` Russell King - ARM Linux
2018-03-21 13:25 ` Arthur LAMBERT
2018-03-29 20:54 ` Russell King - ARM Linux
2018-04-03 14:15 ` Arthur LAMBERT
2018-04-09 13:58 ` Arthur LAMBERT
2018-04-09 14:31 ` Russell King - ARM Linux
2018-05-16 10:31 ` Arthur LAMBERT
2018-05-16 10:42 ` Russell King - ARM Linux
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=20180320171608.GB32282@arthur-bzh \
--to=lambertarthur22@gmail.com \
--cc=linux-arm-kernel@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