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

Daily report for validation - 2025-Feb-13

by lava＠validation.linaro.org

Total jobs: 15 Total errors: 12 (80.00%) LAVA errors: 0 (0.00%) Test errors: 0 (0.00%) Job errors: 12 (80.00%) Infra errors: 0 (0.00%) Canceled jobs: 0 (0.00%) Device type: dragonboard-845c Total jobs: 14 Total errors: 12 (85.71%) Error type: Job Error count: 12 (85.71%) Error: No match for error type 'Job', message 'login-action timed out after 628 seconds' Count: 1 (7.14%) IDs: dragonboard-845c-04: 4129004 Error: No match for error type 'Job', message 'login-action timed out after 873 seconds' Count: 3 (21.43%) IDs: dragonboard-845c-06: 4128826 4128874 4128985 Error: No match for error type 'Job', message 'login-action timed out after 874 seconds' Count: 7 (50.00%) IDs: dragonboard-845c-04: 4128822 4128892 4128909 4128919 dragonboard-845c-06: 4128856 4128942 4128972 Error: No match for error type 'Job', message 'login-action timed out after 875 seconds' Count: 1 (7.14%) IDs: dragonboard-845c-04: 4128848 Device type: imx93-11x11-evk Total jobs: 1 Total errors: 0 (0.00%)

8 months, 3 weeks

1
0
0 0

selftest/vDSO: vdso_test_abi tests with gcc-13 and pass with clang-19

by Naresh Kamboju

The kselftest-vDSO/vdso_test_abi test encounters failures when built and executed using GCC-13 on armv7 architecture. The issue has been observed on both TI X15 devices and QEMU-armv7. Interestingly, the same test passes without any issues when built using Clang-19.This failure is specific to GCC-13. but test case should have been failed on clang toolchain but it did not. The Clang toolchain likely defaults to the traditional 32-bit time_t on 32-bit Debian Trixie (except x86), leading to an ABI issue similar to older compilers. This is affecting compatibility. This is not a new regression, this report generated on Linux next but also seen on Linux stable tree. Test name: kselftest-vDSO/vdso_test_abi Fails: gcc-13 pass: clang-19 Arnd Bergmann investigated and proposed a patch which fixes the problem. Test regression: selftest-vDSO/vdso_test_abi: Reported-by: Linux Kernel Functional Testing <lkft(a)linaro.org> # selftests: vDSO: vdso_test_abi # TAP version 13 # 1..16 # # [vDSO kselftest] VDSO_VERSION: LINUX_2.6 # # The time is 184285885525887.-5268386858514840748 # ok 1 __vdso_gettimeofday # # clock_id: CLOCK_REALTIME # # The time is 184287230099877759.-1225334784 # ok 2 __vdso_clock_gettime CLOCK_REALTIME # # The vdso resolution is 4294967296 -1225335584 # # The syscall resolution is 4294967296 -1225334784 # not ok 3 __vdso_clock_getres CLOCK_REALTIME # # clock_id: CLOCK_BOOTTIME # # The time is 3253049749439251215.-1225334784 # ok 4 __vdso_clock_gettime CLOCK_BOOTTIME # # The vdso resolution is 4294967296 -1225335584 # # The syscall resolution is 4294967296 -1225334784 # not ok 5 __vdso_clock_getres CLOCK_BOOTTIME # # clock_id: CLOCK_TAI # # The time is 184549377723756415.-1225334784 # ok 6 __vdso_clock_gettime CLOCK_TAI # # The vdso resolution is 4294967296 -1225335584 # # The syscall resolution is 4294967296 -1225334784 # not ok 7 __vdso_clock_getres CLOCK_TAI # # clock_id: CLOCK_REALTIME_COARSE # # The time is 128974845965660031.-1225334784 # ok 8 __vdso_clock_gettime CLOCK_REALTIME_COARSE # # The vdso resolution is 42949672960000000 -1225335584 # # The syscall resolution is 42949672960000000 -1225334784 # not ok 9 __vdso_clock_getres CLOCK_REALTIME_COARSE # # clock_id: CLOCK_MONOTONIC # # The time is 3253311892768162575.-1225334784 # ok 10 __vdso_clock_gettime CLOCK_MONOTONIC # # The vdso resolution is 4294967296 -1225335584 # # The syscall resolution is 4294967296 -1225334784 # not ok 11 __vdso_clock_getres CLOCK_MONOTONIC # # clock_id: CLOCK_MONOTONIC_RAW # # The time is 3253442966580101903.-1225334784 # ok 12 __vdso_clock_gettime CLOCK_MONOTONIC_RAW # # The vdso resolution is 4294967296 -1225335584 # # The syscall resolution is 4294967296 -1225334784 # not ok 13 __vdso_clock_getres CLOCK_MONOTONIC_RAW # # clock_id: CLOCK_MONOTONIC_COARSE # # The time is 3197606291493094159.-1225334784 # ok 14 __vdso_clock_gettime CLOCK_MONOTONIC_COARSE # # The vdso resolution is 42949672960000000 -1225335584 # # The syscall resolution is 42949672960000000 -1225334784 # not ok 15 __vdso_clock_getres CLOCK_MONOTONIC_COARSE # # Couldn't find __vdso_time # ok 16 # SKIP __vdso_time # # 1 skipped test(s) detected. Consider enabling relevant config options to improve coverage. # # Totals: pass:8 fail:7 xfail:0 xpass:0 skip:1 error:0 not ok 3 selftests: vDSO: vdso_test_abi # exit=1 ## Build * test log: https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20241126/te… * TI x15 test log: https://lkft.validation.linaro.org/scheduler/job/8117196#L7091 * build link: https://storage.tuxsuite.com/public/linaro/lkft/builds/2spp0E2mMNQq16RHsbzL… ## Source * git tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git * git sha: df5d6180169ae06a2eac57e33b077ad6f6252440 (this not new issue) * architectures: armv7 * toolchain: gcc-13 (13.3.0) - failed * toolchain: clang ( version: 19.1.7) - pass * devices: Armv7 TI beaglebone, qemu-armv7 -- Linaro LKFT https://lkft.linaro.org

8 months, 4 weeks

2
1
0 0

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

by lava＠validation.linaro.org

Total jobs: 256 Total errors: 61 (23.83%) LAVA errors: 0 (0.00%) Test errors: 53 (20.70%) Job errors: 4 (1.56%) Infra errors: 2 (0.78%) Canceled jobs: 2 (0.78%) Device type: dragonboard-845c Total jobs: 122 Total errors: 30 (24.59%) Error type: Test Error count: 30 (24.59%) Error: No match for error type 'Test', message 'lava-docker-test-shell timed out after 595 seconds' Count: 1 (0.82%) IDs: db845c-02: 8119102 Error: No match for error type 'Test', message 'tradefed - adb device lost[fbf682a2]' Count: 1 (0.82%) IDs: db845c-09: 8118668 Error: No match for error type 'Test', message 'tradefed - adb device lost[476f370a]' Count: 1 (0.82%) IDs: db845c-10: 8118401 Error: No match for error type 'Test', message 'tradefed - adb device lost[c7cf1849]' Count: 2 (1.64%) IDs: db845c-07: 8118237 8118384 Error: No match for error type 'Test', message 'lava-docker-test-shell timed out after 298 seconds' Count: 5 (4.10%) IDs: db845c-02: 8118319 db845c-06: 8118380 db845c-09: 8118320 db845c-10: 8118018 8118083 Error: No match for error type 'Test', message 'tradefed - adb device lost[dd3b965f]' Count: 2 (1.64%) IDs: db845c-02: 8117974 8118355 Error: Device NOT found! Count: 8 (6.56%) IDs: db845c-02: 8118272 8118321 8118341 8118344 db845c-04: 8117990 db845c-07: 8118354 db845c-09: 8118273 8118274 Error: No match for error type 'Test', message 'lava-docker-test-shell timed out after 598 seconds' Count: 6 (4.92%) IDs: db845c-02: 8118071 db845c-04: 8118343 db845c-07: 8118212 db845c-09: 8118029 8118322 8118324 Error: No match for error type 'Test', message 'tradefed - adb device lost[d966d3f5]' Count: 1 (0.82%) IDs: db845c-03: 8118299 Error: No match for error type 'Test', message 'lava-docker-test-shell timed out after 53998 seconds' Count: 1 (0.82%) IDs: db845c-08: 8118298 Error: No match for error type 'Test', message 'tradefed - adb device lost[b6b742b9]' Count: 1 (0.82%) IDs: db845c-01: 8118076 Error: No match for error type 'Test', message 'lava-docker-test-shell timed out after 581 seconds' Count: 1 (0.82%) IDs: db845c-01: 8118034 Device type: qrb5165-rb5 Total jobs: 107 Total errors: 21 (19.63%) Error type: Test Error count: 16 (14.95%) Error: No match for error type 'Test', message 'lava-docker-test-shell timed out after 598 seconds' Count: 5 (4.67%) IDs: rb5-03: 8117995 8118055 8118259 8118410 8118764 Error: No match for error type 'Test', message 'lava-docker-test-shell timed out after 594 seconds' Count: 1 (0.93%) IDs: rb5-03: 8118762 Error: No match for error type 'Test', message 'tradefed - adb device lost[74d67c95]' Count: 3 (2.80%) IDs: rb5-03: 8118096 8118235 8118285 Error: Device NOT found! Count: 4 (3.74%) IDs: rb5-03: 8118009 8118089 8118246 rb5-06: 8118196 Error: No match for error type 'Test', message 'lava-docker-test-shell timed out after 298 seconds' Count: 2 (1.87%) IDs: rb5-03: 8118242 rb5-06: 8118241 Error: No match for error type 'Test', message 'lava-docker-test-shell timed out after 584 seconds' Count: 1 (0.93%) IDs: rb5-03: 8117996 Error type: Job Error count: 3 (2.80%) Error: No match for error type 'Job', message 'lava-create-overlay timed out after 300 seconds' Count: 1 (0.93%) IDs: rb5-05: 8118054 Error: auto-login action timed out Count: 1 (0.93%) IDs: rb5-03: 8118053 Error: No match for error type 'Job', message 'login-action timed out after 696 seconds' Count: 1 (0.93%) IDs: rb5-06: 8118005 Error type: Infrastructure Error count: 2 (1.87%) Error: Connection closed Count: 1 (0.93%) IDs: rb5-05: 8118010 Error: No match for error type 'Infrastructure', message 'Failed to clean after job' Count: 1 (0.93%) IDs: rb5-03: 8118006 Device type: hi6220-hikey-r2 Total jobs: 5 Total errors: 5 (100.00%) Error type: Test Error count: 3 (60.00%) Error: No match for error type 'Test', message 'tradefed - adb device lost[235D989C003B0752]' Count: 3 (60.00%) IDs: hikey-6220-r2-03: 8118349 8118412 8118670 Error type: Canceled Error count: 2 (40.00%) Error: The job was canceled Count: 2 (40.00%) IDs: hikey-6220-r2-04: 8118347 hikey-6220-r2-06: 8118348 Device type: sm8550-hdk Total jobs: 22 Total errors: 5 (22.73%) Error type: Test Error count: 4 (18.18%) Error: No match for error type 'Test', message 'lava-docker-test-shell timed out after 598 seconds' Count: 4 (18.18%) IDs: sm8550-hdk-01: 8116296 8117584 8118012 8118013 Error type: Job Error count: 1 (4.55%) Error: auto-login action timed out Count: 1 (4.55%) IDs: sm8550-hdk-01: 8115796

8 months, 4 weeks

1
0
0 0

Daily report for validation - 2025-Feb-12

by lava＠validation.linaro.org

Total jobs: 98 Total errors: 70 (71.43%) LAVA errors: 0 (0.00%) Test errors: 0 (0.00%) Job errors: 19 (19.39%) Infra errors: 51 (52.04%) Canceled jobs: 0 (0.00%) Device type: dragonboard-845c Total jobs: 40 Total errors: 30 (75.00%) Error type: Job Error count: 16 (40.00%) Error: No match for error type 'Job', message 'login-action timed out after 875 seconds' Count: 8 (20.00%) IDs: dragonboard-845c-06: 4128600 4128644 4128672 4128687 4128721 4128728 4128788 4128793 Error: No match for error type 'Job', message 'login-action timed out after 874 seconds' Count: 4 (10.00%) IDs: dragonboard-845c-06: 4128558 4128571 4128605 4128704 Error: No match for error type 'Job', message 'login-action timed out after 873 seconds' Count: 1 (2.50%) IDs: dragonboard-845c-06: 4128630 Error: No match for error type 'Job', message 'login-action timed out after 635 seconds' Count: 1 (2.50%) IDs: dragonboard-845c-06: 4128531 Error: No match for error type 'Job', message 'login-action timed out after 549 seconds' Count: 1 (2.50%) IDs: dragonboard-845c-06: 4128496 Error: No match for error type 'Job', message '[ 0.000000] Kernel panic - not syncing: Attempted to kill the idle task! [ 0.000000] ---[ end Kernel panic - not syncing: Attempted to kill the idle task! ]---' Count: 1 (2.50%) IDs: dragonboard-845c-06: 4128455 Error type: Infrastructure Error count: 14 (35.00%) Error: Connection closed Count: 6 (15.00%) IDs: dragonboard-845c-04: 4128353 4128596 4128639 4128642 4128655 dragonboard-845c-06: 4128533 Error: No match for error type 'Infrastructure', message 'Unable to run pre-power: '/usr/local/lab-scripts/cbrxd_hub_control -n w1-hub01 -m sync -u 2' failed' Count: 4 (10.00%) IDs: dragonboard-845c-04: 4128375 4128580 4128582 4128586 Error: No match for error type 'Infrastructure', message 'Unable to run: ['docker', 'exec', 'lava-4128578-1.9.7-325c8dc9-5e5b-4de4-8db3-05ea9913ec90', 'fastboot', '-s', 'f0c466e0', 'flash', 'rootfs', '/var/lib/lava/dispatcher/tmp/4128578/fastboot-deploy-pak7fw9q/rootfs/linaro-sid-developer-dragonboard-845c-412.img']' Count: 1 (2.50%) IDs: dragonboard-845c-06: 4128578 Error: No match for error type 'Infrastructure', message 'Unable to run: ['docker', 'exec', 'lava-4128577-1.9.7-cd186170-e6e4-4da3-a093-fd60ecf92d00', 'fastboot', '-s', 'fe596908', 'flash', 'rootfs', '/var/lib/lava/dispatcher/tmp/4128577/fastboot-deploy-nknwilxy/rootfs/linaro-sid-developer-dragonboard-845c-412.img']' Count: 1 (2.50%) IDs: dragonboard-845c-04: 4128577 Error: Reboot failed Count: 1 (2.50%) IDs: dragonboard-845c-04: 4128327 Error: No match for error type 'Infrastructure', message 'Unable to run: ['docker', 'exec', 'lava-4128305-2.7.11-ddfe22ff-fb40-43d2-bb9f-dfb2ad7ec267', 'fastboot', '-s', 'fe596908', 'flash', 'rootfs', '/var/lib/lava/dispatcher/tmp/4128305/fastboot-deploy-wg8iwb47/rootfs.img']' Count: 1 (2.50%) IDs: dragonboard-845c-04: 4128305 Device type: dragonboard-410c Total jobs: 6 Total errors: 6 (100.00%) Error type: Infrastructure Error count: 5 (83.33%) Error: No match for error type 'Infrastructure', message 'Unable to run pre-power: '/usr/local/lab-scripts/cbrxd_hub_control -n w1-hub01 -m sync -u 11' failed' Count: 5 (83.33%) IDs: dragonboard-410c-01: 4128359 4128361 4128362 4128363 4128579 Error type: Job Error count: 1 (16.67%) Error: No match for error type 'Job', message 'Unable to update image rootfs: 'mount: mount exited with status 32: mount: /sysroot: wrong fs type, bad option, bad superblock on /dev/sda, missing codepage or helper program, or other error.\n dmesg(1) may have more information after failed mount system call.'' Count: 1 (16.67%) IDs: dragonboard-410c-01: 4128355 Device type: x15 Total jobs: 29 Total errors: 17 (58.62%) Error type: Infrastructure Error count: 15 (51.72%) Error: Connection closed Count: 2 (6.90%) IDs: x15-01: 4128462 4128573 Error: bootloader-interrupt timed out Count: 1 (3.45%) IDs: x15-01: 4128546 Error: No match for error type 'Infrastructure', message 'wait-device-boardid timed out after 858 seconds' Count: 1 (3.45%) IDs: x15-01: 4128514 Error: No match for error type 'Infrastructure', message 'Unable to run: ['docker', 'exec', 'lava-4128478-4.7.3-bd426267-09b1-4f55-8c85-d760c8e6b611', 'fastboot', '-s', '1300d00902428922', 'flash', 'super', '/var/lib/lava/dispatcher/tmp/4128478/fastboot-deploy-j2ojbc93/super/rpb-console-image-am57xx-evm-20180205221320-631.rootfs.img']' Count: 1 (3.45%) IDs: x15-01: 4128478 Error: matched a bootloader error message Count: 9 (31.03%) IDs: x15-01: 4128388 4128393 4128397 4128400 4128401 4128404 4128411 4128413 4128416 Error: No match for error type 'Infrastructure', message 'Unable to run: ['docker', 'exec', 'lava-4128367-1.18.7-c1bd4b9f-b38d-458b-aec9-d92db53ad008', 'fastboot', '-s', '1300d00902428922', 'flash', 'super', '/var/lib/lava/dispatcher/tmp/4128367/fastboot-deploy-97s0qu6t/super/4.19-super.img']' Count: 1 (3.45%) IDs: x15-01: 4128367 Error type: Job Error count: 2 (6.90%) Error: No match for error type 'Job', message 'uboot-enter-fastboot timed out after 898 seconds' Count: 1 (3.45%) IDs: x15-01: 4128475 Error: Login incorrect Count: 1 (3.45%) IDs: x15-01: 4128465 Device type: bcm2837-rpi-3-b-32 Total jobs: 10 Total errors: 10 (100.00%) Error type: Infrastructure Error count: 10 (100.00%) Error: Reboot failed Count: 10 (100.00%) IDs: rpi3-b-32-03: 4128358 4128360 4128368 4128370 4128460 4128461 4128479 4128523 4128537 4128540 Device type: imx93-11x11-evk Total jobs: 3 Total errors: 1 (33.33%) Error type: Infrastructure Error count: 1 (33.33%) Error: No match for error type 'Infrastructure', message 'Fail UUUBootAction on cmd : -b emmc_all /var/lib/lava/dispatcher/tmp/4128366/uuu-deploy-auv57ooc/boot/imx-boot-imx93-11x11-lpddr4x-evk-sd.bin-flash_singleboot /var/lib/lava/dispatcher/tmp/4128366/uuu-deploy-auv57ooc/rootfs/trs-image-trs-qemuarm64.rootfs.wic' Count: 1 (33.33%) IDs: imx93-01: 4128366 Device type: beaglebone-black Total jobs: 7 Total errors: 3 (42.86%) Error type: Infrastructure Error count: 3 (42.86%) Error: matched a bootloader error message Count: 2 (28.57%) IDs: beaglebone-black03: 4128371 4128382 Error: Connection closed Count: 1 (14.29%) IDs: beaglebone-black03: 4128364 Device type: hi6220-hikey-r2 Total jobs: 3 Total errors: 3 (100.00%) Error type: Infrastructure Error count: 3 (100.00%) Error: No match for error type 'Infrastructure', message 'Unable to run pre-power: '/usr/local/lab-scripts/cbrxd_hub_control -n w1-hub01 -m sync -u 15' failed' Count: 3 (100.00%) IDs: hi6220-hikey-r2-02: 4128365 4128369 4128372

