From owner-freebsd-current@FreeBSD.ORG Mon Sep 22 10:13:32 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CE96216A4B3 for ; Mon, 22 Sep 2003 10:13:32 -0700 (PDT) Received: from freebie.xs4all.nl (freebie.xs4all.nl [213.84.32.253]) by mx1.FreeBSD.org (Postfix) with ESMTP id ECDAC43FEA for ; Mon, 22 Sep 2003 10:13:23 -0700 (PDT) (envelope-from wkb@freebie.xs4all.nl) Received: from freebie.xs4all.nl (localhost [127.0.0.1]) by freebie.xs4all.nl (8.12.9/8.12.9) with ESMTP id h8MHBFJt045570; Mon, 22 Sep 2003 19:11:15 +0200 (CEST) (envelope-from wkb@freebie.xs4all.nl) Received: (from wkb@localhost) by freebie.xs4all.nl (8.12.9/8.12.9/Submit) id h8MHBFHr045569; Mon, 22 Sep 2003 19:11:15 +0200 (CEST) (envelope-from wkb) Date: Mon, 22 Sep 2003 19:11:15 +0200 From: Wilko Bulte To: Holger Kipp Message-ID: <20030922171115.GB45499@freebie.xs4all.nl> References: <200309221425.h8MEPWY68417@alogis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200309221425.h8MEPWY68417@alogis.com> User-Agent: Mutt/1.4.1i X-OS: FreeBSD 4.9-PRERELEASE X-PGP: finger wilko@freebsd.org cc: jsmith@drexel.edu cc: freebsd-current@freebsd.org Subject: Re: Gcc 3.2.2 vs gcc 3.2.3 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Sep 2003 17:13:32 -0000 On Mon, Sep 22, 2003 at 02:25:27PM +0000, Holger Kipp wrote: > > > Justin Smith (jsmith@drexel.edu) wrote: > >I'm running a P4 2.4 Ghz processor with 512meg of ram. > > > >I've had the problem of getting signal 11 and signal 4 when I make > >buildworld and buildkernel. > > > >I tested my system with memtest86 (for several hours) and it says > >everything is OK. > > We had similar problems once. It turned out to be a 'lucky' combination of good > mainboard and good memory that were slightly incompatible. > > memtest86 might not detect this, but make buildworld will. If you don't get the > errors at the same location every time, it might be the same issue. We found > out after contacting both the mainboard and the memory chip vendors. Same experience here, also on P4, with DDR400 memory. Asus mainboard, with memory from the Asus qualified memory list. Did not work worth sh*, at least not with memory at DDR400 speeds. Other memory fixed is perfectly. Go figure.. -- Wilko wkb@freebie.xs4all.nl