From: Dan Williams <dan.j.williams@intel.com>
To: Tirumala Reddy Marri <tmarri@amcc.com>
Cc: "linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>
Subject: RE: where is async_tx_clear_ack() function called.
Date: Fri, 10 Jul 2009 10:53:36 -0700 [thread overview]
Message-ID: <1247248416.15724.5.camel@dwillia2-linux.ch.intel.com> (raw)
In-Reply-To: <AC5E1C3367E37D44970B81A6ADD1DA2C07B08BA9@SDCEXCHANGE01.ad.amcc.com>
On Fri, 2009-07-10 at 10:44 -0700, Tirumala Reddy Marri wrote:
>
> Thanks Dan.
> I see the flags are set in the xxxx_pre_dma_xor. I am hitting
> BUG_ON(async_tx_test_ack(depend_tx) || depend_tx->next || tx->parent)
> I happening. Looks like some dependency related issue. When I
> suppress this by calling async_tx_clear_ack() in xxx_free_slots()
> function, that is leading to file-system corruption in the case of
> recovery or re-build.
>
>
> The driver I am working on is a different SOC . It is a subset of
> (DMA+XOR little different) what emccraft posted. That driver can't be
> used as it is. There is another SOC ADMA driver which is completely
> different HW from the emccrafts driver.
Channel switching can be tricky to debug. One thing you might try is
limiting offload to one channel. I.e. if memcpy and xor are provided by
different channels then turn off (don't register) the memcpy channels
and see if that resolves your issue. If it does then you need to review
the iop-adma driver or the Emcraft ppc440spe driver to see what is
causing the mishandling of channel switching.
--
Dan
next prev parent reply other threads:[~2009-07-10 17:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-09 23:36 where is async_tx_clear_ack() function called Tirumala Reddy Marri
2009-07-10 17:15 ` Dan Williams
2009-07-10 17:44 ` Tirumala Reddy Marri
2009-07-10 17:53 ` Dan Williams [this message]
2009-07-10 20:40 ` Tirumala Reddy Marri
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=1247248416.15724.5.camel@dwillia2-linux.ch.intel.com \
--to=dan.j.williams@intel.com \
--cc=linux-raid@vger.kernel.org \
--cc=tmarri@amcc.com \
/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).