8 months, 4 weeks

1
0
0 0

Let me know

by Martyn Beasley

Hi there! I hope you can get back to me soon. I'm currently in need of help with purchasing some raw materials from China. Thank you! Martyn Beasley

8 months, 4 weeks

1
0
0 0

next-20250210: WARNING: at include/linux/rwsem.h:85 madvise_unlock

by Naresh Kamboju

Regressions on arm64 Juno-r2 device while running LTP syscalls tests madvise01 warnings on the Linux next-20250210 tag. First seen on next-20250210 Good: next-20250207 Bad: next-20250210 This regression is reproducible with CONFIG_ARM64_64K_PAGES=y Test regression: LTP madvise01 WARNING include/linux/rwsem.h madvise_unlock Reported-by: Linux Kernel Functional Testing <lkft(a)linaro.org> ## Test log command: madvise01 [ 1190.422933] /usr/local/bin/kirk[359]: starting test madvise01 (madvise01) tst_tmpdir.c:316: TINFO: Using /tmp/LTP_madSbRtkW as tmpdir (tmpfs filesystem) tst_test.c:1860: TINFO: LTP version: 20240930 [ 1190.607278] Injecting memory failure for pfn 0x8e13f at process virtual address 0xffff8c8c0000 tst_test.c:1864: TINFO:[ ** replaying previous printk message ** [ 1190.618980] Memory failure: 0x8e13f: recovery action for clean LRU page: Recovered [ 1190.619013] ------------[ cut here ]------------ [ 1190.619016] WARNING: CPU: 2 PID: 137820 at include/linux/rwsem.h:85 madvise_unlock (include/linux/rwsem.h:85 (discriminator 1) include/linux/rwsem.h:205 (discriminator 1) include/linux/mmap_lock.h:70 (discriminator 1) include/linux/mmap_lock.h:169 (discriminator 1) include/linux/mmap_lock.h:176 (discriminator 1) mm/madvise.c:1599 (discriminator 1)) Tested kernel: 6.14.0-rc2-next-20[ 1190.646322] Modules linked in: tun overlay btrfs blake2b_generic xor xor_neon raid6_pq zstd_compress panfrost hdlcd tda998x onboard_usb_dev drm_shmem_helper drm_client_lib cec gpu_sched drm_dma_helper drm_kms_helper fuse drm backlight ip_tables x_tables 250210 #1 SMP PREEMPT @1739162484[ 1190.671777] CPU: 2 UID: 0 PID: 137820 Comm: madvise01 Not tainted 6.14.0-rc2-next-20250210 #1 [ 1190.683191] Hardware name: ARM Juno development board (r2) (DT) aarch64 tst_test.c:1703: TINFO:[ 1192.996920] pstate: a0000005 (NzCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--) Timeout per run is 0h 05m 24s [ 1193.006802] pc : madvise_unlock (include/linux/rwsem.h:85 (discriminator 1) include/linux/rwsem.h:205 (discriminator 1) include/linux/mmap_lock.h:70 (discriminator 1) include/linux/mmap_lock.h:169 (discriminator 1) include/linux/mmap_lock.h:176 (discriminator 1) mm/madvise.c:1599 (discriminator 1)) [ 1211.692758] rcu: INFO: rcu_preempt detected stalls on CPUs/tasks: [ 1211.692776] rcu: 1-...0: (0 ticks this GP) idle=f3a4/1/0x4000000000000000 softirq=946757/946757 fqs=2625 [ 1211.692794] rcu: 2-...0: (1 GPs behind) idle=2fac/1/0x4000000000000002 softirq=357256/357257 fqs=2625 [ 1211.692809] rcu: (detected by 4, t=5252 jiffies, g=196909, q=138 ncpus=6) [ 1211.692821] Sending NMI from CPU 4 to CPUs 1: [ 1221.694021] Sending NMI from CPU 4 to CPUs 2: [ 1231.695220] rcu: rcu_preempt kthread timer wakeup didn't happen for 5001 jiffies! g196909 f0x0 RCU_GP_WAIT_FQS(5) ->state=0x402 [ 1231.695231] rcu: Possible timer handling issue on cpu=4 timer-softirq=26922 [ 1231.695238] rcu: rcu_preempt kthread starved for 5002 jiffies! g196909 f0x0 RCU_GP_WAIT_FQS(5) ->state=0x402 ->cpu=4 [ 1231.695251] rcu: Unless rcu_preempt kthread gets sufficient CPU time, OOM is now expected behavior. [ 1231.695257] rcu: RCU grace-period kthread stack dump: [ 1231.695262] task:rcu_preempt state:I stack:0 pid:18 tgid:18 ppid:2 task_flags:0x208040 flags:0x00000008 [ 1231.695280] Call trace: [ 1231.695286] __switch_to (arch/arm64/kernel/process.c:704) (T) [ 1231.695306] __schedule (kernel/sched/core.c:5381 kernel/sched/core.c:6765) [ 1231.695318] schedule (kernel/sched/core.c:6843 kernel/sched/core.c:6857) [ 1231.695330] schedule_timeout (include/linux/timer.h:185 kernel/time/sleep_timeout.c:100) [ 1231.695347] rcu_gp_fqs_loop (kernel/rcu/tree.c:2024 (discriminator 15)) [ 1231.695365] rcu_gp_kthread (kernel/rcu/tree.c:2229 (discriminator 2)) [ 1231.695380] kthread (kernel/kthread.c:464) [ 1231.695395] ret_from_fork (arch/arm64/kernel/entry.S:863) [ 1231.695410] rcu: Stack dump where RCU GP kthread last ran: [ 1231.695417] CPU: 4 UID: 0 PID: 0 Comm: swapper/4 Not tainted 6.14.0-rc2-next-20250210 #1 [ 1231.695428] Hardware name: ARM Juno development board (r2) (DT) [ 1231.695434] pstate: 40000005 (nZcv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 1231.695445] pc : cpuidle_enter_state (drivers/cpuidle/cpuidle.c:292) [ 1231.695467] lr : cpuidle_enter_state (arch/arm64/include/asm/irqflags.h:26 arch/arm64/include/asm/irqflags.h:48 drivers/cpuidle/cpuidle.c:290) [ 1231.695481] sp : ffff80008378fd90 [ 1231.695486] x29: ffff80008378fd90 x28: 0000000000000000 x27: 0000000000000000 [ 1231.695503] x26: 0000000000000000 x25: 0000000000000001 x24: 0000011a1e4785a4 [ 1231.695519] x23: 0000000000000001 x22: ffff00080314a080 x21: 0000011a1e83fe44 [ 1231.695536] x20: 0000000000000001 x19: ffff00097d625778 x18: ffff8000a0c2fc10 [ 1231.695552] x17: 000000040044ffff x16: 00500072f5507510 x15: 0000000000000000 [ 1231.695568] x14: ffff0008007bc800 x13: ffff8008fad70000 x12: 0000000034d4d91d [ 1231.695585] x11: 0000000000000000 x10: 0000000000001000 x9 : ffff8000815901a4 [ 1231.695601] x8 : ffff80008378fc98 x7 : 0000000000000001 x6 : ffff8000829f9000 [ 1231.695617] x5 : ffff0008007bc800 x4 : ffff8000829f95e0 x3 : 0000000000000000 [ 1231.695633] x2 : 0000000000000000 x1 : 0000000100000001 x0 : 0000000100000001 [ 1231.695649] Call trace: [ 1231.695653] cpuidle_enter_state (drivers/cpuidle/cpuidle.c:292) (P) [ 1231.695671] cpuidle_enter (drivers/cpuidle/cpuidle.c:391 (discriminator 2)) [ 1231.695692] do_idle (kernel/sched/idle.c:155 kernel/sched/idle.c:230 kernel/sched/idle.c:325) [ 1231.695716] cpu_startup_entry (kernel/sched/idle.c:423 (discriminator 1)) [ 1231.695732] secondary_start_kernel (arch/arm64/include/asm/atomic_ll_sc.h:95 (discriminator 2) arch/arm64/include/asm/atomic.h:28 (discriminator 2) include/linux/atomic/atomic-arch-fallback.h:546 (discriminator 2) include/linux/atomic/atomic-arch-fallback.h:994 (discriminator 2) include/linux/atomic/atomic-instrumented.h:436 (discriminator 2) include/linux/sched/mm.h:37 (discriminator 2) arch/arm64/kernel/smp.c:214 (discriminator 2)) [ 1231.695749] __secondary_switched (arch/arm64/kernel/head.S:421) madvise01.c:68: TINFO: Mounting [ 1231.961851] lr : do_madvise (mm/madvise.c:1748) [ 1242.412862] sp : ffff8000a188fdc0 tmp_madvise to /tmp/LTP_madSbRtkW/tmp_madvise fstyp=tmpfs flags=0[ 1242.416214] x29: ffff8000a188fdc0 x28: ffff000813417c00 x27: 0000000000000000 madvise01.c:113: TPASS: madvise[ 1294.712666] rcu: INFO: rcu_preempt detected stalls on CPUs/tasks: [ 1294.712685] rcu: 2-...0: (1 GPs behind) idle=2fac/1/0x4000000000000002 softirq=357256/357257 fqs=7636 [ 1294.712704] rcu: (detected by 4, t=26007 jiffies, g=196909, q=184 ncpus=6) [ 1294.712716] Sending NMI from CPU 4 to CPUs 2: [ 1304.713915] rcu: rcu_preempt kthread timer wakeup didn't happen for 8168 jiffies! g196909 f0x0 RCU_GP_WAIT_FQS(5) ->state=0x402 [ 1304.713927] rcu: Possible timer handling issue on cpu=3 timer-softirq=35895 [ 1304.713933] rcu: rcu_preempt kthread starved for 8169 jiffies! g196909 f0x0 RCU_GP_WAIT_FQS(5) ->state=0x402 ->cpu=3 [ 1304.713945] rcu: Unless rcu_preempt kthread gets sufficient CPU time, OOM is now expected behavior. [ 1304.713951] rcu: RCU grace-period kthread stack dump: [ 1304.713955] task:rcu_preempt state:I stack:0 pid:18 tgid:18 ppid:2 task_flags:0x208040 flags:0x00000008 [ 1304.713974] Call trace: [ 1304.713979] __switch_to (arch/arm64/kernel/process.c:704) (T) [ 1304.714000] __schedule (kernel/sched/core.c:5381 kernel/sched/core.c:6765) [ 1304.714013] schedule (kernel/sched/core.c:6843 kernel/sched/core.c:6857) [ 1304.714024] schedule_timeout (include/linux/timer.h:185 kernel/time/sleep_timeout.c:100) [ 1304.714042] rcu_gp_fqs_loop (kernel/rcu/tree.c:2024 (discriminator 15)) [ 1304.714061] rcu_gp_kthread (kernel/rcu/tree.c:2229 (discriminator 2)) [ 1304.714076] kthread (kernel/kthread.c:464) [ 1304.714090] ret_from_fork (arch/arm64/kernel/entry.S:863) [ 1304.714105] rcu: Stack dump where RCU GP kthread last ran: [ 1304.714109] Sending NMI from CPU 4 to CPUs 3: [ 1304.714119] NMI backtrace for cpu 3 [ 1304.714130] CPU: 3 UID: 0 PID: 205 Comm: systemd-udevd Not tainted 6.14.0-rc2-next-20250210 #1 [ 1304.714143] Hardware name: ARM Juno development board (r2) (DT) [ 1304.714148] pstate: 00000005 (nzcv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 1304.714158] pc : queued_spin_lock_slowpath (kernel/locking/qspinlock.c:380 (discriminator 5)) [ 1304.714176] lr : _raw_spin_lock_bh (kernel/locking/spinlock.c:179) [ 1304.714189] sp : ffff800085e6f310 [ 1304.714193] x29: ffff800085e6f310 x28: ffff000808761c00 x27: ffff00080295b500 [ 1304.714210] x26: ffff00081e724e00 x25: 0000000000000000 x24: 0000000000008080 [ 1304.714224] x23: 0000000000000000 x22: 0000000074000080 x21: 0000000000000078 [ 1304.714239] x20: ffff000802bb0a30 x19: ffff000802bb0a30 x18: 0000000000000000 [ 1304.714254] x17: 0000000000000000 x16: 0000000000000000 x15: 0000aaaabea75a70 [ 1304.714268] x14: 0000000000000000 x13: 2dcd92d500000000 x12: 40982a24d45a0569 [ 1304.714283] x11: 3cc1638a3642b30d x10: d5e7818600000000 x9 : ffff80008159decc [ 1304.714298] x8 : ffff800085e6f278 x7 : 0000000000000000 x6 : 0000000000000201 [ 1304.714312] x5 : ffff8000829f9000 x4 : ffff8000829f95e0 x3 : 0000000000000001 [ 1304.714326] x2 : 0000000000000000 x1 : 0000000000000000 x0 : 0000000000000001 [ 1304.714339] Call trace: [ 1304.714343] queued_spin_lock_slowpath (kernel/locking/qspinlock.c:380 (discriminator 5)) (P) [ 1304.714360] _raw_spin_lock_bh (kernel/locking/spinlock.c:179) [ 1304.714374] lock_sock_nested (net/core/sock.c:3649 (discriminator 1)) [ 1304.714388] tcp_sock_set_cork (net/ipv4/tcp.c:3547 net/ipv4/tcp.c:3560) [ 1304.714405] xs_tcp_send_request (net/sunrpc/xprtsock.c:1124) [ 1304.714418] xprt_transmit (net/sunrpc/xprt.c:1578 net/sunrpc/xprt.c:1634) [ 1304.714434] call_transmit (net/sunrpc/clnt.c:2283 net/sunrpc/clnt.c:2265) [ 1304.714447] __rpc_execute (include/asm-generic/bitops/generic-non-atomic.h:128 net/sunrpc/sched.c:954) [ 1304.714463] rpc_execute (include/linux/sched/mm.h:339 (discriminator 1) include/linux/sched/mm.h:399 (discriminator 1) net/sunrpc/sched.c:1026 (discriminator 1)) [ 1304.714476] rpc_run_task (net/sunrpc/clnt.c:1250) [ 1304.714488] rpc_call_sync (net/sunrpc/clnt.c:1278 (discriminator 1)) [ 1304.714501] nfs3_rpc_wrapper (fs/nfs/nfs3proc.c:36) [ 1304.714516] nfs3_proc_getattr (fs/nfs/nfs3proc.c:123) [ 1304.714528] __nfs_revalidate_inode (fs/nfs/inode.c:1311 (discriminator 2)) [ 1304.714546] nfs_access_get_cached (fs/nfs/dir.c:3058 (discriminator 1) fs/nfs/dir.c:3118 (discriminator 1)) [ 1304.714561] nfs_do_access (fs/nfs/dir.c:3246) [ 1304.714574] nfs_permission (fs/nfs/dir.c:3360) [ 1304.714588] inode_permission (fs/namei.c:588 fs/namei.c:562) [ 1304.714606] link_path_walk.part.0.constprop.0 (fs/namei.c:1831 fs/namei.c:2422) [ 1304.714624] path_lookupat (fs/namei.c:2607 fs/namei.c:2630) [ 1304.714639] filename_lookup (fs/namei.c:2660) [ 1304.714654] kern_path (fs/namei.c:2768) [ 1304.714669] unix_find_other (net/unix/af_unix.c:1153 net/unix/af_unix.c:1182) [ 1304.714681] unix_dgram_sendmsg (net/unix/af_unix.c:2038) [ 1304.714692] ____sys_sendmsg (net/socket.c:718 (discriminator 1) net/socket.c:733 (discriminator 1) net/socket.c:2573 (discriminator 1)) [ 1304.714710] ___sys_sendmsg (net/socket.c:2627) [ 1304.714725] __sys_sendmsg (net/socket.c:2659 (discriminator 1)) [ 1304.714740] __arm64_sys_sendmsg (net/socket.c:2662) [ 1304.714755] invoke_syscall.constprop.0 (arch/arm64/include/asm/syscall.h:61 arch/arm64/kernel/syscall.c:54) [ 1304.714772] do_el0_svc (arch/arm64/kernel/syscall.c:139 arch/arm64/kernel/syscall.c:151) [ 1304.714787] el0_svc (arch/arm64/include/asm/irqflags.h:82 (discriminator 1) arch/arm64/include/asm/irqflags.h:123 (discriminator 1) arch/arm64/include/asm/irqflags.h:136 (discriminator 1) arch/arm64/kernel/entry-common.c:165 (discriminator 1) arch/arm64/kernel/entry-common.c:178 (discriminator 1) arch/arm64/kernel/entry-common.c:745 (discriminator 1)) [ 1304.714806] el0t_64_sync_handler (arch/arm64/kernel/entry-common.c:763) [ 1304.714821] el0t_64_sync (arch/arm64/kernel/entry.S:600) test for MADV_NORMAL PASSED ## Source * kernel version: 6.14.0-rc2-next-20250210 * git tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git * git sha: df5d6180169ae06a2eac57e33b077ad6f6252440 * git describe: next-20250210 * project details: https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20250210/ * architecture: arm64 * device: Juno-r2 * toolchain: gcc-13 * config : CONFIG_ARM64_64K_PAGES=y (gcc-13-lkftconfig-64k_page_size) * build config: https://storage.tuxsuite.com/public/linaro/lkft/builds/2spp0dMfaQHNeHr0jT9D… * build: https://storage.tuxsuite.com/public/linaro/lkft/builds/2spp0dMfaQHNeHr0jT9D… ## Boot log Juno-r2 log: https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20250210/te… Juno-r2 details: https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20250210/te… Juno-r2 history: https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20250210/te… Juno-r2 lava log 1: https://lkft.validation.linaro.org/scheduler/job/8117395#L43180 Juno-r2 lava log 2: https://lkft.validation.linaro.org/scheduler/job/8118169 Juno-r2 lava log 3: https://lkft.validation.linaro.org/scheduler/job/8118170 -- Linaro LKFT https://lkft.linaro.org

