This is the start of the stable review cycle for the 6.12.32 release. There are 55 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 Wed, 04 Jun 2025 13:42:20 +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.12.32-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.12.y and the diffstat can be found below.
thanks,
greg k-h
------------- Pseudo-Shortlog of commits:
Greg Kroah-Hartman gregkh@linuxfoundation.org Linux 6.12.32-rc1
Namjae Jeon linkinjeon@kernel.org ksmbd: use list_first_entry_or_null for opinfo_get_list()
Nishanth Menon nm@ti.com net: ethernet: ti: am65-cpsw: Lower random mac address error print to info
Mark Pearson mpearson-lenovo@squebb.ca platform/x86: thinkpad_acpi: Ignore battery threshold change event notification
Kailang Yang kailang@realtek.com ALSA: hda/realtek - restore auto-mute mode for Dell Chrome platform
Valtteri Koskivuori vkoskiv@gmail.com platform/x86: fujitsu-laptop: Support Lifebook S2110 hotkeys
Trond Myklebust trond.myklebust@hammerspace.com NFS: Avoid flushing data while holding directory locks in nfs_rename()
Purva Yeshi purvayeshi550@gmail.com char: tpm: tpm-buf: Add sanity check fallback in read helpers
Umesh Nerlige Ramappa umesh.nerlige.ramappa@intel.com drm/xe: Save the gt pointer in lrc and drop the tile
Aradhya Bhatia aradhya.bhatia@intel.com drm/xe/xe2hpg: Add Wa_22021007897
Ilya Guterman amfernusus@gmail.com nvme-pci: add NVME_QUIRK_NO_DEEPEST_PS quirk for SOLIDIGM P44 Pro
Alessandro Grassi alessandro.grassi@mailbox.org spi: spi-sun4i: fix early activation
Algea Cao algea.cao@rock-chips.com phy: phy-rockchip-samsung-hdptx: Fix PHY PLL output 50.25MHz error
Hal Feng hal.feng@starfivetech.com phy: starfive: jh7110-usb: Fix USB 2.0 host occasional detection failure
Aurabindo Pillai aurabindo.pillai@amd.com drm/amd/display: check stream id dml21 wrapper to get plane_id
George Shen george.shen@amd.com drm/amd/display: fix link_set_dpms_off multi-display MST corner case
Markus Burri markus.burri@mt.com gpio: virtuser: fix potential out-of-bound write
Masahiro Yamada masahiroy@kernel.org um: let 'make clean' properly clean underlying SUBARCH as well
John Chau johnchau@0atlas.com platform/x86: thinkpad_acpi: Support also NEC Lavie X1475JAS
Jeff Layton jlayton@kernel.org nfs: don't share pNFS DS connections between net namespaces
Milton Barrera miltonjosue2001@gmail.com HID: quirks: Add ADATA XPG alpha wireless mouse support
Purva Yeshi purvayeshi550@gmail.com dmaengine: idxd: cdev: Fix uninitialized use of sva in idxd_cdev_open
Christian Brauner brauner@kernel.org coredump: hand a pidfd to the usermode coredump helper
Christian Brauner brauner@kernel.org coredump: fix error handling for replace_fd()
Robin Murphy robin.murphy@arm.com perf/arm-cmn: Add CMN S3 ACPI binding
Robin Murphy robin.murphy@arm.com perf/arm-cmn: Initialise cmn->cpu earlier
Robin Murphy robin.murphy@arm.com perf/arm-cmn: Fix REQ2/SNP2 mixup
Pedro Tammela pctammela@mojatatu.com net_sched: hfsc: Address reentrant enqueue adding class to eltree twice
Siddharth Vadapalli s-vadapalli@ti.com arm64: dts: ti: k3-j784s4-j742s2-main-common: Fix length of serdes_ln_ctrl
Siddharth Vadapalli s-vadapalli@ti.com arm64: dts: ti: k3-j722s-main: Disable "serdes_wiz0" and "serdes_wiz1"
Siddharth Vadapalli s-vadapalli@ti.com arm64: dts: ti: k3-j722s-evm: Enable "serdes_wiz0" and "serdes_wiz1"
Yemike Abhilash Chandra y-abhilashchandra@ti.com arm64: dts: ti: k3-j721e-sk: Add requiried voltage supplies for IMX219
Yemike Abhilash Chandra y-abhilashchandra@ti.com arm64: dts: ti: k3-j721e-sk: Remove clock-names property from IMX219 overlay
Yemike Abhilash Chandra y-abhilashchandra@ti.com arm64: dts: ti: k3-j721e-sk: Add DT nodes for power regulators
Yemike Abhilash Chandra y-abhilashchandra@ti.com arm64: dts: ti: k3-am68-sk: Fix regulator hierarchy
Judith Mendez jm@ti.com arm64: dts: ti: k3-am65-main: Add missing taps to sdhci0
Yemike Abhilash Chandra y-abhilashchandra@ti.com arm64: dts: ti: k3-am62x: Rename I2C switch to I2C mux in OV5640 overlay
Yemike Abhilash Chandra y-abhilashchandra@ti.com arm64: dts: ti: k3-am62x: Rename I2C switch to I2C mux in IMX219 overlay
Yemike Abhilash Chandra y-abhilashchandra@ti.com arm64: dts: ti: k3-am62x: Remove clock-names property from IMX219 overlay
Judith Mendez jm@ti.com arm64: dts: ti: k3-am62p-j722s-common-main: Set eMMC clock parent to default
Judith Mendez jm@ti.com arm64: dts: ti: k3-am62a-main: Set eMMC clock parent to default
Judith Mendez jm@ti.com arm64: dts: ti: k3-am62-main: Set eMMC clock parent to default
Stephan Gerhold stephan.gerhold@linaro.org arm64: dts: qcom: x1e80100: Fix video thermal zone
Johan Hovold johan+linaro@kernel.org arm64: dts: qcom: x1e80100-yoga-slim7x: mark l12b and l15b always-on
Johan Hovold johan+linaro@kernel.org arm64: dts: qcom: x1e80100-qcp: mark l12b and l15b always-on
Stephan Gerhold stephan.gerhold@linaro.org arm64: dts: qcom: x1e80100-qcp: Fix vreg_l2j_1p2 voltage
Stephan Gerhold stephan.gerhold@linaro.org arm64: dts: qcom: x1e80100-lenovo-yoga-slim7x: Fix vreg_l2j_1p2 voltage
Stephan Gerhold stephan.gerhold@linaro.org arm64: dts: qcom: x1e80100-asus-vivobook-s15: Fix vreg_l2j_1p2 voltage
Stephan Gerhold stephan.gerhold@linaro.org arm64: dts: qcom: sm8650: Add missing properties for cryptobam
Stephan Gerhold stephan.gerhold@linaro.org arm64: dts: qcom: sm8550: Add missing properties for cryptobam
Stephan Gerhold stephan.gerhold@linaro.org arm64: dts: qcom: sm8450: Add missing properties for cryptobam
Alok Tiwari alok.a.tiwari@oracle.com arm64: dts: qcom: sm8350: Fix typo in pil_camera_mem node
Karthik Sanagavarapu quic_kartsana@quicinc.com arm64: dts: qcom: sa8775p: Remove cdsp compute-cb@10
Ling Xu quic_lxu5@quicinc.com arm64: dts: qcom: sa8775p: Remove extra entries from the iommus property
Stephan Gerhold stephan.gerhold@linaro.org arm64: dts: qcom: ipq9574: Add missing properties for cryptobam
Axel Forsman axfo@kvaser.com can: kvaser_pciefd: Force IRQ edge in case of nested IRQ
-------------
Diffstat:
Makefile | 4 +- arch/arm64/boot/dts/qcom/ipq9574.dtsi | 2 + arch/arm64/boot/dts/qcom/sa8775p.dtsi | 246 ++------------------- arch/arm64/boot/dts/qcom/sm8350.dtsi | 2 +- arch/arm64/boot/dts/qcom/sm8450.dtsi | 2 + arch/arm64/boot/dts/qcom/sm8550.dtsi | 2 + arch/arm64/boot/dts/qcom/sm8650.dtsi | 2 + .../boot/dts/qcom/x1e80100-asus-vivobook-s15.dts | 4 +- .../boot/dts/qcom/x1e80100-lenovo-yoga-slim7x.dts | 7 +- arch/arm64/boot/dts/qcom/x1e80100-qcp.dts | 6 +- arch/arm64/boot/dts/qcom/x1e80100.dtsi | 10 +- arch/arm64/boot/dts/ti/k3-am62-main.dtsi | 2 - arch/arm64/boot/dts/ti/k3-am62a-main.dtsi | 2 - .../boot/dts/ti/k3-am62p-j722s-common-main.dtsi | 2 - .../arm64/boot/dts/ti/k3-am62x-sk-csi2-imx219.dtso | 3 +- .../arm64/boot/dts/ti/k3-am62x-sk-csi2-ov5640.dtso | 2 +- .../boot/dts/ti/k3-am62x-sk-csi2-tevi-ov5640.dtso | 2 +- arch/arm64/boot/dts/ti/k3-am65-main.dtsi | 2 + arch/arm64/boot/dts/ti/k3-am68-sk-base-board.dts | 13 +- .../boot/dts/ti/k3-j721e-sk-csi2-dual-imx219.dtso | 35 ++- arch/arm64/boot/dts/ti/k3-j721e-sk.dts | 31 +++ arch/arm64/boot/dts/ti/k3-j722s-evm.dts | 8 + arch/arm64/boot/dts/ti/k3-j722s-main.dtsi | 4 + .../boot/dts/ti/k3-j784s4-j742s2-main-common.dtsi | 2 +- arch/um/Makefile | 1 + drivers/char/tpm/tpm-buf.c | 6 +- drivers/dma/idxd/cdev.c | 4 +- drivers/gpio/gpio-virtuser.c | 12 +- .../dc/dml2/dml21/dml21_translation_helper.c | 20 +- drivers/gpu/drm/amd/display/dc/link/link_dpms.c | 13 +- drivers/gpu/drm/xe/regs/xe_gt_regs.h | 1 + drivers/gpu/drm/xe/xe_lrc.c | 4 +- drivers/gpu/drm/xe/xe_lrc_types.h | 4 +- drivers/gpu/drm/xe/xe_wa.c | 4 + drivers/hid/hid-ids.h | 4 + drivers/hid/hid-quirks.c | 2 + drivers/net/can/kvaser_pciefd.c | 83 ++++--- drivers/net/ethernet/ti/am65-cpsw-nuss.c | 2 +- drivers/nvme/host/pci.c | 2 + drivers/perf/arm-cmn.c | 11 +- drivers/phy/rockchip/phy-rockchip-samsung-hdptx.c | 2 + drivers/phy/starfive/phy-jh7110-usb.c | 7 + drivers/platform/x86/fujitsu-laptop.c | 33 ++- drivers/platform/x86/thinkpad_acpi.c | 7 + drivers/spi/spi-sun4i.c | 5 +- fs/coredump.c | 65 +++++- fs/nfs/client.c | 2 + fs/nfs/dir.c | 15 +- fs/nfs/filelayout/filelayoutdev.c | 6 +- fs/nfs/flexfilelayout/flexfilelayoutdev.c | 6 +- fs/nfs/pnfs.h | 4 +- fs/nfs/pnfs_nfs.c | 9 +- fs/smb/server/oplock.c | 7 +- include/linux/coredump.h | 1 + include/linux/nfs_fs_sb.h | 12 +- net/sched/sch_hfsc.c | 9 +- sound/pci/hda/patch_realtek.c | 5 +- 57 files changed, 408 insertions(+), 355 deletions(-)
On 6/2/25 06:47, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 6.12.32 release. There are 55 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 Wed, 04 Jun 2025 13:42:20 +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.12.32-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.12.y and the diffstat can be found below.
thanks,
greg k-h
On ARCH_BRCMSTB using 32-bit and 64-bit ARM kernels, build tested on BMIPS_GENERIC:
Tested-by: Florian Fainelli florian.fainelli@broadcom.com
Am 02.06.2025 um 15:47 schrieb Greg Kroah-Hartman:
This is the start of the stable review cycle for the 6.12.32 release. There are 55 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.
Builds, boots and works on my 2-socket Ivy Bridge Xeon E5-2697 v2 server. No dmesg oddities or regressions found.
Tested-by: Peter Schneider pschneider1968@googlemail.com
Beste Grüße, Peter Schneider
Hi Greg,
On 02/06/25 19:17, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 6.12.32 release. There are 55 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 Wed, 04 Jun 2025 13:42:20 +0000. Anything received after that time might be too late.
No problems seen on x86_64 and aarch64 with our testing.
Tested-by: Harshit Mogalapalli harshit.m.mogalapalli@oracle.com
Thanks, Harshit
On 6/2/25 06:47, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 6.12.32 release. There are 55 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 Wed, 04 Jun 2025 13:42:20 +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.12.32-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.12.y and the diffstat can be found below.
thanks,
greg k-h
Built and booted successfully on RISC-V RV64 (HiFive Unmatched).
Tested-by: Ron Economos re@w6rz.net
On Mon, Jun 02, 2025 at 03:47:17PM +0200, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 6.12.32 release. There are 55 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.
Tested-by: Mark Brown broonie@kernel.org
On Mon, 2 Jun 2025 at 19:31, Greg Kroah-Hartman gregkh@linuxfoundation.org wrote:
This is the start of the stable review cycle for the 6.12.32 release. There are 55 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 Wed, 04 Jun 2025 13:42:20 +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.12.32-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.12.y and the diffstat can be found below.
thanks,
greg k-h
Results from Linaro’s test farm. No regressions on arm64, arm, x86_64, and i386.
Tested-by: Linux Kernel Functional Testing lkft@linaro.org
## Build * kernel: 6.12.32-rc1 * git: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git * git commit: ce2ebbe0294cb1fbd36bf75316d94f81f26e582b * git describe: v6.12.31-56-gce2ebbe0294c * test details: https://qa-reports.linaro.org/lkft/linux-stable-rc-linux-6.12.y/build/v6.12....
## Test Regressions (compared to v6.12.30-627-g3fc6e1848884)
## Metric Regressions (compared to v6.12.30-627-g3fc6e1848884)
## Test Fixes (compared to v6.12.30-627-g3fc6e1848884)
## Metric Fixes (compared to v6.12.30-627-g3fc6e1848884)
## Test result summary total: 309879, pass: 285936, fail: 4866, skip: 18494, xfail: 583
## Build Summary * arc: 5 total, 5 passed, 0 failed * arm: 139 total, 137 passed, 2 failed * arm64: 57 total, 56 passed, 1 failed * i386: 18 total, 18 passed, 0 failed * mips: 34 total, 33 passed, 1 failed * parisc: 4 total, 4 passed, 0 failed * powerpc: 40 total, 40 passed, 0 failed * riscv: 25 total, 23 passed, 2 failed * s390: 22 total, 21 passed, 1 failed * sh: 5 total, 5 passed, 0 failed * sparc: 4 total, 3 passed, 1 failed * x86_64: 49 total, 48 passed, 1 failed
## Test suites summary * boot * commands * kselftest-arm64 * kselftest-breakpoints * kselftest-capabilities * kselftest-cgroup * kselftest-clone3 * kselftest-core * kselftest-cpu-hotplug * kselftest-cpufreq * kselftest-efivarfs * kselftest-exec * kselftest-fpu * kselftest-futex * kselftest-gpio * kselftest-intel_pstate * kselftest-ipc * kselftest-kcmp * kselftest-kvm * kselftest-livepatch * kselftest-membarrier * kselftest-memfd * kselftest-mincore * kselftest-mm * kselftest-mqueue * kselftest-net * kselftest-net-mptcp * kselftest-openat2 * kselftest-ptrace * kselftest-rseq * kselftest-rtc * kselftest-seccomp * kselftest-sigaltstack * kselftest-size * kselftest-tc-testing * kselftest-timers * kselftest-tmpfs * kselftest-tpm2 * kselftest-user_events * kselftest-vDSO * kselftest-x86 * kunit * kvm-unit-tests * lava * libgpiod * libhugetlbfs * log-parser-boot * log-parser-build-clang * log-parser-build-gcc * log-parser-test * ltp-capability * ltp-commands * ltp-containers * ltp-controllers * ltp-cpuhotplug * ltp-crypto * ltp-cve * ltp-dio * ltp-fcntl-locktests * ltp-fs * ltp-fs_bind * ltp-fs_perms_simple * ltp-hugetlb * ltp-ipc * ltp-math * ltp-mm * ltp-nptl * ltp-pty * ltp-sched * ltp-smoke * ltp-syscalls * ltp-tracing * modules * perf * rcutorture * rt-tests-cyclicdeadline * rt-tests-pi-stress * rt-tests-pmqtest * rt-tests-rt-migrate-test * rt-tests-signaltest
-- Linaro LKFT https://lkft.linaro.org
On Mon, Jun 2, 2025 at 10:05 AM Greg Kroah-Hartman gregkh@linuxfoundation.org wrote:
This is the start of the stable review cycle for the 6.12.32 release. There are 55 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 Wed, 04 Jun 2025 13:42:20 +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.12.32-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.12.y and the diffstat can be found below.
thanks,
greg k-h
Builds successfully. Boots and works on qemu and Dell XPS 15 9520 w/ Intel Core i7-12600H
Tested-by: Brett Mastbergen bmastbergen@ciq.com
Thanks, Brett
On 6/2/25 07:47, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 6.12.32 release. There are 55 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 Wed, 04 Jun 2025 13:42:20 +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.12.32-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.12.y and the diffstat can be found below.
thanks,
greg k-h
Compiled and booted on my test system. No dmesg regressions.
Tested-by: Shuah Khan skhan@linuxfoundation.org
thanks, -- Shuah
The kernel, bpf tool, and perf tool builds fine for v6.12.32-rc1 on x86 and arm64 Azure VM.
Kernel binary size for x86 build: text data bss dec hex filename 29859850 17724758 6385664 53970272 3378560 vmlinux
Kernel binary size for arm64 build: text data bss dec hex filename 36415263 15006501 1052880 52474644 320b314 vmlinux
Tested-by: Hardik Garg hargar@linux.microsoft.com
Thanks, Hardik
On Mon, 02 Jun 2025 15:47:17 +0200, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 6.12.32 release. There are 55 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 Wed, 04 Jun 2025 13:42:20 +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.12.32-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.12.y and the diffstat can be found below.
thanks,
greg k-h
Failures detected for Tegra ...
Test results for stable-v6.12: 10 builds: 10 pass, 0 fail 28 boots: 28 pass, 0 fail 116 tests: 115 pass, 1 fail
Linux version: 6.12.32-rc1-gce2ebbe0294c Boards tested: tegra124-jetson-tk1, tegra186-p2771-0000, tegra186-p3509-0000+p3636-0001, tegra194-p2972-0000, tegra194-p3509-0000+p3668-0000, tegra20-ventana, tegra210-p2371-2180, tegra210-p3450-0000, tegra30-cardhu-a04
Test failures: tegra186-p2771-0000: pm-system-suspend.sh
Jon
Hi Greg,
On 04/06/2025 10:41, Jon Hunter wrote:
On Mon, 02 Jun 2025 15:47:17 +0200, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 6.12.32 release. There are 55 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 Wed, 04 Jun 2025 13:42:20 +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.12.32-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.12.y and the diffstat can be found below.
thanks,
greg k-h
Failures detected for Tegra ...
Test results for stable-v6.12: 10 builds: 10 pass, 0 fail 28 boots: 28 pass, 0 fail 116 tests: 115 pass, 1 fail
Linux version: 6.12.32-rc1-gce2ebbe0294c Boards tested: tegra124-jetson-tk1, tegra186-p2771-0000, tegra186-p3509-0000+p3636-0001, tegra194-p2972-0000, tegra194-p3509-0000+p3668-0000, tegra20-ventana, tegra210-p2371-2180, tegra210-p3450-0000, tegra30-cardhu-a04
Test failures: tegra186-p2771-0000: pm-system-suspend.sh
I have been looking at this and this appears to be an intermittent failure that has crept in. Bisect is point to the following change which landed in v6.12.31 and we did not catch it ...
# first bad commit: [d95fdee2253e612216e72f29c65b92ec42d254eb] cpufreq: tegra186: Share policy per cluster
I have tested v6.15 which has this change and I don't see the same issue there. I have also tested v6.6.y because this was backported to the various stable branches and I don't see any problems there. Only v6.12.y appears to be impacted which is odd (although this test only runs on v6.6+ kernels for this board). However, the testing is conclusive that this change is a problem for v6.12.y.
So I think we do need to revert the above change for v6.12.y but I am not sure if it makes sense to revert for earlier stable branches too?
Let me know your thoughts.
However, given that this is not a new failure for this stable update we can handle in subsequent updates. So for this update ...
Tested-by: Jon Hunter jonathanh@nvidia.com
Cheers Jon
On Wed, Jun 04, 2025 at 10:57:29AM +0100, Jon Hunter wrote:
Hi Greg,
On 04/06/2025 10:41, Jon Hunter wrote:
On Mon, 02 Jun 2025 15:47:17 +0200, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 6.12.32 release. There are 55 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 Wed, 04 Jun 2025 13:42:20 +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.12.32-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.12.y and the diffstat can be found below.
thanks,
greg k-h
Failures detected for Tegra ...
Test results for stable-v6.12: 10 builds: 10 pass, 0 fail 28 boots: 28 pass, 0 fail 116 tests: 115 pass, 1 fail
Linux version: 6.12.32-rc1-gce2ebbe0294c Boards tested: tegra124-jetson-tk1, tegra186-p2771-0000, tegra186-p3509-0000+p3636-0001, tegra194-p2972-0000, tegra194-p3509-0000+p3668-0000, tegra20-ventana, tegra210-p2371-2180, tegra210-p3450-0000, tegra30-cardhu-a04
Test failures: tegra186-p2771-0000: pm-system-suspend.sh
I have been looking at this and this appears to be an intermittent failure that has crept in. Bisect is point to the following change which landed in v6.12.31 and we did not catch it ...
# first bad commit: [d95fdee2253e612216e72f29c65b92ec42d254eb] cpufreq: tegra186: Share policy per cluster
I have tested v6.15 which has this change and I don't see the same issue there. I have also tested v6.6.y because this was backported to the various stable branches and I don't see any problems there. Only v6.12.y appears to be impacted which is odd (although this test only runs on v6.6+ kernels for this board). However, the testing is conclusive that this change is a problem for v6.12.y.
So I think we do need to revert the above change for v6.12.y but I am not sure if it makes sense to revert for earlier stable branches too?
Yes, let's revert it for the older ones as well as it would look odd, and our tools might notice that we had "skipped" a stable release tree.
Can you send the revert or do you need us to?
Let me know your thoughts.
However, given that this is not a new failure for this stable update we can handle in subsequent updates. So for this update ...
Tested-by: Jon Hunter jonathanh@nvidia.com
Wonderful, thanks for testing!
greg k-h
On 04/06/2025 11:19, Greg Kroah-Hartman wrote:
On Wed, Jun 04, 2025 at 10:57:29AM +0100, Jon Hunter wrote:
Hi Greg,
On 04/06/2025 10:41, Jon Hunter wrote:
On Mon, 02 Jun 2025 15:47:17 +0200, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 6.12.32 release. There are 55 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 Wed, 04 Jun 2025 13:42:20 +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.12.32-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.12.y and the diffstat can be found below.
thanks,
greg k-h
Failures detected for Tegra ...
Test results for stable-v6.12: 10 builds: 10 pass, 0 fail 28 boots: 28 pass, 0 fail 116 tests: 115 pass, 1 fail
Linux version: 6.12.32-rc1-gce2ebbe0294c Boards tested: tegra124-jetson-tk1, tegra186-p2771-0000, tegra186-p3509-0000+p3636-0001, tegra194-p2972-0000, tegra194-p3509-0000+p3668-0000, tegra20-ventana, tegra210-p2371-2180, tegra210-p3450-0000, tegra30-cardhu-a04
Test failures: tegra186-p2771-0000: pm-system-suspend.sh
I have been looking at this and this appears to be an intermittent failure that has crept in. Bisect is point to the following change which landed in v6.12.31 and we did not catch it ...
# first bad commit: [d95fdee2253e612216e72f29c65b92ec42d254eb] cpufreq: tegra186: Share policy per cluster
I have tested v6.15 which has this change and I don't see the same issue there. I have also tested v6.6.y because this was backported to the various stable branches and I don't see any problems there. Only v6.12.y appears to be impacted which is odd (although this test only runs on v6.6+ kernels for this board). However, the testing is conclusive that this change is a problem for v6.12.y.
So I think we do need to revert the above change for v6.12.y but I am not sure if it makes sense to revert for earlier stable branches too?
Yes, let's revert it for the older ones as well as it would look odd, and our tools might notice that we had "skipped" a stable release tree.
Can you send the revert or do you need us to?
I can no problem. Do you need a revert for each stable branch or just one email with the commit to revert for each stable branch?
Jon
On Wed, Jun 04, 2025 at 11:22:53AM +0100, Jon Hunter wrote:
On 04/06/2025 11:19, Greg Kroah-Hartman wrote:
On Wed, Jun 04, 2025 at 10:57:29AM +0100, Jon Hunter wrote:
Hi Greg,
On 04/06/2025 10:41, Jon Hunter wrote:
On Mon, 02 Jun 2025 15:47:17 +0200, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 6.12.32 release. There are 55 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 Wed, 04 Jun 2025 13:42:20 +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.12.32-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.12.y and the diffstat can be found below.
thanks,
greg k-h
Failures detected for Tegra ...
Test results for stable-v6.12: 10 builds: 10 pass, 0 fail 28 boots: 28 pass, 0 fail 116 tests: 115 pass, 1 fail
Linux version: 6.12.32-rc1-gce2ebbe0294c Boards tested: tegra124-jetson-tk1, tegra186-p2771-0000, tegra186-p3509-0000+p3636-0001, tegra194-p2972-0000, tegra194-p3509-0000+p3668-0000, tegra20-ventana, tegra210-p2371-2180, tegra210-p3450-0000, tegra30-cardhu-a04
Test failures: tegra186-p2771-0000: pm-system-suspend.sh
I have been looking at this and this appears to be an intermittent failure that has crept in. Bisect is point to the following change which landed in v6.12.31 and we did not catch it ...
# first bad commit: [d95fdee2253e612216e72f29c65b92ec42d254eb] cpufreq: tegra186: Share policy per cluster
I have tested v6.15 which has this change and I don't see the same issue there. I have also tested v6.6.y because this was backported to the various stable branches and I don't see any problems there. Only v6.12.y appears to be impacted which is odd (although this test only runs on v6.6+ kernels for this board). However, the testing is conclusive that this change is a problem for v6.12.y.
So I think we do need to revert the above change for v6.12.y but I am not sure if it makes sense to revert for earlier stable branches too?
Yes, let's revert it for the older ones as well as it would look odd, and our tools might notice that we had "skipped" a stable release tree.
Can you send the revert or do you need us to?
I can no problem. Do you need a revert for each stable branch or just one email with the commit to revert for each stable branch?
Which ever is easier for you, I can handle the git id "fixups" when applying them to the different branches if you don't want to have to dig for them.
thanks,
greg k-h
On Wed, Jun 04, 2025 at 02:41:11AM -0700, Jon Hunter wrote:
On Mon, 02 Jun 2025 15:47:17 +0200, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 6.12.32 release. There are 55 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 Wed, 04 Jun 2025 13:42:20 +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.12.32-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.12.y and the diffstat can be found below.
thanks,
greg k-h
Failures detected for Tegra ...
Test results for stable-v6.12: 10 builds: 10 pass, 0 fail 28 boots: 28 pass, 0 fail 116 tests: 115 pass, 1 fail
Linux version: 6.12.32-rc1-gce2ebbe0294c Boards tested: tegra124-jetson-tk1, tegra186-p2771-0000, tegra186-p3509-0000+p3636-0001, tegra194-p2972-0000, tegra194-p3509-0000+p3668-0000, tegra20-ventana, tegra210-p2371-2180, tegra210-p3450-0000, tegra30-cardhu-a04
Test failures: tegra186-p2771-0000: pm-system-suspend.sh
Any hints as to what is causing the failure?
thanks,
greg k-h
On 04/06/2025 10:58, Greg Kroah-Hartman wrote:
On Wed, Jun 04, 2025 at 02:41:11AM -0700, Jon Hunter wrote:
On Mon, 02 Jun 2025 15:47:17 +0200, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 6.12.32 release. There are 55 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 Wed, 04 Jun 2025 13:42:20 +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.12.32-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.12.y and the diffstat can be found below.
thanks,
greg k-h
Failures detected for Tegra ...
Test results for stable-v6.12: 10 builds: 10 pass, 0 fail 28 boots: 28 pass, 0 fail 116 tests: 115 pass, 1 fail
Linux version: 6.12.32-rc1-gce2ebbe0294c Boards tested: tegra124-jetson-tk1, tegra186-p2771-0000, tegra186-p3509-0000+p3636-0001, tegra194-p2972-0000, tegra194-p3509-0000+p3668-0000, tegra20-ventana, tegra210-p2371-2180, tegra210-p3450-0000, tegra30-cardhu-a04
Test failures: tegra186-p2771-0000: pm-system-suspend.sh
Any hints as to what is causing the failure?
Yes, I had just responded to my initial email reporting the failure with the details when you sent this.
Cheers Jon
-
Brett Mastbergen -
Florian Fainelli -
Greg Kroah-Hartman -
Hardik Garg -
Harshit Mogalapalli -
Jon Hunter -
Mark Brown -
Naresh Kamboju -
Peter Schneider -
Ron Economos -
Shuah Khan