From owner-freebsd-sparc64@FreeBSD.ORG  Wed Sep 23 00:30:07 2009
Return-Path: <owner-freebsd-sparc64@FreeBSD.ORG>
Delivered-To: freebsd-sparc64@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id B4263106566B
	for <freebsd-sparc64@freebsd.org>; Wed, 23 Sep 2009 00:30:07 +0000 (UTC)
	(envelope-from marius@alchemy.franken.de)
Received: from alchemy.franken.de (alchemy.franken.de [194.94.249.214])
	by mx1.freebsd.org (Postfix) with ESMTP id 4533F8FC18
	for <freebsd-sparc64@freebsd.org>; Wed, 23 Sep 2009 00:30:07 +0000 (UTC)
Received: from alchemy.franken.de (localhost [127.0.0.1])
	by alchemy.franken.de (8.14.3/8.14.3/ALCHEMY.FRANKEN.DE) with ESMTP id
	n8N0U6cB037752; Wed, 23 Sep 2009 02:30:06 +0200 (CEST)
	(envelope-from marius@alchemy.franken.de)
Received: (from marius@localhost)
	by alchemy.franken.de (8.14.3/8.14.3/Submit) id n8N0U6sx037751;
	Wed, 23 Sep 2009 02:30:06 +0200 (CEST) (envelope-from marius)
Date: Wed, 23 Sep 2009 02:30:06 +0200
From: Marius Strobl <marius@alchemy.franken.de>
To: KOT MATPOCKuH <matpockuh@gmail.com>
Message-ID: <20090923003006.GK73777@alchemy.franken.de>
References: <3979a4b0909170200x754ea8c5l495e300b2a7a5113@mail.gmail.com>
	<20090917224556.GA41908@alchemy.franken.de>
	<3979a4b0909172329q3a113942xfcd71394a98fee19@mail.gmail.com>
	<20090918131416.GQ57060@alchemy.franken.de>
	<3979a4b0909202346h5c062fa1qb5150ad90f970c5b@mail.gmail.com>
	<20090921172517.GE73777@alchemy.franken.de>
	<3979a4b0909220722w7fd3f23fp57065cd0a981e42b@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3979a4b0909220722w7fd3f23fp57065cd0a981e42b@mail.gmail.com>
User-Agent: Mutt/1.4.2.3i
Cc: freebsd-sparc64@freebsd.org
Subject: Re: Is it posible to run FreeBSD/sparc64 on SunFire V215?
X-BeenThere: freebsd-sparc64@freebsd.org
X-Mailman-Version: 2.1.5
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, 23 Sep 2009 00:30:07 -0000

On Tue, Sep 22, 2009 at 06:22:22PM +0400, KOT MATPOCKuH wrote:
> Hello!
> 
> 2009/9/21 Marius Strobl <marius@alchemy.franken.de>:
> >> pcib1: <OFW PCI-PCI bridge> mem 0x100pcib0: DMC error: MMU error 0x4000000040
> >> panic: pcib0: fatal DMC/PEC error
> > Please re-fetch fire.diff and try again.
> I have a new panic logs :)
> http://kot.spb.ru/tmp/fbsd/boot.log.0 (with -sv)
> http://kot.spb.ru/tmp/fbsd/boot.log.1 (without)
> 

Please try booting the same kernel using the following loader:
http://people.freebsd.org/~marius/loader

If that still results in the following panic:
pcib0: DMC error: MMU error 0x4000000040
panic: pcib0: fatal DMC/PEC error
locate the following lines in fire.c:
	/* not enabled by OpenSolaris *
	FIRE_PCI_SET(sc, FO_PCI_MMU_INT_EN,
	    FO_PCI_MMU_ERR_INT_S_MASK | FO_PCI_MMU_ERR_INT_P_MASK);
and replace them with:
	FIRE_PCI_SET(sc, FO_PCI_MMU_INT_EN,
	    (FO_PCI_MMU_ERR_INT_S_MASK | FO_PCI_MMU_ERR_INT_P_MASK) &
	    ~(FO_PCI_MMU_ERR_INT_TTE_INV_S | FO_PCI_MMU_ERR_INT_TTE_INV_P));
Then try again with a kernel built with that change in place
(the loader shouldn't matter in this case).

Marius