From owner-freebsd-sparc64@FreeBSD.ORG  Wed Jan  5 12:38:49 2005
Return-Path: <owner-freebsd-sparc64@FreeBSD.ORG>
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 DB38F16A4CE
	for <freebsd-sparc@freebsd.org>; Wed,  5 Jan 2005 12:38:49 +0000 (GMT)
Received: from web17308.mail.tpe.yahoo.com (web17308.mail.tpe.yahoo.com
	[202.43.200.129])
	by mx1.FreeBSD.org (Postfix) with SMTP id 2FB3643D39
	for <freebsd-sparc@freebsd.org>;
	Wed,  5 Jan 2005 12:38:49 +0000 (GMT)
	(envelope-from cuma1207@yahoo.com.tw)
Message-ID: <20050105123847.41645.qmail@web17308.mail.tpe.yahoo.com>
Received: from [220.135.204.56] by web17308.mail.tpe.yahoo.com via HTTP;
	Wed, 05 Jan 2005 20:38:47 CST
Date: Wed, 5 Jan 2005 20:38:47 +0800 (CST)
From: cuma1207 <cuma1207@yahoo.com.tw>
To: Kris Kennaway <kris@obsecurity.org>
In-Reply-To: <20050104222258.GB79661@xor.obsecurity.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=big5
Content-Transfer-Encoding: 8bit
cc: freebsd-sparc@freebsd.org
Subject: Re: Fast Data Access MMU Miss problem
X-BeenThere: freebsd-sparc64@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Porting FreeBSD to the Sparc <freebsd-sparc64.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-sparc64>,
	<mailto:freebsd-sparc64-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-sparc64>
List-Post: <mailto:freebsd-sparc64@freebsd.org>
List-Help: <mailto:freebsd-sparc64-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-sparc64>,
	<mailto:freebsd-sparc64-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Jan 2005 12:38:50 -0000

 --- Kris Kennaway <kris@obsecurity.org> 的訊息：
> On Tue, Jan 04, 2005 at 10:35:25AM -1000, David
> Cornejo wrote:
> > I am getting this error quite often on my Ultra60.
>  I can get it to boot, 
> > but quite often portupgrade (not implying it's
> causing it, just that it's a 
> > good way for me to make it happen) when run will
> kill the machine.
> 
> 'fast data access mmu miss' is a fairly generic
> panic, so the causes
> are likely be to disparate.  Yours makes me a bit
> suspicious of
> hardware failure, but you should get a debugging
> traceback (see
> developers' handbook) if you want someone to take a
> closer look.
> 

In my case , it happened on the bootrap when trying to
boot from the HD(it never boot success from the HD
after I finished the instalation), is there kernel
crash dump in such situation?

thanks


_______________________________________________________________________
Yahoo!奇摩電子信箱
250MB 超大免費信箱，信件再多也不怕！
http://mail.yahoo.com.tw/