From owner-freebsd-sparc64@FreeBSD.ORG Thu May 6 08:10:03 2010 Return-Path: Delivered-To: freebsd-sparc64@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B08DB106566B for ; Thu, 6 May 2010 08:10:03 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40]) by mx1.freebsd.org (Postfix) with ESMTP id 9FFD68FC17 for ; Thu, 6 May 2010 08:10:03 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id o468A3i7056571 for ; Thu, 6 May 2010 08:10:03 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o468A3sZ056570; Thu, 6 May 2010 08:10:03 GMT (envelope-from gnats) Date: Thu, 6 May 2010 08:10:03 GMT Message-Id: <201005060810.o468A3sZ056570@freefall.freebsd.org> To: freebsd-sparc64@FreeBSD.org From: Marius Strobl Cc: Subject: Re: sparc64/144867: panic: trap: memory address not aligned booting Sunfire 280R X-BeenThere: freebsd-sparc64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Marius Strobl List-Id: Porting FreeBSD to the Sparc List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 May 2010 08:10:03 -0000 The following reply was made to PR sparc64/144867; it has been noted by GNATS. From: Marius Strobl To: Rob Farmer Cc: bug-followup@freebsd.org Subject: Re: sparc64/144867: panic: trap: memory address not aligned booting Sunfire 280R Date: Thu, 6 May 2010 10:01:41 +0200 On Wed, May 05, 2010 at 10:54:49AM -0700, Rob Farmer wrote: > On Sat, Apr 17, 2010 at 1:05 PM, Marius Strobl > wrote: > > > > Could both of you please refetch the following patch and give it try? > > http://people.freebsd.org/~marius/cas_mmf.diff > > The MD5 hash of the new version is 0d668f21e2b3bb3c9641950bd0153e3d. > > > > Marius > > > > > > Is the patch you sent me the same as what was committed? Except for a change in a comment it was. > I just tried > to upgrade the system today and am getting a panic again: This likely is a variation of the problem that when booting from disk the firmware leaves us with a PCI bus error that may be cleared from the status registers but nevertheless triggers an error interrupt, which you already hit earlier. I've to think some more about this. Marius