From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932337Ab2GFJVp (ORCPT ); Fri, 6 Jul 2012 05:21:45 -0400 Received: from nat28.tlf.novell.com ([130.57.49.28]:51101 "EHLO nat28.tlf.novell.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755599Ab2GFJVP convert rfc822-to-8bit (ORCPT ); Fri, 6 Jul 2012 05:21:15 -0400 Message-Id: <4FF6BDFB020000780008DFEF@nat28.tlf.novell.com> X-Mailer: Novell GroupWise Internet Agent 12.0.0 Date: Fri, 06 Jul 2012 09:29:15 +0100 From: "Jan Beulich" To: "Olaf Hering" Cc: , , Subject: Re: [Xen-devel] incorrect layout of globals from head_64.S during kexec boot References: <20120705210607.GA26908@aepfle.de> In-Reply-To: <20120705210607.GA26908@aepfle.de> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 8BIT Content-Disposition: inline Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org >>> On 05.07.12 at 23:06, Olaf Hering 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 From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Jan Beulich" Subject: Re: [Xen-devel] incorrect layout of globals from head_64.S during kexec boot Date: Fri, 06 Jul 2012 09:29:15 +0100 Message-ID: <4FF6BDFB020000780008DFEF@nat28.tlf.novell.com> References: <20120705210607.GA26908@aepfle.de> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20120705210607.GA26908-QOLJcTWqO2uzQB+pC5nmwQ@public.gmane.org> Content-Disposition: inline List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: kexec-bounces-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org Errors-To: kexec-bounces+glkk-kexec=m.gmane.org-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org To: Olaf Hering Cc: xen-devel-GuqFBffKawuULHF6PoxzQEEOCMrvLtNR@public.gmane.org, kexec-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org, linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-Id: xen-devel@lists.xenproject.org >>> On 05.07.12 at 23:06, Olaf Hering 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 From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from nat28.tlf.novell.com ([130.57.49.28]) by merlin.infradead.org with esmtp (Exim 4.76 #1 (Red Hat Linux)) id 1Sn3xn-0000At-CP for kexec@lists.infradead.org; Fri, 06 Jul 2012 08:32:32 +0000 Message-Id: <4FF6BDFB020000780008DFEF@nat28.tlf.novell.com> Date: Fri, 06 Jul 2012 09:29:15 +0100 From: "Jan Beulich" Subject: Re: [Xen-devel] incorrect layout of globals from head_64.S during kexec boot References: <20120705210607.GA26908@aepfle.de> In-Reply-To: <20120705210607.GA26908@aepfle.de> Mime-Version: 1.0 Content-Disposition: inline List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: kexec-bounces@lists.infradead.org Errors-To: kexec-bounces+dwmw2=infradead.org@lists.infradead.org To: Olaf Hering Cc: xen-devel@lists.xensource.com, kexec@lists.infradead.org, linux-kernel@vger.kernel.org >>> On 05.07.12 at 23:06, Olaf Hering 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