linux-kernel - Re: [PATCH] soc: qcom: mark pd-mapper as broken

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <Z4TXww5rAkMR8OmM@hovoldconsulting.com>
Date: Mon, 13 Jan 2025 10:07:15 +0100
From: Johan Hovold <johan@...nel.org>
To: Frank Oltmanns <frank@...manns.dev>
Cc: Bjorn Andersson <andersson@...nel.org>,
	Chris Lew <quic_clew@...cinc.com>,
	Stephan Gerhold <stephan.gerhold@...aro.org>,
	Johan Hovold <johan+linaro@...nel.org>,
	Dmitry Baryshkov <dmitry.baryshkov@...aro.org>,
	Konrad Dybcio <konradybcio@...nel.org>,
	Abel Vesa <abel.vesa@...aro.org>, linux-arm-msm@...r.kernel.org,
	linux-kernel@...r.kernel.org, regressions@...ts.linux.dev,
	stable@...r.kernel.org
Subject: Re: [PATCH] soc: qcom: mark pd-mapper as broken

On Sat, Jan 11, 2025 at 03:21:35PM +0100, Frank Oltmanns wrote:
> On 2025-01-08 at 15:06:34 +0100, Johan Hovold <johan@...nel.org> wrote:

> > And today I also hit this on the sc8280xp CRD reference design, so as
> > expected, there is nothing SoC specific about the audio service
> > regression either:
> >
> > [   11.235564] PDR: avs/audio get domain list txn wait failed: -110
> > [   11.241976] PDR: service lookup for avs/audio failed: -110
> >
> > even if it may be masked by random changes in timing.
> >
> > These means it affects also machines like the X13s which already have
> > audio enabled.
> 
> I've blocklisted the in-kernel pd-mapper module for now and have
> switched back to the userspace pd-mapper.
> 
> I don't know if it's helpful or not, but I don't get these error logs
> when using to the in-kernel pd-mapper. It's just that the phone's mic
> only works on approximately every third boot (unless I defer loading the
> module).

Ok, then it sounds like you're hitting a separate bug that is also
triggered by the changed timings with the in-kernel pd-mapper.

Are there any hints in the logs about what goes wrong in your setup? And
the speakers are still working, it's just affecting the mic?

Johan