From owner-freebsd-alpha Mon Dec 9 6: 4:14 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 914EB37B401 for ; Mon, 9 Dec 2002 06:04:13 -0800 (PST) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id C151E43EB2 for ; Mon, 9 Dec 2002 06:04:12 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id JAA19772; Mon, 9 Dec 2002 09:04:07 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.6/8.9.1) id gB9E3bN02684; Mon, 9 Dec 2002 09:03:37 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15860.41656.977291.824250@grasshopper.cs.duke.edu> Date: Mon, 9 Dec 2002 09:03:36 -0500 (EST) To: Jan Lentfer Cc: freebsd-alpha@freebsd.org Subject: Re: Memory Problems In-Reply-To: <1039419132.571.2.camel@jan-linnb.lan> References: <20021206083651.C66664-100000@dove.penix.org> <1039183724.3df0af6cec2b7@www-mail.floundjan.homeip.net> <1039189222.3df0c4e62256c@www-mail.floundjan.homeip.net> <15856.50726.647449.10642@grasshopper.cs.duke.edu> <1039419132.571.2.camel@jan-linnb.lan> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Jan Lentfer writes: > > > Maybe linux puts its memory in a different place and you'll get > > screwed later rather than sooner. We have no problems with 1GB or > > less of *good* memory on a miata. Sorry. > > You are rigth. With this chips in Linux kernel panics when filling up > the memory :-( > So from your experience, what would you say? Are the chips broken or is > this an incompatibility problem, like everythings works - just not > together? Sorry, I really don't know. I've only ever tinkered with miata memory 5 years ago when miatas were new, and memory cost real money. We used DataRam memory exclusively. We never had a problem. We ran some machines up to a Gig, and I don't remember having to fool around re-ordering memory, but it was years ago now.. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message