Re: 05e0caad3b7bd0d0fbeff980bca22f186241a501 breaks ia64 kdump
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- To: "Zou, Nanhai" <nanhai.zou@xxxxxxxxx>
- Subject: Re: 05e0caad3b7bd0d0fbeff980bca22f186241a501 breaks ia64 kdump
- From: Horms <horms@xxxxxxxxxxxx>
- Date: Thu, 2 Nov 2006 17:24:25 +0900
- Cc: Mel Gorman <mel@xxxxxxxxx>, Andy Whitcroft <apw@xxxxxxxxxxxx>, linux-ia64@xxxxxxxxxxxxxxx, Linus Torvalds <torvalds@xxxxxxxxxxx>, Bob Picco <bob.picco@xxxxxx>, Andrew Morton <akpm@xxxxxxxx>, Dave Hansen <haveblue@xxxxxxxxxx>, Andi Kleen <ak@xxxxxx>, Benjamin Herrenschmidt <benh@xxxxxxxxxxxxxxxxxxx>, Paul Mackerras <paulus@xxxxxxxxx>, Keith Mannthey <kmannth@xxxxxxxxx>, "Luck, Tony" <tony.luck@xxxxxxxxx>, KAMEZAWA Hiroyuki <kamezawa.hiroyu@xxxxxxxxxxxxxx>, Yasunori Goto <y-goto@xxxxxxxxxxxxxx>, Khalid Aziz <khalid_aziz@xxxxxx>
- In-reply-to: <10EA09EFD8728347A513008B6B0DA77A086B0C@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
- References: <10EA09EFD8728347A513008B6B0DA77A086B0C@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
- User-agent: mutt-ng/devel-r804 (Debian)
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
--
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@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
[Index of Archives]
[Linux Kernel]
[Sparc Linux]
[DCCP]
[Linux ARM]
[Yosemite News]
[Linux SCSI]
[Linux x86_64]
[Linux for Ham Radio]
