RE: 05e0caad3b7bd0d0fbeff980bca22f186241a501 breaks ia64 kdump

From: Zou, Nanhai <nanhai.zou_at_intel.com>
Date: 2006-11-02 21:38:54
> -----Original Message-----
> From: Horms [mailto:horms@verge.net.au]
> Sent: 2006ńÍ11‘¬2»’ 16:24
> To: Zou, Nanhai
> Cc: Mel Gorman; Andy Whitcroft; linux-ia64@vger.kernel.org; Linus Torvalds;
> Bob Picco; Andrew Morton; Dave Hansen; Andi Kleen; Benjamin Herrenschmidt; Paul
> Mackerras; Keith Mannthey; Luck, Tony; KAMEZAWA Hiroyuki; Yasunori Goto;
> Khalid Aziz
> Subject: Re: 05e0caad3b7bd0d0fbeff980bca22f186241a501 breaks ia64 kdump
> 
> On Thu, Nov 02, 2006 at 10:13:12AM +0800, Zou, Nanhai wrote:
> > Hi Neil,
> > 	Does the attached patch fix the issue?
> 
> I gave your patch a quick test. It does seem to make the problem go
> away, but it does not seem to be correct. It gives
> 
> early_node_map[1] active PFN ranges
>     0:        0 ->    32768
> (end of list)
> 
> But it really should be 16384 -> 32768
> 

Finally I've gotten some time to look detail into the problem.
It should be the filter_rsvd_memory in 
paging_init -> efi_memmap_walk(filter_rsvd_memory, count_node_pages)
filter out the kernel image and other rsvd regions in rsvd_regions...

It is strange we don't see the oops when booting the first kernel°£

efi_memmap_walk(filter_rsvd_memory, count_node_pages) looks questionable to me even without Mel's patch.
I will consider it more and provide patch to tomorrow.

Thanks
Zou Nan hai
-
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 Thu Nov 02 21:39:09 2006

This archive was generated by hypermail 2.1.8 : 2006-11-02 21:39:27 EST