From owner-freebsd-current@FreeBSD.ORG Tue Jun 22 07:45:56 2004 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 2E96416A4CF for ; Tue, 22 Jun 2004 07:45:56 +0000 (GMT) Received: from mail002.syd.optusnet.com.au (mail002.syd.optusnet.com.au [211.29.132.32]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1A4B443D41 for ; Tue, 22 Jun 2004 07:45:55 +0000 (GMT) (envelope-from PeterJeremy@optushome.com.au) Received: from cirb503493.alcatel.com.au (c211-30-75-229.belrs2.nsw.optusnet.com.au [211.30.75.229]) i5M7jUJ21234; Tue, 22 Jun 2004 17:45:32 +1000 Received: from cirb503493.alcatel.com.au (localhost.alcatel.com.au [127.0.0.1])i5M7jTVd053665; Tue, 22 Jun 2004 17:45:30 +1000 (EST) (envelope-from pjeremy@cirb503493.alcatel.com.au) Received: (from pjeremy@localhost)i5M7jSlJ053664; Tue, 22 Jun 2004 17:45:28 +1000 (EST) (envelope-from pjeremy) Date: Tue, 22 Jun 2004 17:45:28 +1000 From: Peter Jeremy To: Gordon Bergling Message-ID: <20040622074528.GP1596@cirb503493.alcatel.com.au> References: <20040621145538.GA968@nemesis.md.0xfce3.net> <20040621193259.GA673@nemesis.md.0xfce3.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040621193259.GA673@nemesis.md.0xfce3.net> User-Agent: Mutt/1.4.2i cc: current@freebsd.org Subject: Re: new motherboard - fsck_ufs died with signal 8 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: Tue, 22 Jun 2004 07:45:56 -0000 On Mon, 2004-Jun-21 21:32:59 +0200, Gordon Bergling wrote: >It tried many times to get in complete build for an GENERIC based kernel >config, but I didn't get _one_ successfully build. Every build breaks on >a different position of the build process. Mostly asm-erros or gcc core >dumps. The strange thing is that the build of GENERIC runs successful. This smells very much like a hardware problem - buildworld and buildkernel have proven to be excellent system stress tests over time. Make sure the CPU & system cooling and power supply is up to scratch - it's not clear how much of your system is new but your old PSU might be a bit stressed running your new XP. >I had run memtest about 20 times and it didn't find any errors, so I >think the RAM should be okay. (I presume this is Memtest86 from www.memtest86.com). Whilst in-situ memory tests will pick up a stuck bit or badly out-of-tolerance memory, they are far less reliable at detecting marginal memory or pattern sensitivities. Can you exchange the DIMM or (temporarily) swap it with a known good one? Have you tried under-clocking your system or using less aggressive RAM timings? If that makes it stable, it's a fairly clear indication that your system is marginal. -- Peter Jeremy