June 2025 - Lkft-triage - lists.linaro.org

by Greg Kroah-Hartman

This is the start of the stable review cycle for the 6.15.2 release. There are 34 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 Mon, 09 Jun 2025 10:07:05 +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.15.2-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.15.y and the diffstat can be found below. thanks, greg k-h ------------- Pseudo-Shortlog of commits: Greg Kroah-Hartman <gregkh(a)linuxfoundation.org> Linux 6.15.2-rc1 Aurabindo Pillai <aurabindo.pillai(a)amd.com> Revert "drm/amd/display: more liberal vmin/vmax update for freesync" Xu Yang <xu.yang_2(a)nxp.com> dt-bindings: phy: imx8mq-usb: fix fsl,phy-tx-vboost-level-microvolt property Lukasz Czechowski <lukasz.czechowski(a)thaumatec.com> dt-bindings: usb: cypress,hx3: Add support for all variants Krzysztof Kozlowski <krzysztof.kozlowski(a)linaro.org> dt-bindings: remoteproc: qcom,sm8150-pas: Add missing SC8180X compatible David Lechner <dlechner(a)baylibre.com> dt-bindings: pwm: adi,axi-pwmgen: Fix clocks Sergey Senozhatsky <senozhatsky(a)chromium.org> thunderbolt: Do not double dequeue a configuration request Carlos Llamas <cmllamas(a)google.com> binder: fix yet another UAF in binder_devices Dmitry Antipov <dmantipov(a)yandex.ru> binder: fix use-after-free in binderfs_evict_inode() Dave Penkler <dpenkler(a)gmail.com> usb: usbtmc: Fix timeout value in get_stb Arnd Bergmann <arnd(a)arndb.de> nvmem: rmem: select CONFIG_CRC32 Dustin Lundquist <dustin(a)null-ptr.net> serial: jsm: fix NPE during jsm_uart_port_init Bartosz Golaszewski <bartosz.golaszewski(a)linaro.org> Bluetooth: hci_qca: move the SoC type check to the right place Qasim Ijaz <qasdev00(a)gmail.com> usb: typec: ucsi: fix Clang -Wsign-conversion warning Charles Yeh <charlesyeh522(a)gmail.com> USB: serial: pl2303: add new chip PL2303GC-Q20 and PL2303GT-2AB Hongyu Xie <xiehongyu1(a)kylinos.cn> usb: storage: Ignore UAS driver for SanDisk 3.2 Gen2 storage device Jiayi Li <lijiayi(a)kylinos.cn> usb: quirks: Add NO_LPM quirk for SanDisk Extreme 55AE Kent Overstreet <kent.overstreet(a)linux.dev> bcachefs: Fix subvol to missing root repair Kent Overstreet <kent.overstreet(a)linux.dev> bcachefs: Run may_delete_deleted_inode() checks in bch2_inode_rm() Kent Overstreet <kent.overstreet(a)linux.dev> bcachefs: delete dead code from may_delete_deleted_inode() Kent Overstreet <kent.overstreet(a)linux.dev> bcachefs: Repair code for directory i_size Kent Overstreet <kent.overstreet(a)linux.dev> bcachefs: Kill un-reverted directory i_size code Alexandre Mergnat <amergnat(a)baylibre.com> rtc: Fix offset calculation for .start_secs < 0 Alexandre Mergnat <amergnat(a)baylibre.com> rtc: Make rtc_time64_to_tm() support dates before 1970 Nícolas F. R. A. Prado <nfraprado(a)collabora.com> pinctrl: mediatek: eint: Fix invalid pointer dereference for v1 platforms Sakari Ailus <sakari.ailus(a)linux.intel.com> Documentation: ACPI: Use all-string data node references Gautham R. Shenoy <gautham.shenoy(a)amd.com> acpi-cpufreq: Fix nominal_freq units to KHz in get_max_boost_ratio() Pritam Manohar Sutar <pritam.sutar(a)samsung.com> clk: samsung: correct clock summary for hsi1 block Gabor Juhos <j4g8y7(a)gmail.com> pinctrl: armada-37xx: set GPIO output value before setting direction Gabor Juhos <j4g8y7(a)gmail.com> pinctrl: armada-37xx: use correct OUTPUT_VAL register for GPIOs > 31 Ahmed Salem <x0rw3ll(a)gmail.com> ACPICA: Apply ACPI_NONSTRING in more places Kees Cook <kees(a)kernel.org> ACPICA: Apply ACPI_NONSTRING Kees Cook <kees(a)kernel.org> ACPICA: Introduce ACPI_NONSTRING Rafael J. Wysocki <rafael.j.wysocki(a)intel.com> Revert "x86/smp: Eliminate mwait_play_dead_cpuid_hint()" Pan Taixi <pantaixi(a)huaweicloud.com> tracing: Fix compilation warning on arm32 ------------- Diffstat: .../bindings/phy/fsl,imx8mq-usb-phy.yaml | 3 +- .../devicetree/bindings/pwm/adi,axi-pwmgen.yaml | 13 +++- .../bindings/remoteproc/qcom,sm8150-pas.yaml | 3 + .../devicetree/bindings/usb/cypress,hx3.yaml | 19 +++++- .../acpi/dsd/data-node-references.rst | 26 ++++---- Documentation/firmware-guide/acpi/dsd/graph.rst | 11 ++-- Documentation/firmware-guide/acpi/dsd/leds.rst | 7 +- Makefile | 4 +- arch/x86/kernel/smpboot.c | 54 +++++++++++++-- drivers/acpi/acpica/acdebug.h | 2 +- drivers/acpi/acpica/aclocal.h | 4 +- drivers/acpi/acpica/nsnames.c | 2 +- drivers/acpi/acpica/nsrepair2.c | 2 +- drivers/android/binder.c | 16 ++++- drivers/android/binder_internal.h | 8 ++- drivers/android/binderfs.c | 2 +- drivers/bluetooth/hci_qca.c | 14 ++-- drivers/clk/samsung/clk-exynosautov920.c | 2 +- drivers/cpufreq/acpi-cpufreq.c | 2 +- drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c | 16 ++--- drivers/nvmem/Kconfig | 1 + drivers/pinctrl/mediatek/mtk-eint.c | 26 ++++---- drivers/pinctrl/mediatek/mtk-eint.h | 5 +- drivers/pinctrl/mediatek/pinctrl-mtk-common-v2.c | 2 +- drivers/pinctrl/mediatek/pinctrl-mtk-common.c | 2 +- drivers/pinctrl/mvebu/pinctrl-armada-37xx.c | 14 ++-- drivers/rtc/class.c | 2 +- drivers/rtc/lib.c | 24 +++++-- drivers/thunderbolt/ctl.c | 5 ++ drivers/tty/serial/jsm/jsm_tty.c | 1 + drivers/usb/class/usbtmc.c | 4 +- drivers/usb/core/quirks.c | 3 + drivers/usb/serial/pl2303.c | 2 + drivers/usb/storage/unusual_uas.h | 7 ++ drivers/usb/typec/ucsi/ucsi.h | 2 +- fs/bcachefs/dirent.c | 12 +--- fs/bcachefs/dirent.h | 4 +- fs/bcachefs/errcode.h | 2 + fs/bcachefs/fs.c | 8 ++- fs/bcachefs/fsck.c | 8 +++ fs/bcachefs/inode.c | 77 ++++++++++++++-------- fs/bcachefs/namei.c | 4 +- fs/bcachefs/sb-errors_format.h | 4 +- fs/bcachefs/subvolume.c | 19 ++++-- include/acpi/actbl.h | 6 +- include/acpi/actypes.h | 4 ++ include/acpi/platform/acgcc.h | 8 +++ kernel/trace/trace.c | 2 +- .../acpi/os_specific/service_layers/oslinuxtbl.c | 2 +- tools/power/acpi/tools/acpidump/apfiles.c | 2 +- 50 files changed, 314 insertions(+), 158 deletions(-)

1 week, 5 days

12
11
0 0

Daily cts/vts report for lkft - 2025-Jun-12

by lava＠validation.linaro.org

Total jobs: 269 Total errors: 88 (32.71%) LAVA errors: 0 (0.00%) Test errors: 41 (15.24%) Job errors: 44 (16.36%) Infra errors: 3 (1.12%) Canceled jobs: 0 (0.00%) Device type: dragonboard-845c Total jobs: 168 Total errors: 57 (33.93%) Error type: Job Error count: 44 (26.19%) Error: No match for error type 'Job', message 'login-action timed out after 873 seconds' Count: 25 (14.88%) IDs: db845c-01: 8309083 8310473 8310551 8310555 8310577 8310580 8310585 8310589 8310593 8310625 8311104 8311122 8311129 8311182 8311196 8311229 8311265 8311266 8311271 8311323 8311635 8311638 8311797 8311804 8311870 Error: No match for error type 'Job', message 'login-action timed out after 872 seconds' Count: 9 (5.36%) IDs: db845c-01: 8311161 8311192 8311195 8311280 8311289 8311629 8311800 8311801 8311806 Error: No match for error type 'Job', message 'login-action timed out after 799 seconds' Count: 1 (0.60%) IDs: db845c-01: 8311633 Error: No match for error type 'Job', message 'login-action timed out after 874 seconds' Count: 1 (0.60%) IDs: db845c-01: 8311308 Error: No match for error type 'Job', message 'login-action timed out after 875 seconds' Count: 1 (0.60%) IDs: db845c-01: 8310616 Error: No match for error type 'Job', message 'login-action timed out after 871 seconds' Count: 1 (0.60%) IDs: db845c-01: 8310554 Error: No match for error type 'Job', message 'login-action timed out after 762 seconds' Count: 1 (0.60%) IDs: db845c-01: 8310549 Error: No match for error type 'Job', message 'login-action timed out after 826 seconds' Count: 1 (0.60%) IDs: db845c-01: 8310548 Error: No match for error type 'Job', message 'lava-create-overlay timed out after 300 seconds' Count: 1 (0.60%) IDs: db845c-04: 8310483 Error: No match for error type 'Job', message 'login-action timed out after 827 seconds' Count: 1 (0.60%) IDs: db845c-01: 8310476 Error: No match for error type 'Job', message 'test-definition timed out after 14 seconds' Count: 1 (0.60%) IDs: db845c-07: 8310445 Error: No match for error type 'Job', message 'login-action timed out after 823 seconds' Count: 1 (0.60%) IDs: db845c-01: 8296979 Error type: Test Error count: 12 (7.14%) Error: No match for error type 'Test', message 'lava-docker-test-shell timed out after 598 seconds' Count: 5 (2.98%) IDs: db845c-02: 8310442 8310500 8311618 8311660 db845c-07: 8310534 Error: Device NOT found! Count: 2 (1.19%) IDs: db845c-02: 8311245 db845c-03: 8311644 Error: No match for error type 'Test', message 'tradefed - adb device lost[dd3b965f]' Count: 3 (1.79%) IDs: db845c-02: 8296980 8311222 8311317 Error: No match for error type 'Test', message 'lava-docker-test-shell timed out after 596 seconds' Count: 1 (0.60%) IDs: db845c-02: 8310421 Error: No match for error type 'Test', message 'lava-docker-test-shell timed out after 594 seconds' Count: 1 (0.60%) IDs: db845c-07: 8300945 Error type: Infrastructure Error count: 1 (0.60%) Error: Connection closed Count: 1 (0.60%) IDs: db845c-08: 8310416 Device type: qrb5165-rb5 Total jobs: 73 Total errors: 17 (23.29%) Error type: Infrastructure Error count: 2 (2.74%) Error: fastboot-flash-action timed out Count: 1 (1.37%) IDs: rb5-06: 8311692 Error: Connection closed Count: 1 (1.37%) IDs: rb5-01: 8311653 Error type: Test Error count: 15 (20.55%) Error: No match for error type 'Test', message 'lava-docker-test-shell timed out after 598 seconds' Count: 11 (15.07%) IDs: rb5-03: 8310509 8310516 8310567 8310581 8311116 8311150 8311205 8311206 8311251 8311264 rb5-07: 8311677 Error: No match for error type 'Test', message 'tradefed - adb device lost[74d67c95]' Count: 1 (1.37%) IDs: rb5-03: 8311657 Error: No match for error type 'Test', message 'lava-docker-test-shell timed out after 298 seconds' Count: 1 (1.37%) IDs: rb5-01: 8311146 Error: Device NOT found! Count: 2 (2.74%) IDs: rb5-03: 8310515 8310596 Device type: sm8550-hdk Total jobs: 28 Total errors: 14 (50.00%) Error type: Test Error count: 14 (50.00%) Error: No match for error type 'Test', message 'The network seems not available, as the ping command failed' Count: 1 (3.57%) IDs: sm8550-hdk-01: 8311167 Error: Device NOT found! Count: 5 (17.86%) IDs: sm8550-hdk-01: 8303753 8303755 8304112 8304823 8305588 Error: No match for error type 'Test', message 'lava-docker-test-shell timed out after 599 seconds' Count: 5 (17.86%) IDs: sm8550-hdk-01: 8303752 8304824 8304826 8304869 8305586 Error: No match for error type 'Test', message 'tradefed - adb device lost[124d1c34]' Count: 3 (10.71%) IDs: sm8550-hdk-01: 8303757 8304104 8304105

1 week, 5 days

1
0
0 0

Daily report for validation - 2025-Jun-12

by lava＠validation.linaro.org

Total jobs: 74 Total errors: 1 (1.35%) LAVA errors: 0 (0.00%) Test errors: 0 (0.00%) Job errors: 1 (1.35%) Infra errors: 0 (0.00%) Canceled jobs: 0 (0.00%) Device type: beaglebone-black Total jobs: 41 Total errors: 0 (0.00%) Device type: x15 Total jobs: 32 Total errors: 1 (3.12%) Error type: Job Error count: 1 (3.12%) Error: No match for error type 'Job', message 'login-action timed out after 274 seconds' Count: 1 (3.12%) IDs: x15-01: 4153082 Device type: imx93-11x11-evk Total jobs: 1 Total errors: 0 (0.00%)

1 week, 5 days

1
0
0 0

selftests/filesystem: clang warning null passed to a callee that requires a non-null argument [-Wnonnull]

by Naresh Kamboju

Regressions found on arm, arm64 and x86_64 building warnings with clang-20 and clang-nightly started from Linux next-20250603 Regressions found on arm, arm64 and x86_64 - selftests/filesystem Regression Analysis: - New regression? Yes - Reproducible? Yes First seen on the next-20250603 Good: next-20250530 Bad: next-20250603 Test regression: arm arm64 x86_64 clang warning null passed to a callee that requires a non-null argument [-Wnonnull] Reported-by: Linux Kernel Functional Testing <lkft(a)linaro.org> ## Build warnings make[4]: Entering directory '/builds/linux/tools/testing/selftests/filesystems' CC devpts_pts CC file_stressor CC anon_inode_test anon_inode_test.c:45:37: warning: null passed to a callee that requires a non-null argument [-Wnonnull] 45 | ASSERT_LT(execveat(fd_context, "", NULL, NULL, AT_EMPTY_PATH), 0); | ^~~~ ## Source * Kernel version: 6.15.0-next-20250605 * Git tree: https://kernel.googlesource.com/pub/scm/linux/kernel/git/next/linux-next.git * Git sha: a0bea9e39035edc56a994630e6048c8a191a99d8 * Toolchain: Debian clang version 21.0.0 (++20250529012636+c474f8f2404d-1~exp1~20250529132821.1479) ## Build * Test log: https://qa-reports.linaro.org/api/testruns/28651387/log_file/ * Build link: https://storage.tuxsuite.com/public/linaro/lkft/builds/2xzM4wMl8SvuLKE3mw3c… * Kernel config: https://storage.tuxsuite.com/public/linaro/lkft/builds/2xzM4wMl8SvuLKE3mw3c… -- Linaro LKFT https://lkft.linaro.org

1 week, 6 days

3
3
0 0

next-20250610: arm64 No rule to make target rockchip rk3399-rockpro64-screen.dtso

by Naresh Kamboju

Regression while building arm64 with the Linux next-20250610 the following dtb build errors noticed. Regressions found on arm64 builds - dtb build error Regression Analysis: - New regression? Yes - Reproducibility? Yes First seen on the next-20250610 Good: next-20250606 Bad: next-20250610 Anders bisected this to, # first bad commit: [49760b9f60528393cca3ea35c4d0719f84215a48] arm64: dts: rockchip: add overlay for RockPro64 screen Build regression: arm64 No rule to make target rockchip rk3399-rockpro64-screen.dtso Reported-by: Linux Kernel Functional Testing <lkft(a)linaro.org> ## Build error *** No rule to make target 'arch/arm64/boot/dts/rockchip/rk3399-rockpro64-screen.dtso', needed by '__dtbs_install'. ## Source * Kernel version: 6.16.0-rc1 * Git tree: https://kernel.googlesource.com/pub/scm/linux/kernel/git/next/linux-next.git * Git sha: b27cc623e01be9de1580eaa913508b237a7a9673 * git describe: next-20250610 * Toolchains: gcc-8, gcc-13, clang-20 * Config: defconfig * Architecture: arm64 ## Build details * Build warning: https://storage.tuxsuite.com/public/linaro/lkft/builds/2yJ4IOQa1XxMqDgmzjEl… * Build link: https://storage.tuxsuite.com/public/linaro/lkft/builds/2yJ4IOQa1XxMqDgmzjEl… * Kernel config: https://storage.tuxsuite.com/public/linaro/lkft/builds/2yJ4IOQa1XxMqDgmzjEl… ## Steps to reproduce - tuxmake --runtime podman --target-arch arm64 --toolchain gcc-13 --kconfig defconfig -- Linaro LKFT https://lkft.linaro.org

1 week, 6 days

3
3
0 0

Daily report for validation - 2025-Jun-11

by lava＠validation.linaro.org

Total jobs: 76 Total errors: 3 (3.95%) LAVA errors: 0 (0.00%) Test errors: 0 (0.00%) Job errors: 3 (3.95%) Infra errors: 0 (0.00%) Canceled jobs: 0 (0.00%) Device type: x15 Total jobs: 34 Total errors: 3 (8.82%) Error type: Job Error count: 3 (8.82%) Error: No match for error type 'Job', message 'login-action timed out after 275 seconds' Count: 2 (5.88%) IDs: x15-01: 4152841 4152985 Error: No match for error type 'Job', message 'login-action timed out after 273 seconds' Count: 1 (2.94%) IDs: x15-01: 4152838 Device type: beaglebone-black Total jobs: 41 Total errors: 0 (0.00%) Device type: imx93-11x11-evk Total jobs: 1 Total errors: 0 (0.00%)

1 week, 6 days

1
0
0 0

Need Help Understanding Boot Failure Logs in LKFT Reports

by olivia christ

Hey all, I'm working with LKFT (Linaro Kernel Functional Testing) results and found multiple test reports showing boot failures for a few kernel revisions. I'm trying to figure out the best way to interpret the boot logs properly and identify if the changes made in the kernel or the device related configuration caused the failure. I've looked through the notable logs on the LKFT dashboard, but some of it's a little vague especially where the log ends abruptly after the kernel starts initializing the drivers. I'm wondering if it could be DT or defconfig mismatches - but not sure. Can anyone help me with the following: Best practices to debug such boot failures using LKFT logs? Any specific kernel configs or recent upstream patches that are known to cause these failures? you can also check this website:https://www.igmguru.com/machine-learning-ai/generative-ai-training I'm relatively new to this, so I would appreciate any information and/or pointers to previous discussions, if possible. Appreciate any help and thanks in advance! Regards, olivia

