From owner-freebsd-sparc64@FreeBSD.ORG  Mon Apr 11 08:24:06 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 114F216A4CE; Mon, 11 Apr 2005 08:24:06 +0000 (GMT)
Received: from obsecurity.dyndns.org
	(CPE0050040655c8-CM00111ae02aac.cpe.net.cable.rogers.com [69.194.102.111])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 2841C43D48; Mon, 11 Apr 2005 08:24:05 +0000 (GMT)
	(envelope-from kris@obsecurity.org)
Received: by obsecurity.dyndns.org (Postfix, from userid 1000)
	id 685CD530E0; Mon, 11 Apr 2005 01:24:02 -0700 (PDT)
Date: Mon, 11 Apr 2005 01:24:02 -0700
From: Kris Kennaway <kris@obsecurity.org>
To: sparc64@FreeBSD.org
Message-ID: <20050411082402.GA97880@xor.obsecurity.org>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="C7zPtVaVf+AK4Oqc"
Content-Disposition: inline
User-Agent: Mutt/1.4.2.1i
cc: marius@FreeBSD.org
Subject: 'panic: trap: memory address not aligned' in 5.4
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: Mon, 11 Apr 2005 08:24:06 -0000


--C7zPtVaVf+AK4Oqc
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

I got this shortly after updating an e450 to 5.4-rc2 (from RELENG_5 of
about 6 weeks ago) and applying marius' clock patch.

panic: tpanic: trap: memory address not aligned
cpuid = -1072483876
KDB: enter: panic
spin lock sched lock held by 0xc0040fb0 for > 5 seconds
panic: trap: fast data access mmu miss
cpuid = 0
KDB: enter: panic

i.e. both CPUs panicked simultaneously.  It hung there, so I can't get
any further debugging.

Kris


--C7zPtVaVf+AK4Oqc
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (FreeBSD)

iD8DBQFCWjQhWry0BWjoQKURAv9YAJ4xqEM1eOIirSeBTpH9fVZSp7lPJQCdHmws
LwOZx69DkJd87aa6UhHVFak=
=tOtj
-----END PGP SIGNATURE-----

--C7zPtVaVf+AK4Oqc--