From: "Jan Beulich" <JBeulich@suse.com>
To: "Olaf Hering" <olaf@aepfle.de>
Cc: <kexec@lists.infradead.org>, <xen-devel@lists.xensource.com>,
<linux-kernel@vger.kernel.org>
Subject: Re: [Xen-devel] incorrect layout of globals from head_64.S during kexec boot
Date: Fri, 06 Jul 2012 09:29:15 +0100 [thread overview]
Message-ID: <4FF6BDFB020000780008DFEF@nat28.tlf.novell.com> (raw)
In-Reply-To: <20120705210607.GA26908@aepfle.de>
>>> On 05.07.12 at 23:06, Olaf Hering <olaf@aepfle.de> wrote:
> My question is: were to put additional debug to trace the copying of the
> data section to its final destination? Is this a task of kexec -l or
> does that happen during decompressing? I suspect the latter. This is the
> console output before the crash (the crash happens in 'movq %rax, %cr3'):
>
> ...
> [ 44.072548] Starting new kernel
> I'm in purgatory
> early console in decompress_kernel
>
> Decompressing Linux... Parsing ELF... done.
According to this, I'd first of all extend the printing done on
arch/x86/boot/compressed/misc.c:parse_elf(). One possible
problem (without much looking at how the individual address
ranges get determined) could be overlapping memory ranges
in the call to memcpy() inside the loop.
Jan
WARNING: multiple messages have this Message-ID (diff)
From: "Jan Beulich" <JBeulich-IBi9RG/b67k@public.gmane.org>
To: Olaf Hering <olaf-QOLJcTWqO2uzQB+pC5nmwQ@public.gmane.org>
Cc: xen-devel-GuqFBffKawuULHF6PoxzQEEOCMrvLtNR@public.gmane.org,
kexec-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [Xen-devel] incorrect layout of globals from head_64.S during kexec boot
Date: Fri, 06 Jul 2012 09:29:15 +0100 [thread overview]
Message-ID: <4FF6BDFB020000780008DFEF@nat28.tlf.novell.com> (raw)
In-Reply-To: <20120705210607.GA26908-QOLJcTWqO2uzQB+pC5nmwQ@public.gmane.org>
>>> On 05.07.12 at 23:06, Olaf Hering <olaf-QOLJcTWqO2uzQB+pC5nmwQ@public.gmane.org> wrote:
> My question is: were to put additional debug to trace the copying of the
> data section to its final destination? Is this a task of kexec -l or
> does that happen during decompressing? I suspect the latter. This is the
> console output before the crash (the crash happens in 'movq %rax, %cr3'):
>
> ...
> [ 44.072548] Starting new kernel
> I'm in purgatory
> early console in decompress_kernel
>
> Decompressing Linux... Parsing ELF... done.
According to this, I'd first of all extend the printing done on
arch/x86/boot/compressed/misc.c:parse_elf(). One possible
problem (without much looking at how the individual address
ranges get determined) could be overlapping memory ranges
in the call to memcpy() inside the loop.
Jan
WARNING: multiple messages have this Message-ID (diff)
From: "Jan Beulich" <JBeulich@suse.com>
To: Olaf Hering <olaf@aepfle.de>
Cc: xen-devel@lists.xensource.com, kexec@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [Xen-devel] incorrect layout of globals from head_64.S during kexec boot
Date: Fri, 06 Jul 2012 09:29:15 +0100 [thread overview]
Message-ID: <4FF6BDFB020000780008DFEF@nat28.tlf.novell.com> (raw)
In-Reply-To: <20120705210607.GA26908@aepfle.de>
>>> On 05.07.12 at 23:06, Olaf Hering <olaf@aepfle.de> wrote:
> My question is: were to put additional debug to trace the copying of the
> data section to its final destination? Is this a task of kexec -l or
> does that happen during decompressing? I suspect the latter. This is the
> console output before the crash (the crash happens in 'movq %rax, %cr3'):
>
> ...
> [ 44.072548] Starting new kernel
> I'm in purgatory
> early console in decompress_kernel
>
> Decompressing Linux... Parsing ELF... done.
According to this, I'd first of all extend the printing done on
arch/x86/boot/compressed/misc.c:parse_elf(). One possible
problem (without much looking at how the individual address
ranges get determined) could be overlapping memory ranges
in the call to memcpy() inside the loop.
Jan
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2012-07-06 9:21 UTC|newest]
Thread overview: 70+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-05 21:06 incorrect layout of globals from head_64.S during kexec boot Olaf Hering
2012-07-05 21:06 ` Olaf Hering
2012-07-06 8:29 ` Jan Beulich [this message]
2012-07-06 8:29 ` [Xen-devel] " Jan Beulich
2012-07-06 8:29 ` Jan Beulich
2012-07-06 8:41 ` Daniel Kiper
2012-07-06 8:41 ` Daniel Kiper
2012-07-06 8:41 ` Daniel Kiper
2012-07-06 12:07 ` Olaf Hering
2012-07-06 12:07 ` Olaf Hering
2012-07-06 12:56 ` [Xen-devel] " Jan Beulich
2012-07-06 12:56 ` Jan Beulich
2012-07-06 12:56 ` Jan Beulich
2012-07-06 13:31 ` Olaf Hering
2012-07-06 13:31 ` Olaf Hering
2012-07-06 13:31 ` Olaf Hering
2012-07-06 13:53 ` Jan Beulich
2012-07-06 13:53 ` Jan Beulich
2012-07-06 13:53 ` Jan Beulich
2012-07-06 14:14 ` Olaf Hering
2012-07-06 14:14 ` Olaf Hering
2012-07-06 14:50 ` Jan Beulich
2012-07-06 14:50 ` Jan Beulich
2012-07-06 14:50 ` Jan Beulich
2012-07-06 17:29 ` Olaf Hering
2012-07-06 17:29 ` Olaf Hering
2012-07-10 9:33 ` Olaf Hering
2012-07-10 9:33 ` Olaf Hering
2012-07-10 14:14 ` Konrad Rzeszutek Wilk
2012-07-10 14:14 ` Konrad Rzeszutek Wilk
2012-07-10 14:46 ` Ian Campbell
2012-07-10 14:46 ` Ian Campbell
2012-07-10 14:51 ` Konrad Rzeszutek Wilk
2012-07-10 14:51 ` Konrad Rzeszutek Wilk
2012-07-10 14:51 ` Konrad Rzeszutek Wilk
2012-07-10 15:29 ` Ian Campbell
2012-07-10 15:29 ` Ian Campbell
2012-07-10 15:29 ` Ian Campbell
2012-07-10 15:37 ` Olaf Hering
2012-07-10 15:37 ` Olaf Hering
2012-07-10 15:23 ` Olaf Hering
2012-07-10 15:23 ` Olaf Hering
2012-07-10 17:26 ` Konrad Rzeszutek Wilk
2012-07-10 17:26 ` Konrad Rzeszutek Wilk
2012-07-10 17:26 ` Konrad Rzeszutek Wilk
2012-07-10 18:09 ` Olaf Hering
2012-07-10 18:09 ` Olaf Hering
2012-07-10 18:32 ` Konrad Rzeszutek Wilk
2012-07-10 18:32 ` Konrad Rzeszutek Wilk
2012-07-10 19:08 ` Keir Fraser
2012-07-10 19:08 ` Keir Fraser
2012-07-10 19:08 ` Keir Fraser
2012-07-13 20:20 ` Olaf Hering
2012-07-13 20:20 ` Olaf Hering
2012-07-14 4:54 ` Keir Fraser
2012-07-14 4:54 ` Keir Fraser
2012-07-14 4:54 ` Keir Fraser
2012-07-15 16:06 ` Olaf Hering
2012-07-15 16:06 ` Olaf Hering
2012-07-15 17:17 ` Keir Fraser
2012-07-15 17:17 ` Keir Fraser
2012-07-15 17:17 ` Keir Fraser
2012-07-16 15:46 ` Konrad Rzeszutek Wilk
2012-07-16 15:46 ` Konrad Rzeszutek Wilk
2012-07-17 10:24 ` Olaf Hering
2012-07-17 10:24 ` Olaf Hering
2012-07-17 12:34 ` Olaf Hering
2012-07-17 12:34 ` Olaf Hering
2012-07-06 15:54 ` Daniel Kiper
2012-07-06 15:54 ` Daniel Kiper
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=4FF6BDFB020000780008DFEF@nat28.tlf.novell.com \
--to=jbeulich@suse.com \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olaf@aepfle.de \
--cc=xen-devel@lists.xensource.com \
/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.