"boot: mem=1024M" causes only one CPU is brought up in 2.6.17-mm4

[Michael Ellerman]

On Fri, 2006-06-30 at 15:05 +0800, Raid Cheng wrote:
> I installed latest mm kernel 2.6.17-mm4 on ppc64 with RHEL4-U3.
> When i tried to limit the memory to 1024M by modifying yaboot.conf or
> typing on the boot line, I found some error messages in dmesg log
> and only one CPU is brought up by checking /proc/cpuinfo.
> 
>  But if i boot the kernel without such "mem=1024M" limitation, all 8 CPUs
>  will be show in /proc/cpuinfo

Oops, must be a bug in my "cleaned up" mem=x handling. Can you send me
your System.map, and a tar.gz of /proc/device-tree for a working kernel
and also the mem=1024M kernel?

cheers

-- 
Michael Ellerman
IBM OzLabs

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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 191 bytes
Desc: This is a digitally signed message part
URL: <http://lists.ozlabs.org/pipermail/linuxppc-dev/attachments/20060630/ca5656f0/attachment.pgp>