* [linux-next regression] remoteproc seems to be broken
@ 2025-05-11 1:09 Alexey Klimov
2025-05-12 19:05 ` Thomas Gleixner
0 siblings, 1 reply; 2+ messages in thread
From: Alexey Klimov @ 2025-05-11 1:09 UTC (permalink / raw)
To: tglx, linux-next
Cc: peterz, neil.armstrong, linux-arm-msm, linux-remoteproc,
andersson, mathieu.poirier
Hi,
we started to observe regression on linux-next starting with next-20250508.
Neil bisected it and it pointed to:
2ef2e13094c7510c40833951c2ec36cf8574331a
genirq/chip: Rework handle_nested_irq()
https://lore.kernel.org/all/20250429065420.744042890@linutronix.de
>No functional change.
Manually reverting that commit resolved the problem for me.
I suspect it may affect more than one Qcom board but I test it currently on qrb4210 rb2.
Mostly failed remoteproc start up hence no adsp, cdsp, no wifi, etc.
[ 8.937745] remoteproc remoteproc0: modem is available
[ 8.963841] remoteproc remoteproc1: adsp is available
[ 8.971927] remoteproc remoteproc2: cdsp is available
[ 9.027266] remoteproc remoteproc2: powering up cdsp
[ 9.037796] remoteproc remoteproc2: Booting fw image qcom/qrb4210/cdsp.mbn, size 3008020
[ 9.153625] remoteproc remoteproc1: powering up adsp
[ 9.158697] remoteproc remoteproc1: Booting fw image qcom/qrb4210/adsp.mbn, size 13196348
[ 10.357702] remoteproc remoteproc0: powering up modem
[ 10.442049] remoteproc remoteproc0: Booting fw image qcom/qrb4210/modem.mbn, size 8881672
...
[ 14.508388] qcom_q6v5_pas b300000.remoteproc: start timed out
[ 14.508418] qcom_q6v5_pas a400000.remoteproc: start timed out
[ 14.522733] remoteproc remoteproc2: can't start rproc cdsp: -110
[ 14.532531] remoteproc remoteproc1: can't start rproc adsp: -110
[ 16.043271] qcom_q6v5_pas 6080000.remoteproc: start timed out
[ 16.058593] remoteproc remoteproc0: can't start rproc modem: -110
[ 16.076600] remoteproc remoteproc0: Boot failed: -110
[ 20.143356] platform sound: deferred probe pending: platform: wait for supplier /soc@0/pinctrl@a7c0000/lpi-i2s2-active-state
[ 20.154630] platform a7c0000.pinctrl: deferred probe pending: qcom-sm4250-lpass-lpi-pinctrl: Failed to get clk 'audio'
[ 20.165381] platform a600000.codec: deferred probe pending: platform: supplier a730000.codec not ready
[ 20.174738] platform a620000.codec: deferred probe pending: platform: supplier a730000.codec not ready
[ 20.184089] platform a610000.soundwire: deferred probe pending: platform: wait for supplier /soc@0/pinctrl@a7c0000/lpass-rx-swr-active-state
[ 20.196738] i2c 1-000f: deferred probe pending: i2c: supplier a7c0000.pinctrl not ready
[ 20.204793] platform a730000.codec: deferred probe pending: platform: wait for supplier /soc@0/pinctrl@a7c0000/lpass-dmic01-active-state
[ 20.217114] platform a740000.soundwire: deferred probe pending: platform: wait for supplier /soc@0/pinctrl@a7c0000/lpass-tx-swr-active-state
Thanks,
Alexey
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [linux-next regression] remoteproc seems to be broken
2025-05-11 1:09 [linux-next regression] remoteproc seems to be broken Alexey Klimov
@ 2025-05-12 19:05 ` Thomas Gleixner
0 siblings, 0 replies; 2+ messages in thread
From: Thomas Gleixner @ 2025-05-12 19:05 UTC (permalink / raw)
To: Alexey Klimov, linux-next
Cc: peterz, neil.armstrong, linux-arm-msm, linux-remoteproc,
andersson, mathieu.poirier
On Sun, May 11 2025 at 02:09, Alexey Klimov wrote:
> Hi,
>
> we started to observe regression on linux-next starting with next-20250508.
> Neil bisected it and it pointed to:
> 2ef2e13094c7510c40833951c2ec36cf8574331a
> genirq/chip: Rework handle_nested_irq()
> https://lore.kernel.org/all/20250429065420.744042890@linutronix.de
>
>>No functional change.
>
> Manually reverting that commit resolved the problem for me.
https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/commit/?h=irq/core
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2025-05-12 19:05 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2025-05-11 1:09 [linux-next regression] remoteproc seems to be broken Alexey Klimov
2025-05-12 19:05 ` Thomas Gleixner
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox