From owner-freebsd-sparc64@FreeBSD.ORG Thu Apr 1 16:00:19 2010 Return-Path: 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 CCBCF106566B for ; Thu, 1 Apr 2010 16:00:19 +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 A16C08FC15 for ; Thu, 1 Apr 2010 16:00:19 +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 o31G0JCe065008 for ; Thu, 1 Apr 2010 16:00:19 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o31G0J7j065007; Thu, 1 Apr 2010 16:00:19 GMT (envelope-from gnats) Date: Thu, 1 Apr 2010 16:00:19 GMT Message-Id: <201004011600.o31G0J7j065007@freefall.freebsd.org> To: freebsd-sparc64@FreeBSD.org From: Nathaniel W Filardo 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: Nathaniel W Filardo List-Id: Porting FreeBSD to the Sparc List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Apr 2010 16:00:19 -0000 The following reply was made to PR sparc64/145211; it has been noted by GNATS. From: Nathaniel W Filardo To: Marius Strobl Cc: bug-followup@freebsd.org Subject: Re: kern/145211: Memory modified after free Date: Thu, 1 Apr 2010 11:52:48 -0400 --z20Z95FJiBb6FirT Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Thu, Apr 01, 2010 at 01:23:59PM +0200, Marius Strobl wrote: > 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 Thank you for decoding that for me. > 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 Just csup'd and am now rebuilding; will let you know. > Which version of if_bge.c were you running when the panic occurred? $FreeBSD: src/sys/dev/bge/if_bge.c,v 1.284 2010/03/25 17:17:35 yongari Exp $ --z20Z95FJiBb6FirT Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAku0wVAACgkQTeQabvr9Tc9jgQCeNIHaRTCWFvsZyxIwvS7kqTVY /XoAniK2Qq/z7NdJK9NrfNN/d+w+//dq =TzYn -----END PGP SIGNATURE----- --z20Z95FJiBb6FirT--