From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Subject: Re: "boot: mem=1024M" causes only one CPU is brought up in 2.6.17-mm4 From: Michael Ellerman To: Raid Cheng In-Reply-To: References: Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-gfi45qIPT7NuI+Wcmcuc" Date: Fri, 30 Jun 2006 17:51:20 +1000 Message-Id: <1151653880.11247.2.camel@localhost.localdomain> Mime-Version: 1.0 Cc: linuxppc-dev@ozlabs.org Reply-To: michael@ellerman.id.au List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , --=-gfi45qIPT7NuI+Wcmcuc Content-Type: text/plain Content-Transfer-Encoding: quoted-printable 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. >=20 > But if i boot the kernel without such "mem=3D1024M" limitation, all 8 CP= Us > will be show in /proc/cpuinfo Oops, must be a bug in my "cleaned up" mem=3Dx handling. Can you send me your System.map, and a tar.gz of /proc/device-tree for a working kernel and also the mem=3D1024M kernel? cheers --=20 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 --=-gfi45qIPT7NuI+Wcmcuc Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (GNU/Linux) iD8DBQBEpNf4dSjSd0sB4dIRAp5rAKDC50D2h+nfWf6Jrb4yRMQdzgVQdACfRt1c YgGgTsUlYlJWodcXVAQpDNM= =brSw -----END PGP SIGNATURE----- --=-gfi45qIPT7NuI+Wcmcuc--