From owner-freebsd-questions@FreeBSD.ORG Wed Apr 2 11:29:09 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3AEA637B401 for ; Wed, 2 Apr 2003 11:29:09 -0800 (PST) Received: from ns.museum.rain.com (gw-ipinc.museum.rain.com [206.29.169.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1400A43F75 for ; Wed, 2 Apr 2003 11:29:08 -0800 (PST) (envelope-from list@museum.rain.com) Received: from ns.museum.rain.com (localhost [127.0.0.1]) by ns.museum.rain.com (8.12.8/8.12.8) with ESMTP id h32JT6gT016530 for ; Wed, 2 Apr 2003 11:29:06 -0800 (PST) (envelope-from list@ns.museum.rain.com) Received: (from list@localhost) by ns.museum.rain.com (8.12.8/8.12.8/Submit) id h32JT6lA016529 for freebsd-questions@freebsd.org; Wed, 2 Apr 2003 11:29:06 -0800 (PST) (envelope-from list) Date: Wed, 2 Apr 2003 11:29:06 -0800 From: James Long To: freebsd-questions@freebsd.org Message-ID: <20030402112906.A16512@ns.museum.rain.com> References: <20030401141454.N43325-100000@atlantis.atlantis.dp.ua> <20030401113952.GA34796@falcon.midgard.homeip.net> <20030402162618.GA530@blackman> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20030402162618.GA530@blackman>; from freebsd@blackman.unixtechs.org on Wed, Apr 02, 2003 at 11:26:19AM -0500 X-Spam-Status: No, hits=-3.0 required=5.0 tests=IN_REP_TO,QUOTED_EMAIL_TEXT,REFERENCES,SPAM_PHRASE_00_01, USER_AGENT,USER_AGENT_MUTT version=2.43 Subject: Re: Fatal trap after adding more memory X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: james_mapson@museum.rain.com List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Apr 2003 19:29:09 -0000 On Wed, Apr 02, 2003 at 11:26:19AM -0500, Eric Ekong wrote: > > I added memory to my machine yesterday and since then I have noticed > Fatal traps when I try to do some intensive activity on the machine. > IE. make buildworld That's a classic sign of faulty memory. I had the same thing when I bought four pieces of 256M ECC RAM. I had two parts each built from NEC and Samsung chips. Much as I have liked Samsung in the past, any time I had any piece of the Samsung memory installed, no matter which slot, a buildworld running while doing some heavy tar compress/decom- press operations would cause a fatal trap. Run the NEC memory alone, no problems. Run either or both of the Samsung pieces alone, problems. Remove the newly-added memory and ensure that the problems goes away. If so, try using JUST the new memory alone, either one piece at a time, or all at once, and see whether the problem occurs only when the new memory is used. If so, return the memory for a different make or better quality.