1 week, 6 days

1
0
0 0

Issue with Kernel Test Failures in Recent Builds

by olivia christ

Hi LKFT team, I hope all is well. I have been running kernel tests from the latest builds (kernel 5.x) on our CI environment, and there are several failures I have repeated. It looks like these failures are related to the memory management subsystem. The specific failure I continue to see relates to kmemleak not initializing on some architectures and there are also memory leak test failures. Has anyone seen similar behaviour in the new Linaro builds or noticed a change in reliability with tests here? If so, I would appreciate any information or thoughts you may have about possible workarounds/fixes. Also, are there existing configuration flags or patches that we should think about turning on and/or enabling to mitigate this issue until the underlying problem is fixed? Thank you in advance for your help! Best, olivia

2 weeks

2
1
0 0

Juno-r2 WARNING kernel time clockevents.c cev_delta2ns clockevents_config.part

by Naresh Kamboju

Regression while booting Juno-r2 with the Linux next-20250606 the following kernel warnings found. This boot warning was reproduced with juno-r2.dtb and juno-r2-scmi.dtb. Regressions found on Juno-r2 - boot warning Regression Analysis: - New regression? Yes - Reproducibility? Yes First seen on the next-20250606 Good: next-20250512 Bad: next-20250606 The suspected patch that found between tags is, # git show next-20250512..next-20250513 -- arch/arm64/boot/dts/arm/juno-base.dtsi commit 1fa3ed04ac55134063e3cd465b41aeb26715e52a Author: Sudeep Holla <sudeep.holla(a)arm.com> Date: Mon May 12 11:11:32 2025 +0100 arm64: dts: arm: Drop the clock-frequency property from timer nodes Drop the clock-frequency property from the timer nodes, since it must be configured by the boot/secure firmware. Cc: Liviu Dudau <liviu.dudau(a)arm.com> Cc: Lorenzo Pieralisi <lpieralisi(a)kernel.org> Cc: Mark Rutland <mark.rutland(a)arm.com> Message-Id: <20250512101132.1743920-1-sudeep.holla(a)arm.com> Signed-off-by: Sudeep Holla <sudeep.holla(a)arm.com> diff --git a/arch/arm64/boot/dts/arm/juno-base.dtsi b/arch/arm64/boot/dts/arm/juno-base.dtsi index 055764d0b9e5..9ccb80821bdb 100644 --- a/arch/arm64/boot/dts/arm/juno-base.dtsi +++ b/arch/arm64/boot/dts/arm/juno-base.dtsi @@ -10,7 +10,6 @@ / { memtimer: timer@2a810000 { compatible = "arm,armv7-timer-mem"; reg = <0x0 0x2a810000 0x0 0x10000>; - clock-frequency = <50000000>; #address-cells = <1>; #size-cells = <1>; ranges = <0 0x0 0x2a820000 0x20000>; Boot regression: Juno-r2 WARNING kernel time clockevents.c cev_delta2ns clockevents_config.part Reported-by: Linux Kernel Functional Testing <lkft(a)linaro.org> ## Boot warning [ 0.000000] timer_sp804: timer clock not found: -517 [ 0.000000] timer_sp804: arm,sp804 clock not found: -2 [ 0.000000] Failed to initialize '/bus@8000000/motherboard-bus@8000000/iofpga-bus@300000000/timer@110000': -22 [ 0.000000] timer_sp804: timer clock not found: -517 [ 0.000000] timer_sp804: arm,sp804 clock not found: -2 [ 0.000000] Failed to initialize '/bus@8000000/motherboard-bus@8000000/iofpga-bus@300000000/timer@120000': -22 [ 0.000000] arch_timer: frequency not available [ 0.000000] ------------[ cut here ]------------ [ 0.000000] WARNING: CPU: 0 PID: 0 at kernel/time/clockevents.c:38 cev_delta2ns (kernel/time/clockevents.c:38 (discriminator 1)) [ 0.000000] Modules linked in: [ 0.000000] CPU: 0 UID: 0 PID: 0 Comm: swapper/0 Not tainted 6.15.0-next-20250605 #1 PREEMPT [ 0.000000] Hardware name: ARM Juno development board (r2) (DT) [ 0.000000] pstate: 600000c5 (nZCv daIF -PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 0.000000] pc : cev_delta2ns (kernel/time/clockevents.c:38 (discriminator 1)) [ 0.000000] lr : clockevents_config.part.0 (kernel/time/clockevents.c:499) [ 0.000000] sp : ffff800082923cd0 [ 0.000000] x29: ffff800082923cd0 x28: 0000000000000400 x27: ffff800081650000 [ 0.000000] x26: ffff80008292fcc0 x25: ffff800082425888 x24: ffff8000829343c0 [ 0.000000] x23: ffff800083210000 x22: 000000000000000b x21: ffff8000823cf178 [ 0.000000] x20: ffff800082433880 x19: ffff00080021e240 x18: 0000000000000000 [ 0.000000] x17: ffff00080021a400 x16: ffff00080021a200 x15: 0000000000000100 [ 0.000000] x14: fffffdffe0008a00 x13: ffff800080000000 x12: 0000000000000000 [ 0.000000] x11: 0000000000000068 x10: 0000000000000100 x9 : ffff8000801b50f8 [ 0.000000] x8 : 000000001dcd6500 x7 : 000000003b9aca00 x6 : 0000000000000020 [ 0.000000] x5 : 0000000000000020 x4 : 0000000000000000 x3 : 0000000f00000000 [ 0.000000] x2 : 0000000000000000 x1 : ffff00080021e240 x0 : 000000000000000f [ 0.000000] Call trace: [ 0.000000] cev_delta2ns (kernel/time/clockevents.c:38 (discriminator 1)) (P) [ 0.000000] clockevents_config_and_register (kernel/time/clockevents.c:519) [ 0.000000] arch_timer_mem_frame_register (drivers/clocksource/arm_arch_timer.c:1319 drivers/clocksource/arm_arch_timer.c:1580) [ 0.000000] arch_timer_mem_of_init (drivers/clocksource/arm_arch_timer.c:1653) [ 0.000000] timer_probe (drivers/clocksource/timer-probe.c:31) [ 0.000000] time_init (arch/arm64/kernel/time.c:62) [ 0.000000] start_kernel (init/main.c:1014) [ 0.000000] __primary_switched (arch/arm64/kernel/head.S:247) [ 0.000000] ---[ end trace 0000000000000000 ]--- [ 0.000000] arch_timer: cp15 and mmio timer(s) running at 50.00MHz (phys/phys). ## Source * Kernel version: 6.15.0-next-20250513 to 6.15.0-next-20250606 * Git tree: https://kernel.googlesource.com/pub/scm/linux/kernel/git/next/linux-next.git * Git sha: 4f27f06ec12190c7c62c722e99ab6243dea81a94 * Toolchain: gcc-13 ## Boot details * Boot lava log: https://lkft.validation.linaro.org/scheduler/job/8309469#L622 * Boot log: https://qa-reports.linaro.org/api/testruns/28679128/log_file/ * Boot warning: https://regressions.linaro.org/lkft/linux-next-master/next-20250605/log-par… * Build link: https://storage.tuxsuite.com/public/linaro/lkft/builds/2y4wgEvmeoVH3Vr528M4… * Kernel config: https://storage.tuxsuite.com/public/linaro/lkft/builds/2y4wgEvmeoVH3Vr528M4… -- Linaro LKFT https://lkft.linaro.org

