From owner-freebsd-current Thu Aug 22 2:28:57 2002 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 97E0237B400; Thu, 22 Aug 2002 02:28:53 -0700 (PDT) Received: from freebsd.dk (cpe.atm2-0-56339.0x50c6aa0a.abnxx2.customer.tele.dk [80.198.170.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id B9FD643E75; Thu, 22 Aug 2002 02:28:52 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.12.5/8.12.5) id g7M9SlmZ081159; Thu, 22 Aug 2002 11:28:47 +0200 (CEST) (envelope-from sos) From: Soeren Schmidt Message-Id: <200208220928.g7M9SlmZ081159@freebsd.dk> Subject: Re: Memory corruption in CURRENT In-Reply-To: <20020822111650.I45839-100000@levais.imp.ch> To: Martin Blapp Date: Thu, 22 Aug 2002 11:28:47 +0200 (CEST) Cc: Don Lewis , marks@ripe.net, ktsin@acm.org, freebsd-current@FreeBSD.ORG, hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL98b (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=ISO-8859-1 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG It seems Martin Blapp wrote: > Hi Soeren, > > > However, this kind of problem in most cases spells bad HW to me, > > ie subspec RAM, poor powersupply, badly cooled CPU, overclocking etc etc... > > That's what I thought too. I have now three different systems which show > all this: > > 1) PIV 1,6Ghz, Intel B845DG Board, 1GB Kingston Ram, > 2) PIV 2Ghz Intel B845DG Board, 1GB Kingston ECC Ram > 3) PIV 2,26 Ghz Asus P4B533 Board with I845 chipset, 1GB noname Ram > > All running CURRENT. I also replaced in 1) and 2) the CPU, RAM. > It happens both on SCSI and ATA disks. Powersupply has been changed > for all 3 systems. Problem is still the same. > > The problem sometimes appears just after startup. CPU is still cold then. > Other times it builds 6 buildworlds sucessfully, and then suddenly I see > a SIG4. Hmm, thats probably a P4 problem then, I dont see it on any of my systems (P3 + K7) I dont have a P4 here (and newer will unless left at my doorstep), and I have no immediate ideas other than trying a MB that doesn't have a i845 chipset (the less Intel parts the better :) ) -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message