From: "Roedel, Joerg" <Joerg.Roedel@amd.com>
To: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
Cc: "sachinp@linux.vnet.ibm.com" <sachinp@linux.vnet.ibm.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"santil@us.ibm.com" <santil@us.ibm.com>,
"Linuxppc-dev@ozlabs.org" <Linuxppc-dev@ozlabs.org>,
"devilbis@us.ibm.com" <devilbis@us.ibm.com>,
"James.Bottomley@suse.de" <James.Bottomley@suse.de>,
"sleddog@us.ibm.com" <sleddog@us.ibm.com>,
"brking@linux.vnet.ibm.com" <brking@linux.vnet.ibm.com>,
"tj@kernel.org" <tj@kernel.org>,
"subrata@linux.vnet.ibm.com" <subrata@linux.vnet.ibm.com>,
"dipraksh@linux.vnet.ibm.com" <dipraksh@linux.vnet.ibm.com>
Subject: Re: 2.6.35-stable/ppc64/p7: Badness at lib/dma-debug.c:902, Call Trace & Instruction Dump during boot
Date: Wed, 4 Aug 2010 15:16:34 +0200 [thread overview]
Message-ID: <20100804131634.GX26098@amd.com> (raw)
In-Reply-To: <20100802205404C.fujita.tomonori@lab.ntt.co.jp>
On Mon, Aug 02, 2010 at 07:55:03AM -0400, FUJITA Tomonori wrote:
> I guess that this driver does a partial sync with
> dma_sync_single_for_* API. dma-debug can't handle it properly. It's
> likely that this is a false warning.
If this turns out to be true it is not trivial to fix. I prepare a patch
to test for you.
Joerg
--
AMD Operating System Research Center
Advanced Micro Devices GmbH Einsteinring 24 85609 Dornach
General Managers: Alberto Bozzo, Andrew Bowd
Registration: Dornach, Landkr. Muenchen; Registerger. Muenchen, HRB Nr. 43632
next prev parent reply other threads:[~2010-08-04 13:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-02 10:51 2.6.35-stable/ppc64/p7: Badness at lib/dma-debug.c:902, Call Trace & Instruction Dump during boot Subrata Modak
2010-08-02 11:55 ` FUJITA Tomonori
2010-08-04 13:16 ` Roedel, Joerg [this message]
2010-08-04 14:18 ` FUJITA Tomonori
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100804131634.GX26098@amd.com \
--to=joerg.roedel@amd.com \
--cc=James.Bottomley@suse.de \
--cc=Linuxppc-dev@ozlabs.org \
--cc=brking@linux.vnet.ibm.com \
--cc=devilbis@us.ibm.com \
--cc=dipraksh@linux.vnet.ibm.com \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=sachinp@linux.vnet.ibm.com \
--cc=santil@us.ibm.com \
--cc=sleddog@us.ibm.com \
--cc=subrata@linux.vnet.ibm.com \
--cc=tj@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).