On Fri, Apr 18, 2025 at 01:23:27PM +0530, Naresh Kamboju wrote:
On Thu, 17 Apr 2025 at 23:23, Greg Kroah-Hartman gregkh@linuxfoundation.org wrote:
This is the start of the stable review cycle for the 6.14.3 release. There are 449 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know.
Responses should be made by Sat, 19 Apr 2025 17:49:48 +0000. Anything received after that time might be too late.
The whole patch series can be found in one patch at: https://www.kernel.org/pub/linux/kernel/v6.x/stable-review/patch-6.14.3-rc1.... or in the git tree and branch at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-6.14.y and the diffstat can be found below.
thanks,
greg k-h
Regressions on arm64 dragonboard 410c boot failed with lkftconfig on the stable rc 6.14.3-rc1. While booting, the following kernel warnings were noticed and boot failed.
First seen on the 6.14.3-rc1 Good: v6.14.2 Bad: v6.14.2-450-g0e7f2bba84c1
Regressions found on arm64 dragonboard 410c:
- Boot/clang-20-lkftconfig
Regression Analysis:
- New regression? Yes
- Reproducibility? Yes
Boot regression: arm64 dragonboard 410c WARNING regulator core.c regulator_put
Reported-by: Linux Kernel Functional Testing lkft@linaro.org
## Boot log arm64 dragonboard 410c [ 3.924339] remoteproc:smd-edge: failed to parse smd edge [ 4.051490] msm_hsusb 78d9000.usb: Failed to create device link (0x180) with supplier remoteproc for /soc@0/usb@78d9000/ulpi/phy [ 4.055155] qcom-clk-smd-rpm remoteproc:smd-edge:rpm-requests:clock-controller: Error registering SMD clock driver (-1431655766) [ 4.062274] qcom-clk-smd-rpm remoteproc:smd-edge:rpm-requests:clock-controller: probe with driver qcom-clk-smd-rpm failed with error -1431655766
^^^^^^^^^^^ This is 0xaaaaaaaa which is very suspicious.
We recently changed out test configs to use CONFIG_INIT_STACK_ALL_PATTERN=y (my fault) and the documentation says that 0xaaaaaaaa is the default uninitialized variable pattern for Clang 64bit. So it's possible that this is not a regression but an older bug which is only detected with that config change. Could you try again with CONFIG_INIT_STACK_ALL_ZERO=y instead?
However, I don't see how this can be stack data.
This error code is from qcom_rpm_smd_write() and I'm pretty sure it's from the ret = rpm->ack_status; assignment and it's supposed to be zero.
regards, dan carpenter