From owner-freebsd-sparc64@FreeBSD.ORG  Thu Apr  1 11:30:07 2010
Return-Path: <owner-freebsd-sparc64@FreeBSD.ORG>
Delivered-To: freebsd-sparc64@hub.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 10B93106564A
	for <freebsd-sparc64@hub.freebsd.org>;
	Thu,  1 Apr 2010 11:30:07 +0000 (UTC)
	(envelope-from gnats@FreeBSD.org)
Received: from freefall.freebsd.org (freefall.freebsd.org
	[IPv6:2001:4f8:fff6::28])
	by mx1.freebsd.org (Postfix) with ESMTP id F2EE68FC17
	for <freebsd-sparc64@hub.freebsd.org>;
	Thu,  1 Apr 2010 11:30:06 +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 o31BU6YN011894
	for <freebsd-sparc64@freefall.freebsd.org>; Thu, 1 Apr 2010 11:30:06 GMT
	(envelope-from gnats@freefall.freebsd.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o31BU6IY011882;
	Thu, 1 Apr 2010 11:30:06 GMT (envelope-from gnats)
Date: Thu, 1 Apr 2010 11:30:06 GMT
Message-Id: <201004011130.o31BU6IY011882@freefall.freebsd.org>
To: freebsd-sparc64@FreeBSD.org
From: Marius Strobl <marius@alchemy.franken.de>
Cc: 
Subject: Re: kern/145211: Memory modified after free
X-BeenThere: freebsd-sparc64@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Marius Strobl <marius@alchemy.franken.de>
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: Thu, 01 Apr 2010 11:30:07 -0000

The following reply was made to PR sparc64/145211; it has been noted by GNATS.

From: Marius Strobl <marius@alchemy.franken.de>
To: bug-followup@FreeBSD.org, nwf@cs.jhu.edu
Cc:  
Subject: Re: kern/145211: Memory modified after free
Date: Thu, 1 Apr 2010 13:23:59 +0200

 >  
 > Memory modified after free 0xfffff80005675000(2048) val=dead0003 @ 0xfffff80005675000
 > Memory modified after free 0xfffff8000564c800(2048) val=dead0003 @ 0xfffff8000564c800
 > panic: pcib: PCI bus B error AFAR 0 AFSR 0 PCI CSR 0x10730b2aff IOMMU 0x3060003 STATUS 0x2a0
 
 This is the IOMMU reporting an error as STX_PCI_CTRL_MMU_ERR is set in
 the PCI CSR and TOM_PCI_IOMMU_ERR is set in the IOMMO CSR. Moreover the
 TOM_PCI_IOMMU_INVALID_ERR set in the latter suggests that a DMA buffer
 was used after it had been unloaded (and thus the TTE invalidated). So
 it's quite likely that both the UMA and the IOMMU complaints are caused
 by the same problem. Unfortunately, neither allows to identify the
 culprit. If you could move the traffic in question from bge2 to bge1
 and either use r206020 or the following patch that should allow to
 identify at least the driver involved, i.e. ata(4) or bge(4), by
 additionally indicating whether pcib0 or pcib3 triggered the panic.
 http://people.freebsd.org/~marius/psycho_schizo_device_get_nameunit.diff
 
 Which version of if_bge.c were you running when the panic occurred?
 
 Marius