From owner-freebsd-sparc64@FreeBSD.ORG Tue Jan 4 22:22:37 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 CD1B016A4D1 for ; Tue, 4 Jan 2005 22:22:37 +0000 (GMT) Received: from obsecurity.dyndns.org (CPE0050040655c8-CM00111ae02aac.cpe.net.cable.rogers.com [69.199.47.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9D73E43D39 for ; Tue, 4 Jan 2005 22:22:37 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 04E2451354; Tue, 4 Jan 2005 14:22:58 -0800 (PST) Date: Tue, 4 Jan 2005 14:22:58 -0800 From: Kris Kennaway To: David Cornejo Message-ID: <20050104222258.GB79661@xor.obsecurity.org> References: <20050103104025.A6665@carver.gumbysoft.com> <20050104014112.23160.qmail@web17309.mail.tpe.yahoo.com> <6.2.0.14.2.20050104102555.049faa18@white.dogwood.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="s/l3CgOIzMHHjg/5" Content-Disposition: inline In-Reply-To: <6.2.0.14.2.20050104102555.049faa18@white.dogwood.com> User-Agent: Mutt/1.4.2.1i 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Jan 2005 22:22:37 -0000 --s/l3CgOIzMHHjg/5 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable 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,= =20 > but quite often portupgrade (not implying it's causing it, just that it's= a=20 > 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. Kris --s/l3CgOIzMHHjg/5 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFB2xdCWry0BWjoQKURAhV4AKDT8PbUHsf1jeXeRqEUs9c7EnSbBACgsZHA vpXhQ5Q3sW9R0E4ZBuE4FL8= =+MvP -----END PGP SIGNATURE----- --s/l3CgOIzMHHjg/5--