Messages in this thread | | | Date | Fri, 7 Jun 2019 20:00:21 +0100 | From | Mark Brown <> | Subject | Re: [alsa-devel] next/master boot bisection: next-20190528 on sun8i-h3-libretech-all-h3-cc |
| |
On Fri, Jun 07, 2019 at 05:31:12PM +0100, Guillaume Tucker wrote: > On 30/05/2019 16:53, Takashi Iwai wrote:
> >> + mutex_lock(&client_mutex); > >> for_each_rtdcom(rtd, rtdcom) { > >> component = rtdcom->component; > >> > >> if (component->driver->remove_order == order) > >> soc_remove_component(component); > >> } > >> + mutex_unlock(&client_mutex);
> > Ranjani, which code path your patch tries to address? Maybe better to > > wrap client_mutex() in the caller side like snd_soc_unbind_card()?
> Is anyone looking into this issue?
> It is still occurring in next-20190606, there was a bisection > today which landed on the same commit. There just hasn't been > any new bisection reports because they have been temporarily > disabled while we fix some issues on kernelci.org.
I was expecting that Ranjani or one of the other Intel people was looking into it... [unhandled content-type:application/pgp-signature] | |