On Wed, Mar 30, 2005 at 10:42:35AM -0800, Mike Kravetz wrote: > > Hopefully, others can use this info and help track down the > root cause. Most likely, this is a ppc64 specific problem. > But, previously I did find a memmap_init bug (arch independent) > that was only found via the ppc64 code. > Forgot to mention that this only happens with the SPARSEMEM model. Or, at least that was the case with 2.6.11-mhp2. I assume it is still true with the latest patch set. -- Mike
