> > This should have been fixed in memblock in recent kernel, at least I > > believe it is. It looks like this is caused by overlapping lmb_reserve() > > at boot (or lmb_reserve() overlapping an lmb_alloc'ated region which > > boils down to the same thing). > > > > Old lmb didn't deal with that well at all and that lead to corruption of > > the lmb list. We fixed that in > > > > 8f7a66051b7523108c5aefb08c6a637e54aedc47 > > > > mm/memblock: properly handle overlaps and fix error path > > > > Which got merged in 2.6.39. > > > > If you absolutely need to stick to 2.6.30, you can try backporting the > > fix to lmb. > > > > Cheers, > > Ben. > > > > I need to stick to 2.6.30, will try backporting the fix. Is this the same > thing > which is causing the wrong page (already allocated memory) allocation?
I can't say for sure but it looks like it could be. Cheers, Ben. _______________________________________________ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev