From owner-freebsd-stable@FreeBSD.ORG Sun Oct 7 16:09:00 2007 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 66FD416A418 for ; Sun, 7 Oct 2007 16:09:00 +0000 (UTC) (envelope-from peo@intersonic.se) Received: from neonpark.inter-sonic.com (neonpark.inter-sonic.com [212.247.8.98]) by mx1.freebsd.org (Postfix) with ESMTP id 2EC6813C461 for ; Sun, 7 Oct 2007 16:09:00 +0000 (UTC) (envelope-from peo@intersonic.se) X-Virus-Scanned: amavisd-new at inter-sonic.com Message-ID: <4709048F.4050009@intersonic.se> Date: Sun, 07 Oct 2007 18:08:47 +0200 From: Per olof Ljungmark Organization: Intersonic AB User-Agent: Thunderbird 2.0.0.6 (X11/20070814) MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <4708A05C.4090001@intersonic.se> <20071007094011.GA77602@slackbox.xs4all.nl> <20071007102041.GB8676@svzserv.kemerovo.su> In-Reply-To: <20071007102041.GB8676@svzserv.kemerovo.su> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: buildworld failures on STABLE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Oct 2007 16:09:00 -0000 Eugene Grosbein wrote: > On Sun, Oct 07, 2007 at 11:40:11AM +0200, Roland Smith wrote: > >>> On a remote machine currently with RELENG-6 from 20th. June, with STABLE >>> sources from this morning I get build failures in contrib/ similar to: >> >>> /usr/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/lcm.c:801: internal >>> compiler error: Segmentation fault: 11 >> >>> Would this indicate a hardware (memory) problem? >> Yes. The compiler dying with signal 11 is a typical memory problem. >> >>> Any way to test remotely? >> There are memory test applications like memtest86+ (http://www.memtest.org/). >> You have to boot from it, but it does support a console on a serial port. > > There is also ports/sysutils/memtest that may be run from multiuser > if one manages to build it with broken memory :-) > Or it's possible to install a package. > > One problem with running such application with OS loaded is that > kernel places strict limit to amount of memory that user-level application > may lock. There is a PR with a patch that allows to raise the limit > so memtest could test most part of free memory: > > http://www.FreeBSD.org/cgi/query-pr.cgi?pr=kern/114654 Thanks for the memtest advice, I ran it and memory is definitely hosed. Sigh, that means 400 kilometers of travel... Per olof