From owner-freebsd-ppc@FreeBSD.ORG Sat Jun 27 06:34:57 2009 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 1260E106564A for ; Sat, 27 Jun 2009 06:34:57 +0000 (UTC) (envelope-from bruce@cran.org.uk) Received: from muon.cran.org.uk (muon.cran.org.uk [66.246.138.153]) by mx1.freebsd.org (Postfix) with ESMTP id DF4068FC13 for ; Sat, 27 Jun 2009 06:34:56 +0000 (UTC) (envelope-from bruce@cran.org.uk) Received: from gluon.draftnet (87-194-158-129.bethere.co.uk [87.194.158.129]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by muon.cran.org.uk (Postfix) with ESMTPSA id 3DE8E8AF1 for ; Sat, 27 Jun 2009 06:17:23 +0000 (UTC) Date: Sat, 27 Jun 2009 07:17:10 +0100 From: Bruce Cran To: freebsd-ppc@freebsd.org Message-ID: <20090627071710.36c4d2a0@gluon.draftnet> X-Mailer: Claws Mail 3.7.1 (GTK+ 2.16.2; i386-portbld-freebsd7.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: iBook G4 chipset failure causing segfaults? 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: Sat, 27 Jun 2009 06:34:57 -0000 I've recently found that my G4 iBook is causing programs to segfault when they start going into swap: the effect is worse on -current but I'm also seeing it on 7.2. For example, if I run a program to allocate 500MB the system will swap out most programs since I only have 512MB RAM. After a while dhclient and sendmail segfault while the test program keeps running; I've also seen tcsh and login segfault too as I logout. I originally found the problem when building clangbsd, where 'as' would segfault when it started building the large C++ files that come with clang. I can run a normal buildworld so I guess this is more of a problem with the chipset (caused by swapping?) than a memory problem? I've run the Apple Hardware Test utility over 30 loops without any errors - has anyone else seen this problem, and is it likely that the hardware is simply starting to fail? -- Bruce Cran