From owner-freebsd-sparc64@FreeBSD.ORG Mon Mar 14 18:47:17 2005 Return-Path: Delivered-To: freebsd-sparc64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4E5AA16A4CE for ; Mon, 14 Mar 2005 18:47:17 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.204]) by mx1.FreeBSD.org (Postfix) with ESMTP id E042C43D39 for ; Mon, 14 Mar 2005 18:47:16 +0000 (GMT) (envelope-from hengchai@gmail.com) Received: by wproxy.gmail.com with SMTP id 70so1796925wra for ; Mon, 14 Mar 2005 10:47:16 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=nBVAYV0WWdjSo6aQWMncY8bCRxPG6Kyn1mBI5dj4FXofvp0pjppPUi+wR1gfNYd5UbRFXFb8QdqzqMNIE1tEpWvjJw8wKqhiVl75rSQFEfmSTd9ciuKqHRwP/md+ExmhRZwtG9jml0klybKBXBnj63HDnWL4WiLNI2KZVt/tVAE= Received: by 10.54.40.2 with SMTP id n2mr4847270wrn; Mon, 14 Mar 2005 10:47:12 -0800 (PST) Received: by 10.54.23.37 with HTTP; Mon, 14 Mar 2005 10:47:11 -0800 (PST) Message-ID: Date: Tue, 15 Mar 2005 02:47:11 +0800 From: Tan Heng Chai To: Kris Kennaway In-Reply-To: <20050314181421.GM91771@hub.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <423302DD.60609@fsn.hu> <20050314181421.GM91771@hub.freebsd.org> cc: sparc64@freebsd.org Subject: Re: E4000 on FreeBSD 5.3 X-BeenThere: freebsd-sparc64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Tan Heng Chai List-Id: Porting FreeBSD to the Sparc List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Mar 2005 18:47:17 -0000 It happened previous when I just installed the new CPU boards. Reseating the ram fixed it though, so its probably badly seated rams. I ran the system with 6400MB no problems. But I tested with 7424MB and it refused to boot, hung before it displayed the "avail memory" section. On Mon, 14 Mar 2005 18:14:21 +0000, Kris Kennaway wrote: > On Sun, Mar 13, 2005 at 01:17:57AM +0800, Tan Heng Chai wrote: > > As requested, dmesg for my E4000. Note that the ram isn't 6400MB as > > apparently there was a ram test failure just as I rebooted earlier. > > Will try to post another full one later. > > That's pretty suspicious and makes me think that there are further RAM > errors not being caught by the self-test. Try swapping out the RAM to > identify the bad subset. > > I know that the E4500 runs with 5GB of RAM with no problems. > > Kris >