From: Hector Palacios <hector.palacios@digi.com>
To: Fabio Estevam <festevam@gmail.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Marek Vasut <marex@denx.de>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
Shawn Guo <shawn.guo@linaro.org>,
Dong Aisheng <b29396@freescale.com>,
"Mark Brown" <broonie@opensource.wolfsonmicro.com>
Subject: Re: BUG: soft lockup when recording audio on MX28EVK with ASoC sgtl5000
Date: Tue, 26 Mar 2013 12:43:41 +0100 [thread overview]
Message-ID: <515189ED.3080807@digi.com> (raw)
In-Reply-To: <CAOMZO5CvrkfGPi7=4-JXnSLzU+8NKV=RD9n3eLvCehXdv6JHEg@mail.gmail.com>
Hi Fabio,
On 03/26/2013 12:15 AM, Fabio Estevam wrote:
> Hector,
>
> On Mon, Mar 25, 2013 at 4:31 PM, Fabio Estevam <festevam@gmail.com> wrote:
>> Hi Hector,
>>
>> On Mon, Mar 25, 2013 at 7:52 AM, Hector Palacios
>> <hector.palacios@digi.com> wrote:
>>> Hello,
>>>
>>> I just tried recording audio on Freescale's MX28EVK that uses ASoC sgtl5000
>>> (kernel v3.8) with:
>>>
>>> arecord -M -f cd sound.wav --duration 10
>>>
>>> and got a scheduler message:
>>>
>>> [ 789.041847] [sched_delayed] sched: RT throttling activated
>>
>> I have just tested arecord on 3.8,4 and I haven't seen the 'soft lockup' bug.
>>
>> However, I see that mxs saif gets busy after the record and any
>> attempt to do an 'aplay' after the first arecord fails.
>>
>> With the attached patch applied I am able to do arecord/aplay sequence
>> several times.
>>
>> I don't have a cable handy here to actually test if the sound is
>> recorded properly or not.
>>
>> Could you please test it against 3.8.4?
>
> I managed to test arecord and it works with the following as follows:
>
> 1. Run alsamixer and select LINE_IN in the Capture element
>
> 2. Record with the following command line:
>
> arecord -D hw:0,1 -d 10 -f S16_LE -r 44100 -c test.wav
This command works on v3.8 even without your patch. I can arecord/aplay several times
without problems.
With my original command 'arecord [-M] -f cd sound.wav --duration 10', the soft lockup
appears both in v3.8 and v3.8.4 with and without your patch. So it looks like the
patch does not help here.
Regards,
--
Héctor Palacios
prev parent reply other threads:[~2013-03-26 11:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-25 10:52 BUG: soft lockup when recording audio on MX28EVK with ASoC sgtl5000 Hector Palacios
2013-03-25 12:10 ` Marek Vasut
2013-03-25 15:25 ` Shawn Guo
2013-03-25 16:53 ` Hector Palacios
2013-03-25 19:31 ` Fabio Estevam
2013-03-25 19:31 ` Fabio Estevam
2013-03-25 23:15 ` Fabio Estevam
2013-03-26 11:43 ` Hector Palacios [this message]
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=515189ED.3080807@digi.com \
--to=hector.palacios@digi.com \
--cc=alsa-devel@alsa-project.org \
--cc=b29396@freescale.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=festevam@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marex@denx.de \
--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.