From: Anthony Wright <anthony@overnetdata.com>
To: kexec@lists.infradead.org
Subject: Can't load bzImage crashkernel on xen system with 32 bit kernel
Date: Tue, 08 Jul 2014 11:34:51 +0100 [thread overview]
Message-ID: <53BBC94B.8060905@overnetdata.com> (raw)
After successfully modifying kexec-tools to get it to load a crashkernel
on a standard 32 bit linux 3.10.17 kernel, I tried to get it to load the
same crashkernel on the same 32 bit linux kernel running under xen
4.4.0, but get the error "Cannot load <kernel-path>".
I've patched the code to include some diagnostics, and the problem is
caused by add_memmap() reporting that it's been called with overlapping
memory.
It's called twice, the first time it's called with:
address: 0x00000000
size: 0x0009f800
type: 0
This comes from info->backup_src_*
The second time it is passed
address: 0x00000000
size: 0x00000000
type: 0
This is derived from the crash_reserved_mem[] array, which has one
element with the values:
start: 0x0000000000000000 (16 0's)
end: 0xffffffffffffffff (16 f's)
The problem isn't caused by the zero size because the maths in
add_memmap, uses size to calculate end which overflows back again, and
(partially) cancels out the error. The problem is caused by the two
memory blocks being based at 0x0, causing the blocks to overlap.
I'm not sure what the correct functionality should be.
Thanks,
Anthony.
--
Founder, Overnet Data Ltd
+44-1604-807545
www.overnetdata.com
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next reply other threads:[~2014-07-08 10:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-08 10:34 Anthony Wright [this message]
2014-07-10 7:47 ` Can't load bzImage crashkernel on xen system with 32 bit kernel WANG Chao
2014-07-10 10:11 ` Anthony Wright
2014-07-11 7:58 ` WANG Chao
2014-07-11 9:38 ` David Vrabel
2014-07-11 11:27 ` Anthony Wright
2014-07-11 12:17 ` David Vrabel
2014-07-14 11:01 ` Anthony Wright
2014-07-30 9:52 ` David Vrabel
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=53BBC94B.8060905@overnetdata.com \
--to=anthony@overnetdata.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