From: Lars-Peter Clausen <lars@metafoo.de>
To: Fabio Estevam <festevam@gmail.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
Mark Brown <broonie@kernel.org>,
Nicolin Chen <b42378@freescale.com>,
Shawn Guo <shawn.guo@linaro.org>
Subject: Re: mx6: Audio does not work on linux-next 20140107
Date: Tue, 07 Jan 2014 13:07:22 +0100 [thread overview]
Message-ID: <52CBEDFA.10603@metafoo.de> (raw)
In-Reply-To: <CAOMZO5C=TFczzz8CQj6N=N_Z=p26_73SJvSk5cmp9FPVxF+O=A@mail.gmail.com>
On 01/07/2014 12:56 PM, Fabio Estevam wrote:
[...]
> Backtrace:
> [<804aee5c>] (dmaengine_pcm_dma_complete) from [<802e6428>] (sdma_tasklet+0x128)
> [<802e6300>] (sdma_tasklet) from [<8002c4b8>] (tasklet_action+0x90/0x148)
> r10:808f64c0 r8:00000000 r7:8089cd24 r6:80894000 r5:00000000 r4:bfaa41b0
[...]
>
> I haven't started debugging it, but if this looks familiar to someone,
> please let me know.
>
We've had similar problems like this before. Typically this is caused by the
dmaengine driver calling the complete callback when it shouldn't. E.g. after
dmaegine_terminate_all() has already been called for the channel. There is
also unfortunately a small chance condition (which needs some extensions to
the dmaengine API before we can fix it). But the chance for this race
condition to occur is really small and has only been observed on a 4 (or 8,
not sure) core system so far. Is the problem reproducible in your case? Also
do you have a know good kernel version?
> Regards,
>
> Fabio Estevam
>
next prev parent reply other threads:[~2014-01-07 12:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-07 11:56 mx6: Audio does not work on linux-next 20140107 Fabio Estevam
2014-01-07 12:07 ` Lars-Peter Clausen [this message]
2014-01-07 12:29 ` Fabio Estevam
2014-01-07 12:28 ` Nicolin Chen
2014-01-07 12:49 ` Fabio Estevam
2014-01-08 3:50 ` Fabio Estevam
2014-01-08 5:04 ` Nicolin Chen
2014-01-08 10:01 ` Fabio Estevam
2014-01-08 9:53 ` Nicolin Chen
2014-01-08 15:33 ` Fabio Estevam
2014-01-07 12:50 ` Lars-Peter Clausen
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=52CBEDFA.10603@metafoo.de \
--to=lars@metafoo.de \
--cc=alsa-devel@alsa-project.org \
--cc=b42378@freescale.com \
--cc=broonie@kernel.org \
--cc=festevam@gmail.com \
--cc=shawn.guo@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.