2 weeks

1
0
0 0

Daily cts/vts report for lkft - 2025-Jun-10

by lava＠validation.linaro.org

Total jobs: 149 Total errors: 40 (26.85%) LAVA errors: 0 (0.00%) Test errors: 34 (22.82%) Job errors: 0 (0.00%) Infra errors: 6 (4.03%) Canceled jobs: 0 (0.00%) Device type: sm8550-hdk Total jobs: 24 Total errors: 9 (37.50%) Error type: Test Error count: 9 (37.50%) Error: No match for error type 'Test', message 'The network seems not available, as the ping command failed' Count: 1 (4.17%) IDs: sm8550-hdk-01: 8309458 Error: No match for error type 'Test', message 'tradefed - adb device lost[124d1c34]' Count: 3 (12.50%) IDs: sm8550-hdk-01: 8295644 8296050 8309113 Error: No match for error type 'Test', message 'lava-docker-test-shell timed out after 599 seconds' Count: 2 (8.33%) IDs: sm8550-hdk-01: 8295593 8309103 Error: Device NOT found! Count: 3 (12.50%) IDs: sm8550-hdk-01: 8295596 8295643 8295647 Device type: qrb5165-rb5 Total jobs: 43 Total errors: 12 (27.91%) Error type: Test Error count: 6 (13.95%) Error: No match for error type 'Test', message 'lava-docker-test-shell timed out after 598 seconds' Count: 3 (6.98%) IDs: rb5-03: 8309365 rb5-07: 8308269 8309093 Error: No match for error type 'Test', message 'tradefed - adb device lost[d8a1879f]' Count: 1 (2.33%) IDs: rb5-07: 8309294 Error: Device NOT found! Count: 2 (4.65%) IDs: rb5-03: 8309278 rb5-07: 8309173 Error type: Infrastructure Error count: 6 (13.95%) Error: fastboot-flash-action timed out Count: 1 (2.33%) IDs: rb5-05: 8309335 Error: Connection closed Count: 5 (11.63%) IDs: rb5-01: 8309182 8309185 8309328 8309331 8309333 Device type: dragonboard-845c Total jobs: 64 Total errors: 3 (4.69%) Error type: Test Error count: 3 (4.69%) Error: No match for error type 'Test', message 'lava-docker-test-shell timed out after 598 seconds' Count: 2 (3.12%) IDs: db845c-07: 8309153 8309303 Error: Device NOT found! Count: 1 (1.56%) IDs: db845c-02: 8309151 Device type: hi6220-hikey-r2 Total jobs: 16 Total errors: 16 (100.00%) Error type: Test Error count: 16 (100.00%) Error: No match for error type 'Test', message 'The network seems not available, as the ping command failed' Count: 5 (31.25%) IDs: hikey-6220-r2-01: 8309199 hikey-6220-r2-05: 8309213 8309240 hikey-6220-r2-06: 8309144 8309200 Error: No match for error type 'Test', message 'tradefed - adb device lost[235D989C003B0752]' Count: 3 (18.75%) IDs: hikey-6220-r2-03: 8309071 8309116 8309218 Error: No match for error type 'Test', message 'tradefed - adb device lost[191FC75C003312EE]' Count: 1 (6.25%) IDs: hikey-6220-r2-06: 8309209 Error: No match for error type 'Test', message 'tradefed - adb device lost[4595FE84003F72FC]' Count: 3 (18.75%) IDs: hikey-6220-r2-04: 8309084 8309092 8309206 Error: No match for error type 'Test', message 'tradefed - adb device lost[8D6E5F00030E051]' Count: 1 (6.25%) IDs: hikey-6220-r2-02: 8309143 Error: No match for error type 'Test', message 'tradefed - adb device lost[7B1579B5003E507A]' Count: 1 (6.25%) IDs: hikey-6220-r2-05: 8309117 Error: No match for error type 'Test', message 'tradefed - adb device lost[2047EDF7003CEE68]' Count: 1 (6.25%) IDs: hikey-6220-r2-01: 8309115 Error: No match for error type 'Test', message 'lava-test-interactive timed out after 600 seconds' Count: 1 (6.25%) IDs: hikey-6220-r2-06: 8309090 Device type: hi960-hikey Total jobs: 2 Total errors: 0 (0.00%)

2 weeks

1
0
0 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

Lkft-triage June 2025