From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate.crashing.org (gate.crashing.org [63.228.1.57]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by ozlabs.org (Postfix) with ESMTPS id A85C72C0416 for ; Sun, 23 Jun 2013 10:00:58 +1000 (EST) Message-ID: <1371945647.3944.106.camel@pasglop> Subject: Re: Inbound PCI and Memory Corruption From: Benjamin Herrenschmidt To: Peter LaDow Date: Sun, 23 Jun 2013 10:00:47 +1000 In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Cc: linuxppc-dev@lists.ozlabs.org List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Fri, 2013-06-21 at 10:14 -0700, Peter LaDow wrote: > After a (finally!) successful search of the list archive, I did find > this: > > http://web.archiveorange.com/archive/v/9IQA26gPvdf4foaTcmCV > > Which seems very related to my problem. However, the patch that is > ultimately referenced is in place in 3.0.80 (see > https://lists.ozlabs.org/pipermail/linuxppc-dev/2006-February/021267.html). > > Hmmm... perhaps our FDT is bad? Afaik e300 is slightly out of order, maybe it's missing a memory barrier somewhere.... One thing to try is to add some to the dma_map/unmap ops. Also audit the driver to ensure that it properly uses barriers when populating descriptors (and maybe compare to a more recent version of the driver upstream). Ben.