I'm running 2.6.10 on a ppc64 machine with 4GB of memory.
We're debugging an issue and would like to try and see if disabling the
U3 DART makes the problem go away. Unfortunately, this particular blade
is unstable if not all the memory banks are populated.
After some frustration I looked at the code and realized that the "mem="
functionality is not supported for ppc64 on this particular kernel.
Can anyone give me some advice on the simplest way to limit this thing
to under 2GB of memory so that the DART is not allocated/used?
Does anyone know when support for "mem=" was added? I know it is there
in the current git version, but the "powerpc" consolidation means
everything is all different now.
Thanks,
Chris
On Sat, 4 Feb 2006 10:21, Christopher Friesen wrote:
> I'm running 2.6.10 on a ppc64 machine with 4GB of memory.
>
> We're debugging an issue and would like to try and see if disabling the
> U3 DART makes the problem go away. Unfortunately, this particular blade
> is unstable if not all the memory banks are populated.
>
> After some frustration I looked at the code and realized that the "mem="
> functionality is not supported for ppc64 on this particular kernel.
>
> Can anyone give me some advice on the simplest way to limit this thing
> to under 2GB of memory so that the DART is not allocated/used?
>
> Does anyone know when support for "mem=" was added? I know it is there
> in the current git version, but the "powerpc" consolidation means
> everything is all different now.
From memory (harhar) the mem= support was merged in 2.6.11, so the original
patch should _probably_ apply on a vanilla 2.6.10 tree, try it:
http://patchwork.ozlabs.org/linuxppc64/patch?id=724
cheers
--
Michael Ellerman
IBM OzLabs
email: michael:ellerman.id.au
inmsg: mpe:jabber.org
wwweb: http://michael.ellerman.id.au
phone: +61 2 6212 1183 (tie line 70 21183)
We do not inherit the earth from our ancestors,
we borrow it from our children. - S.M.A.R.T Person