8 months, 4 weeks

3
3
0 0

Daily cts/vts report for lkft - 2025-Feb-11

by lava＠validation.linaro.org

Total jobs: 125 Total errors: 19 (15.20%) LAVA errors: 0 (0.00%) Test errors: 17 (13.60%) Job errors: 2 (1.60%) Infra errors: 0 (0.00%) Canceled jobs: 0 (0.00%) Device type: qrb5165-rb5 Total jobs: 24 Total errors: 4 (16.67%) Error type: Test Error count: 2 (8.33%) Error: No match for error type 'Test', message 'lava-docker-test-shell timed out after 562 seconds' Count: 1 (4.17%) IDs: rb5-03: 8117831 Error: Device NOT found! Count: 1 (4.17%) IDs: rb5-03: 8117765 Error type: Job Error count: 2 (8.33%) Error: No match for error type 'Job', message 'lava-create-overlay timed out after 300 seconds' Count: 1 (4.17%) IDs: rb5-05: 8117818 Error: No match for error type 'Job', message 'test-definition timed out after 299 seconds' Count: 1 (4.17%) IDs: rb5-07: 8117779 Device type: dragonboard-845c Total jobs: 69 Total errors: 10 (14.49%) Error type: Test Error count: 10 (14.49%) Error: No match for error type 'Test', message 'lava-docker-test-shell timed out after 598 seconds' Count: 6 (8.70%) IDs: db845c-01: 8105981 db845c-02: 8105983 8117073 8117763 8117797 8117807 Error: No match for error type 'Test', message 'The network seems not available, as the ping command failed' Count: 1 (1.45%) IDs: db845c-08: 8117775 Error: No match for error type 'Test', message 'tradefed - adb device lost[476f370a]' Count: 1 (1.45%) IDs: db845c-10: 8117592 Error: No match for error type 'Test', message 'tradefed - adb device lost[e875976d]' Count: 1 (1.45%) IDs: db845c-06: 8117544 Error: Device NOT found! Count: 1 (1.45%) IDs: db845c-02: 8105994 Device type: hi6220-hikey-r2 Total jobs: 4 Total errors: 4 (100.00%) Error type: Test Error count: 4 (100.00%) Error: No match for error type 'Test', message 'The network seems not available, as the ping command failed' Count: 2 (50.00%) IDs: hikey-6220-r2-02: 8117543 hikey-6220-r2-05: 8117599 Error: No match for error type 'Test', message 'tradefed - adb device lost[4595FE84003F72FC]' Count: 1 (25.00%) IDs: hikey-6220-r2-04: 8117591 Error: No match for error type 'Test', message 'lava-test-interactive timed out after 600 seconds' Count: 1 (25.00%) IDs: hikey-6220-r2-05: 8117531 Device type: hi960-hikey Total jobs: 2 Total errors: 0 (0.00%) Device type: sm8550-hdk Total jobs: 26 Total errors: 1 (3.85%) Error type: Test Error count: 1 (3.85%) Error: No match for error type 'Test', message 'lava-docker-test-shell timed out after 598 seconds' Count: 1 (3.85%) IDs: sm8550-hdk-01: 8115276

