From owner-freebsd-stable@FreeBSD.ORG Sun Oct 7 10:20:43 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 DD9EB16A421 for ; Sun, 7 Oct 2007 10:20:43 +0000 (UTC) (envelope-from eugen@www.svzserv.kemerovo.su) Received: from www.svzserv.kemerovo.su (www.svzserv.kemerovo.su [213.184.65.80]) by mx1.freebsd.org (Postfix) with ESMTP id 45C9C13C457 for ; Sun, 7 Oct 2007 10:20:42 +0000 (UTC) (envelope-from eugen@www.svzserv.kemerovo.su) Received: from www.svzserv.kemerovo.su (eugen@localhost [127.0.0.1]) by www.svzserv.kemerovo.su (8.13.8/8.13.8) with ESMTP id l97AKflR009600; Sun, 7 Oct 2007 18:20:41 +0800 (KRAST) (envelope-from eugen@www.svzserv.kemerovo.su) Received: (from eugen@localhost) by www.svzserv.kemerovo.su (8.13.8/8.13.8/Submit) id l97AKfob009599; Sun, 7 Oct 2007 18:20:41 +0800 (KRAST) (envelope-from eugen) Date: Sun, 7 Oct 2007 18:20:41 +0800 From: Eugene Grosbein To: Per olof Ljungmark , freebsd-stable@freebsd.org Message-ID: <20071007102041.GB8676@svzserv.kemerovo.su> References: <4708A05C.4090001@intersonic.se> <20071007094011.GA77602@slackbox.xs4all.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20071007094011.GA77602@slackbox.xs4all.nl> User-Agent: Mutt/1.4.2.3i Cc: 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 10:20:44 -0000 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 Eugene Grosbein