Re: 05e0caad3b7bd0d0fbeff980bca22f186241a501 breaks ia64 kdump

From: Horms <horms_at_verge.net.au>
Date: 2006-10-30 20:11:26
On Fri, Oct 27, 2006 at 10:15:16AM +0100, Andy Whitcroft wrote:
> Hi,
> 
> Mel and I spent a bit more time thinking about this.  If the efi map is
> being modified such that the kernel area becomes loader data that may
> well move up the start of conventional memory as far as the running
> kernel is concerned.
> 
> [Apologies in advance if Zou is not an appropriate name.]
> 
> It would be helpful both to have a dump of the efi map and the start
> address of the kernel from the affected machine (Horms) and if possible
> the efi map and start address of the kernel from your working test
> platform (Zou).  Also, if we could get the boot logs from a conventional
> kernel and the kexec kernel from the working test platform (Zou).

Below is a log of 05e0caad3b7bd0d0fbeff980bca22f186241a501 + kexec.
It shows the initial successful boot and kdump with oopses. I enabled
EFI_DEBUG which prints out the efi map. And just before that
I added some code to print out the value of _start. If this is not
what you need please let me know.

I can also produce logs for 05e0caad3b7bd0d0fbeff980bca22f186241a501
without kexec, or with 05e0caad3b7bd0d0fbeff980bca22f186241a501 reversed
if you like.

> A logical next step might be to bodge things such that we offer up the
> kernel image as an active range and see if that sorts out the alignment
> issue we are seeing, this will allow us to be certain it is the kernel
> image in this area.  Something like the following inserted into
> register_memory() might work:
> 
> 	add_active_range(0, code_resource.start >> PAGE_SHIFT,
> 			    data_resource.end >> PAGE_SHIFT);
> 
> Not sure this is the right thing as a fix, but would help confirm the
> theory.

I will poke around with that. Though it will probably be tomorrow.

-- 
Horms
  H: http://www.vergenet.net/~horms/
  W: http://www.valinux.co.jp/en/

-
To unsubscribe from this list: send the line "unsubscribe linux-ia64" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Received on Mon Oct 30 20:14:15 2006

This archive was generated by hypermail 2.1.8 : 2006-10-30 20:14:33 EST