8 months, 4 weeks

1
0
0 0

Daily report for validation - 2025-Feb-11

by lava＠validation.linaro.org

Total jobs: 115 Total errors: 39 (33.91%) LAVA errors: 0 (0.00%) Test errors: 2 (1.74%) Job errors: 17 (14.78%) Infra errors: 20 (17.39%) Canceled jobs: 0 (0.00%) Device type: x15 Total jobs: 28 Total errors: 5 (17.86%) Error type: Job Error count: 4 (14.29%) Error: Login incorrect Count: 1 (3.57%) IDs: x15-01: 4128340 Error: No match for error type 'Job', message 'login-action timed out after 275 seconds' Count: 1 (3.57%) IDs: x15-01: 4128292 Error: No match for error type 'Job', message 'login-action timed out after 273 seconds' Count: 1 (3.57%) IDs: x15-01: 4128260 Error: No match for error type 'Job', message 'login-action timed out after 274 seconds' Count: 1 (3.57%) IDs: x15-01: 4128216 Error type: Test Error count: 1 (3.57%) Error: lava-test-shell timed out Count: 1 (3.57%) IDs: x15-01: 4128259 Device type: bcm2837-rpi-3-b-32 Total jobs: 30 Total errors: 5 (16.67%) Error type: Infrastructure Error count: 4 (13.33%) Error: Reboot failed Count: 4 (13.33%) IDs: rpi3-b-32-03: 4128329 4128336 4128338 4128339 Error type: Job Error count: 1 (3.33%) Error: lava-test-retry timed out Count: 1 (3.33%) IDs: rpi3-b-32-03: 4128242 Device type: beaglebone-black Total jobs: 25 Total errors: 2 (8.00%) Error type: Test Error count: 1 (4.00%) Error: lava-test-shell timed out Count: 1 (4.00%) IDs: beaglebone-black03: 4128236 Error type: Infrastructure Error count: 1 (4.00%) Error: No match for error type 'Infrastructure', message 'Failed to clean after job' Count: 1 (4.00%) IDs: beaglebone-black03: 4128219 Device type: dragonboard-410c Total jobs: 10 Total errors: 9 (90.00%) Error type: Job Error count: 9 (90.00%) Error: No match for error type 'Job', message 'Unable to update image rootfs: 'mount: mount exited with status 32: mount: /sysroot: wrong fs type, bad option, bad superblock on /dev/sda, missing codepage or helper program, or other error.\n dmesg(1) may have more information after failed mount system call.'' Count: 9 (90.00%) IDs: dragonboard-410c-01: 4128227 4128244 4128252 4128270 4128295 4128306 4128308 4128309 4128328 Device type: dragonboard-845c Total jobs: 20 Total errors: 18 (90.00%) Error type: Infrastructure Error count: 15 (75.00%) Error: No match for error type 'Infrastructure', message 'Unable to run pre-power: '/usr/local/lab-scripts/cbrxd_hub_control -n w1-hub01 -m sync -u 6' failed' Count: 5 (25.00%) IDs: dragonboard-845c-06: 4128311 4128314 4128315 4128317 4128319 Error: No match for error type 'Infrastructure', message 'Unable to run pre-power: '/usr/local/lab-scripts/cbrxd_hub_control -n w1-hub01 -m sync -u 2' failed' Count: 5 (25.00%) IDs: dragonboard-845c-04: 4128310 4128312 4128313 4128316 4128318 Error: Reboot failed Count: 1 (5.00%) IDs: dragonboard-845c-06: 4128304 Error: Connection closed Count: 3 (15.00%) IDs: dragonboard-845c-04: 4128249 4128303 dragonboard-845c-06: 4128268 Error: No match for error type 'Infrastructure', message 'Failed to clean after job' Count: 1 (5.00%) IDs: dragonboard-845c-04: 4128271 Error type: Job Error count: 3 (15.00%) Error: No match for error type 'Job', message 'login-action timed out after 601 seconds' Count: 1 (5.00%) IDs: dragonboard-845c-06: 4128298 Error: No match for error type 'Job', message 'login-action timed out after 873 seconds' Count: 1 (5.00%) IDs: dragonboard-845c-06: 4128246 Error: No match for error type 'Job', message 'login-action timed out after 875 seconds' Count: 1 (5.00%) IDs: dragonboard-845c-04: 4128224 Device type: hi6220-hikey-r2 Total jobs: 1 Total errors: 0 (0.00%) Device type: imx93-11x11-evk Total jobs: 1 Total errors: 0 (0.00%)

