From: Tony Lindgren <tony@atomide.com>
To: Thiago Jung Bauermann <bauerman@linux.vnet.ibm.com>,
Andrew Morton <akpm@linux-foundation.org>
Cc: Eric Biederman <ebiederm@xmission.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org,
Russell King - ARM Linux <linux@armlinux.org.uk>
Subject: Kexec regression in next-20160906
Date: Tue, 6 Sep 2016 15:09:37 -0700 [thread overview]
Message-ID: <20160906220936.4txqzodkgknhjiyh@atomide.com> (raw)
Hi,
Looks like commit 5c01cdd2d4bc ("kexec_file: allow skipping checksum
calculation for some segments") makes next-20160916 stop working for
me at least on ARM.
I now get "kexec_load failed: Invalid argument error" on loading the
new kernel to memory with kexec -l.
Reverting the following two commits makes things work for me again:
d2bf993afdf1 ("kexec_file: add mechanism to update kexec segments")
5c01cdd2d4bc ("kexec_file: allow skipping checksum calculation for
some segments")
Regards,
Tony
8< -------
kernel: 0xb6b77008 kernel_size: 0x3aa538
MEMORY RANGES
0000000080000000-00000000ffcfffff (0)
00000000fff00000-00000000ffffefff (0)
kexec_load: entry = 0x80008000 flags = 0x280000
nr_segments = 2
segment[0].buf = 0xb6b77008
segment[0].bufsz = 0x3aa538
segment[0].mem = 0x80008000
segment[0].memsz = 0x3ab000
segment[1].buf = 0xadf80
segment[1].bufsz = 0x16080
segment[1].mem = 0x81709000
segment[1].memsz = 0x17000
kexec_load failed: Invalid argument
entry = 0x80008000 flags = 0x280000
nr_segments = 2
segment[0].buf = 0xb6b77008
segment[0].bufsz = 0x3aa538
segment[0].mem = 0x80008000
segment[0].memsz = 0x3ab000
segment[1].buf = 0xadf80
segment[1].bufsz = 0x16080
segment[1].mem = 0x81709000
segment[1].memsz = 0x17000
Nothing has been loaded!
next reply other threads:[~2016-09-06 22:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-06 22:09 Tony Lindgren [this message]
2016-09-06 23:33 ` Kexec regression in next-20160906 Thiago Jung Bauermann
2016-09-07 8:08 ` Russell King - ARM Linux
2016-09-08 15:23 ` Thiago Jung Bauermann
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=20160906220936.4txqzodkgknhjiyh@atomide.com \
--to=tony@atomide.com \
--cc=akpm@linux-foundation.org \
--cc=bauerman@linux.vnet.ibm.com \
--cc=ebiederm@xmission.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@armlinux.org.uk \
/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