From owner-freebsd-ppc@FreeBSD.ORG Mon Oct 6 20:54:55 2008 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A4BB0106568F; Mon, 6 Oct 2008 20:54:55 +0000 (UTC) (envelope-from andreast-list@fgznet.ch) Received: from smtp.fgznet.ch (mail.fgznet.ch [81.92.96.47]) by mx1.freebsd.org (Postfix) with ESMTP id 3E6928FC16; Mon, 6 Oct 2008 20:54:54 +0000 (UTC) (envelope-from andreast-list@fgznet.ch) Received: from wolfram.andreas.nets ([91.190.8.131]) by smtp.fgznet.ch (8.13.8/8.13.8/Submit_SMTPAUTH) with ESMTP id m96Kspn7028759; Mon, 6 Oct 2008 22:54:52 +0200 (CEST) (envelope-from andreast-list@fgznet.ch) Message-ID: <48EA7B1B.9050006@fgznet.ch> Date: Mon, 06 Oct 2008 22:54:51 +0200 From: Andreas Tobler User-Agent: Thunderbird 2.0.0.17 (Macintosh/20080914) MIME-Version: 1.0 To: Peter Grehan References: <20081007063857.EJV27136@dommail.onthenet.com.au> In-Reply-To: <20081007063857.EJV27136@dommail.onthenet.com.au> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.64 on 81.92.96.47 Cc: freebsd-ppc@freebsd.org Subject: Re: physical memory limit? X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Oct 2008 20:54:55 -0000 Hi Peter, Peter Grehan wrote: >> is there an upper physical memory size limitation on ppc? > > For an AIM system (G3/4/5) which is essentially Apple h/w, > it's 2GB since Apple like to memory-map i/o above that. Fortunately I have no more slots to fill :) >> I play on a G3 imac with 1GB memory. On CURRENT. I often >> get SIGSEGV and a rebuild on that component succeeds. >> So, for me it seems strange. I'll change some DIMM's and >> see how far I get. > > I've not had that much RAM in a G3, but certainly have had > 1GB in a number of G4's without problems. I'm guessing it's a > VM bug rather than bad memory. Was the component you were > building using a lot of VM ? (e.g. KDE) I remember back in 05 we had a similar issue when I tried 'buildworld' on a G4 alu book. Then you suggested to me to reduce hw.physmem to 512MB. Right now the failing parts are sporadic, during buildworld or buildkernel. For example, kerberos5 or openssl. Also nfs in buildkernel. You see somehow not predictable. A run over the failing part solves the 11. I'll reduce/replace the memory and see how it behaves. Thanks, Andreas