8 months, 4 weeks

1
0
0 0

two e-bike models with direct shipping from germany

by E-Mobility

Hello, We are glad to present two of our e-bike models, crafted to cater to a variety of riding preferences while seamlessly blending style, functionality, and the latest technology. Whether you're commuting through urban landscapes, heading out on weekend adventures, or simply enjoying a smooth ride, these models offer versatility, comfort, and excellent performance. Both bikes are shipped directly from our warehouse in Germany, ensuring fast and reliable delivery across the EU within 3–7 business days. We take great pride in providing an easy and seamless purchase and delivery experience, so you can start riding your new e-bike as soon as possible. If you're interested in making a purchase or would like a shipping estimate, kindly share your address, and we'll provide a detailed quote based on your location. Classic Moped X: The Classic Moped X merges the charm of a classic scooter with modern e-bike features, making it ideal for those who love vintage looks with a modern twist. Some standout features include: Motor: 500W motor, ensuring smooth acceleration and reliable power on flat roads or moderate inclines. Battery: 48V 15AH lithium battery, offering a solid range of up to 50 miles on a single charge, perfect for longer trips. Brakes: Reliable front and rear disc brakes provide excellent stopping power in any condition. Tires: 22-inch wide tires for superior grip and comfort, ideal for urban streets and leisurely rides on light trails. Design: Classic scooter-inspired design, updated with modern functionality. Its sturdy frame ensures long-term durability while maintaining a retro aesthetic. Lighting: Built-in lighting system to enhance visibility and safety during low-light or night-time riding. [Ouxi_V8_E-Bike_-_100_miles__160_km__long_term_review_4-9_screenshot-90 0x604.jpg] City Explorer Z: Suspension: Dual suspension system featuring a 75mm front air shock and rear suspension for a smooth, comfortable ride on various terrains. Motor: 500W motor, providing power for speeds up to 40 km/h, making it easy to navigate through busy city streets or enjoy leisurely rides in nature. Battery: Removable 48V 15AH lithium-ion battery, offering a range of 60–80 km per charge, perfect for long-distance commutes or weekend getaways. Foldable Design: Weighing just 30 kg, this e-bike features a compact, foldable design, making it ideal for storage and easy transport. Features: The LCD display keeps you updated on speed, battery level, and other metrics. With a 6-speed gear system and 5 levels of pedal assist, you can tailor your ride to any terrain. Mechanical disc brakes offer consistent performance regardless of weather conditions. Tires: 22-inch thick tires provide exceptional stability and traction on both paved streets and gravel paths. [ado-a20f-beast-electric-bike-20.jpg] [ado-a20f-beast-electric-bike-20.jpg] We look forward to your response. Best regards, Andreas Miles Your E-Bike Specialist If you would prefer not to receive emails about our e-bikes, please send email address to unlist

9 months

1
0
0 0

Daily report for validation - 2025-Feb-10

by lava＠validation.linaro.org

Total jobs: 56 Total errors: 11 (19.64%) LAVA errors: 0 (0.00%) Test errors: 1 (1.79%) Job errors: 8 (14.29%) Infra errors: 2 (3.57%) Canceled jobs: 0 (0.00%) Device type: dragonboard-845c Total jobs: 7 Total errors: 5 (71.43%) Error type: Job Error count: 3 (42.86%) Error: No match for error type 'Job', message 'login-action timed out after 873 seconds' Count: 1 (14.29%) IDs: dragonboard-845c-04: 4128188 Error: No match for error type 'Job', message 'login-action timed out after 874 seconds' Count: 1 (14.29%) IDs: dragonboard-845c-06: 4128150 Error: No match for error type 'Job', message 'login-action timed out after 875 seconds' Count: 1 (14.29%) IDs: dragonboard-845c-04: 4128133 Error type: Infrastructure Error count: 2 (28.57%) Error: Connection closed Count: 2 (28.57%) IDs: dragonboard-845c-06: 4128162 4128172 Device type: dragonboard-410c Total jobs: 5 Total errors: 4 (80.00%) Error type: Job Error count: 4 (80.00%) Error: No match for error type 'Job', message 'Unable to update image rootfs: 'mount: mount exited with status 32: mount: /sysroot: wrong fs type, bad option, bad superblock on /dev/sda, missing codepage or helper program, or other error.\n dmesg(1) may have more information after failed mount system call.'' Count: 4 (80.00%) IDs: dragonboard-410c-01: 4128134 4128149 4128163 4128186 Device type: x15 Total jobs: 14 Total errors: 1 (7.14%) Error type: Job Error count: 1 (7.14%) Error: No match for error type 'Job', message 'login-action timed out after 273 seconds' Count: 1 (7.14%) IDs: x15-01: 4128146 Device type: bcm2837-rpi-3-b-32 Total jobs: 10 Total errors: 0 (0.00%) Device type: beaglebone-black Total jobs: 17 Total errors: 0 (0.00%) Device type: hi6220-hikey-r2 Total jobs: 2 Total errors: 1 (50.00%) Error type: Test Error count: 1 (50.00%) Error: Invalid TESTCASE signal Count: 1 (50.00%) IDs: hi6220-hikey-r2-02: 4128116 Device type: imx93-11x11-evk Total jobs: 1 Total errors: 0 (0.00%)

9 months

1
0
0 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

Lkft-triage February 2025