From: Ranjani Sridharan <ranjani.sridharan@linux.intel.com>
To: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
Jon Flatley <jflat@chromium.org>,
alsa-devel@alsa-project.org
Cc: benzh@chromium.org
Subject: Re: [BUG] bdw-rt5650 DSP boot timeout
Date: Mon, 29 Jul 2019 17:53:07 -0700 [thread overview]
Message-ID: <ac7bcb42e40ac12d9924fd65c3e2c68b9b11b093.camel@linux.intel.com> (raw)
In-Reply-To: <39533fe5-c060-7a07-c910-74b83eee53c4@linux.intel.com>
On Mon, 2019-07-29 at 18:02 -0500, Pierre-Louis Bossart wrote:
>
> On 7/29/19 4:53 PM, Jon Flatley wrote:
> > I've been working on upstreaming the bdw-rt5650 machine driver for
> > the
> > Acer Chromebase 24 (buddy). There seems to be an issue when first
> > setting the hardware controls that appears to be crashing the DSP:
> >
> > [ 51.424554] haswell-pcm-audio haswell-pcm-audio: FW loaded,
> > mailbox
> > readback FW info: type 01, - version: 00.00, build 77, source
> > commit
> > id: 876ac6906f31a43b6772b23c7c983ce9dcb18a19
> > ...
> > [ 84.924666] haswell-pcm-audio haswell-pcm-audio: error: audio
> > DSP
> > boot timeout IPCD 0x0 IPCX 0x0
> > [ 85.260655] haswell-pcm-audio haswell-pcm-audio: ipc: --message
> > timeout-- ipcx 0x83000000 isr 0x00000000 ipcd 0x00000000 imrx
> > 0x7fff0000
> > [ 85.273609] haswell-pcm-audio haswell-pcm-audio: error: stream
> > commit failed
> > [ 85.279746] System PCM: error: failed to commit stream -110
> > [ 85.285388] haswell-pcm-audio haswell-pcm-audio: ASoC:
> > haswell-pcm-audio hw params failed: -110
> > [ 85.293963] System PCM: ASoC: hw_params FE failed -110
> >
> > This happens roughly 50% of the time when first setting hardware
> > controls after a reboot. The other 50% of the time the DSP comes up
> > just fine and audio works fine thereafter. Adding "#define DEBUG 1"
> > to
> > sound/soc/intel/haswell/sst-haswell-ipc.c makes the issue occur
> > much
> > less frequently in my testing. Seems like a subtle timing issue.
> >
> > There were timing issues encountered during the bringup of the 2015
> > chromebook pixel (samus) which uses the bdw-rt5677 machine driver.
> > Those were slightly different, and manifested during repeated
> > arecords. Both devices use the same revision of the sst2 firmware.
> >
> > Any ideas for how to debug this?
>
> this could be trying to send an IPC while you are already waiting
> for
> one to complete. we've seen this before with SOF, if the IPCs are
> not
> strictly serialized then things go in the weeds and timeout.
Pierre/Jon
In this case it looks like the DSP boot failed leading to the IPC
timeout? WOndering if increasing the boot timeout would help?
Thanks,
Ranjani
>
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@alsa-project.org
> https://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next prev parent reply other threads:[~2019-07-30 0:53 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-29 21:53 [BUG] bdw-rt5650 DSP boot timeout Jon Flatley
2019-07-29 23:02 ` Pierre-Louis Bossart
2019-07-29 23:10 ` Jon Flatley
2019-07-30 2:28 ` Pierre-Louis Bossart
2019-07-30 0:53 ` Ranjani Sridharan [this message]
2019-07-30 2:23 ` Pierre-Louis Bossart
2019-07-30 17:45 ` Jon Flatley
2019-07-30 18:47 ` Ranjani Sridharan
2019-07-30 19:04 ` Pierre-Louis Bossart
2019-08-14 19:48 ` Jon Flatley
2019-08-14 20:51 ` Pierre-Louis Bossart
2019-08-14 21:25 ` Jon Flatley
2019-08-19 2:33 ` Jie, Yang
2019-08-19 18:08 ` Cezary Rojewski
2019-08-19 22:36 ` Jon Flatley
2019-08-19 23:01 ` Curtis Malainey
2019-08-20 0:55 ` Pierre-Louis Bossart
2019-08-20 2:11 ` Jie, Yang
2019-08-22 15:29 ` Cezary Rojewski
2019-08-27 11:53 ` Gustaw Lewandowski
2019-08-27 22:03 ` Jon Flatley
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=ac7bcb42e40ac12d9924fd65c3e2c68b9b11b093.camel@linux.intel.com \
--to=ranjani.sridharan@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=benzh@chromium.org \
--cc=jflat@chromium.org \
--cc=pierre-louis.bossart@linux.intel.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).