[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <da94225b-f4c5-4cdd-8ddb-937f69a7c8b2@sirena.org.uk>
Date: Mon, 20 Oct 2025 12:12:55 +0100
From: Mark Brown <broonie@...nel.org>
To: Alexey Klimov <alexey.klimov@...aro.org>
Cc: gregkh@...uxfoundation.org, srini@...nel.org, rafael@...nel.org,
dakr@...nel.org, make24@...as.ac.cn, steev@...i.org,
dmitry.baryshkov@....qualcomm.com, linux-kernel@...r.kernel.org,
linux-sound@...r.kernel.org, linux-arm-msm@...r.kernel.org,
stable@...r.kernel.org
Subject: Re: [PATCH] regmap: slimbus: fix bus_context pointer in
__devm_regmap_init_slimbus
On Mon, Oct 20, 2025 at 02:55:57AM +0100, Alexey Klimov wrote:
> Commit 4e65bda8273c ("ASoC: wcd934x: fix error handling in
> wcd934x_codec_parse_data()") revealed the problem in slimbus regmap.
> That commit breaks audio playback, for instance, on sdm845 Thundercomm
> Dragonboard 845c board:
>
> Unable to handle kernel paging request at virtual address ffff8000847cbad4
> Mem abort info:
> ESR = 0x0000000096000007
> EC = 0x25: DABT (current EL), IL = 32 bits
> SET = 0, FnV = 0
> EA = 0, S1PTW = 0
> FSC = 0x07: level 3 translation fault
Please think hard before including complete backtraces in upstream
reports, they are very large and contain almost no useful information
relative to their size so often obscure the relevant content in your
message. If part of the backtrace is usefully illustrative (it often is
for search engines if nothing else) then it's usually better to pull out
the relevant sections.
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists