Lkft-triage April 2025

lkft-triage@lists.linaro.org

49 participants
99 discussions

Daily report for validation - 2025-Apr-03

by lava＠validation.linaro.org

Total jobs: 95 Total errors: 8 (8.42%) LAVA errors: 0 (0.00%) Test errors: 0 (0.00%) Job errors: 8 (8.42%) Infra errors: 0 (0.00%) Canceled jobs: 0 (0.00%) Device type: dragonboard-845c Total jobs: 11 Total errors: 0 (0.00%) Device type: dragonboard-410c Total jobs: 8 Total errors: 7 (87.50%) Error type: Job Error count: 7 (87.50%) 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: 7 (87.50%) IDs: dragonboard-410c-01: 4140567 4140585 4140612 4140638 4140643 4140662 4140676 Device type: bcm2837-rpi-3-b-32 Total jobs: 17 Total errors: 0 (0.00%) Device type: beaglebone-black Total jobs: 32 Total errors: 0 (0.00%) Device type: x15 Total jobs: 25 Total errors: 1 (4.00%) Error type: Job Error count: 1 (4.00%) Error: No match for error type 'Job', message 'login-action timed out after 274 seconds' Count: 1 (4.00%) IDs: x15-01: 4140606 Device type: imx93-11x11-evk Total jobs: 1 Total errors: 0 (0.00%) Device type: hi6220-hikey-r2 Total jobs: 1 Total errors: 0 (0.00%)

3 weeks, 5 days

Re: [PATCH v2 10/13] arch, mm: set high_memory in free_area_init()

by Thomas Weißschuh

(drop all the non-x86 and non-mm recipients) Hi, On Thu, Mar 13, 2025 at 03:50:00PM +0200, Mike Rapoport wrote: > From: "Mike Rapoport (Microsoft)" <rppt(a)kernel.org> > > high_memory defines upper bound on the directly mapped memory. > This bound is defined by the beginning of ZONE_HIGHMEM when a system has > high memory and by the end of memory otherwise. > > All this is known to generic memory management initialization code that > can set high_memory while initializing core mm structures. > > Add a generic calculation of high_memory to free_area_init() and remove > per-architecture calculation except for the architectures that set and > use high_memory earlier than that. This change (in mainline as commit e120d1bc12da ("arch, mm: set high_memory in free_area_init()") breaks booting i386 on QEMU for me (and others [0]). The boot just hangs without output. It's easily reproducible with kunit: ./tools/testing/kunit/kunit.py run --arch i386 See below for the specific problematic hunk. [0] https://lore.kernel.org/lkml/CA+G9fYtdXHVuirs3v6at3UoKNH5keuq0tpcvpz0tJFT4t… > Acked-by: Dave Hansen <dave.hansen(a)linux.intel.com> # x86 > Signed-off-by: Mike Rapoport (Microsoft) <rppt(a)kernel.org> > --- > arch/alpha/mm/init.c | 1 - > arch/arc/mm/init.c | 2 -- > arch/arm64/mm/init.c | 2 -- > arch/csky/mm/init.c | 1 - > arch/hexagon/mm/init.c | 6 ------ > arch/loongarch/kernel/numa.c | 1 - > arch/loongarch/mm/init.c | 2 -- > arch/microblaze/mm/init.c | 2 -- > arch/mips/mm/init.c | 2 -- > arch/nios2/mm/init.c | 6 ------ > arch/openrisc/mm/init.c | 2 -- > arch/parisc/mm/init.c | 1 - > arch/riscv/mm/init.c | 1 - > arch/s390/mm/init.c | 2 -- > arch/sh/mm/init.c | 7 ------- > arch/sparc/mm/init_32.c | 1 - > arch/sparc/mm/init_64.c | 2 -- > arch/um/kernel/um_arch.c | 1 - > arch/x86/kernel/setup.c | 2 -- > arch/x86/mm/init_32.c | 3 --- > arch/x86/mm/numa_32.c | 3 --- > arch/xtensa/mm/init.c | 2 -- > mm/memory.c | 8 -------- > mm/mm_init.c | 30 ++++++++++++++++++++++++++++++ > mm/nommu.c | 2 -- > 25 files changed, 30 insertions(+), 62 deletions(-) <snip> > diff --git a/arch/x86/mm/init_32.c b/arch/x86/mm/init_32.c > index 6d2f8cb9451e..801b659ead0c 100644 > --- a/arch/x86/mm/init_32.c > +++ b/arch/x86/mm/init_32.c > @@ -643,9 +643,6 @@ void __init initmem_init(void) > highstart_pfn = max_low_pfn; > printk(KERN_NOTICE "%ldMB HIGHMEM available.\n", > pages_to_mb(highend_pfn - highstart_pfn)); > - high_memory = (void *) __va(highstart_pfn * PAGE_SIZE - 1) + 1; > -#else > - high_memory = (void *) __va(max_low_pfn * PAGE_SIZE - 1) + 1; > #endif Reverting this hunk fixes the issue for me. > > memblock_set_node(0, PHYS_ADDR_MAX, &memblock.memory, 0);

3 weeks, 5 days

next-20250402: riscv/mm/tlbflush.c:195:23: error: 'start' redeclared as different kind of symbol

by Naresh Kamboju

Regressions on riscv builds tinyconfig, allnoconfig failed with toolchains clang-20 and gcc-13 on the Linux next starting from next-20250328. First seen on the next-20250328 Good: next-20250327 Bad: next-20250328..next-20250402 Regressions found on riscv: - build/gcc-13-tinyconfig - build/gcc-13-allnoconfig - build/clang-20-tinyconfig - build/clang-20-allnoconfig Regression Analysis: - New regression? Yes - Reproducibility? Yes Boot regression: riscv tlbflush.c error 'start' redeclared as different kind of symbol Reported-by: Linux Kernel Functional Testing <lkft(a)linaro.org> ## Build log arch/riscv/mm/tlbflush.c: In function 'arch_tlbbatch_add_pending': arch/riscv/mm/tlbflush.c:195:23: error: 'start' redeclared as different kind of symbol 195 | unsigned long start = uaddr & PAGE_MASK; | ^~~~~ arch/riscv/mm/tlbflush.c:193:53: note: previous definition of 'start' with type 'long unsigned int' 193 | struct mm_struct *mm, unsigned long start, unsigned long end) | ~~~~~~~~~~~~~~^~~~~ arch/riscv/mm/tlbflush.c:195:31: error: 'uaddr' undeclared (first use in this function) 195 | unsigned long start = uaddr & PAGE_MASK; | ^~~~~ arch/riscv/mm/tlbflush.c:195:31: note: each undeclared identifier is reported only once for each function it appears in ## Source * Kernel version: 6.14.0 * Git tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git * Git sha: fefb886b1344e222b3218f3c0165b0fd770e8b88 * Git describe: next-20250402 * Project details: https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20250402/ * Architectures: riscv * Toolchains: clang-20, gcc-13 * Kconfigs: tinyconfig, lkftconfig ## Build * Build log: https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20250402/te… * Build history: https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20250402/te… * Build details: https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20250402/te… * Build link: https://storage.tuxsuite.com/public/linaro/lkft/builds/2v9owDFW4gzrtyDZItZl… * Kernel config: https://storage.tuxsuite.com/public/linaro/lkft/builds/2v9owDFW4gzrtyDZItZl… ## Steps to reproduce - tuxmake --runtime podman --target-arch riscv --toolchain clang-20 --kconfig tinyconfig LLVM=1 LLVM_IAS=1 -- Linaro LKFT https://lkft.linaro.org

3 weeks, 6 days

clang-nightly: ERROR: modpost: "wcslen" [fs/smb/client/cifs.ko] undefined!

by Naresh Kamboju

Regressions on arm, powerpc, s390 defconfig builds failed with toolchain clang-nightly on the mainline master branch. First seen on the v6.14-12245-g91e5bfe317d8 Good: v6.14-11270-g08733088b566 Bad: v6.14-12245-g91e5bfe317d8 Regressions found on arm: - build/clang-nightly-nhk8815_defconfig Regressions found on powerpc: - build/clang-nightly-lkftconfig-lto-full - build/clang-nightly-ppc64e_defconfig - build/clang-nightly-lkftconfig-lto-thing - build/clang-nightly-defconfig - build/clang-nightly-lkftconfig-hardening Regressions found on s390: - build/clang-nightly-lkftconfig-lto-thing - build/clang-nightly-lkftconfig-lto-full - build/clang-nightly-defconfig - build/clang-nightly-lkftconfig-hardening Regression Analysis: - New regression? Yes - Reproducibility? Yes Build regression: arm powerpc s390 modpost "wcslen" fs smb client cifs.ko undefined Reported-by: Linux Kernel Functional Testing <lkft(a)linaro.org> ## Build log ERROR: modpost: "wcslen" [fs/smb/client/cifs.ko] undefined! ## Source * Kernel version: 6.14.0 * Git tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git * Git sha: 91e5bfe317d8f8471fbaa3e70cf66cae1314a516 * Git describe: v6.14-12245-g91e5bfe317d8 * Project details: https://qa-reports.linaro.org/lkft/linux-mainline-master/build/v6.14-12245-… * Arcitures: arm, powerpc, s390 * Toolchains: clang-nightly ## Build * Build log: https://qa-reports.linaro.org/lkft/linux-mainline-master/build/v6.14-12245-… * Build history: https://qa-reports.linaro.org/lkft/linux-mainline-master/build/v6.14-12245-… * Build details: https://qa-reports.linaro.org/lkft/linux-mainline-master/build/v6.14-12245-… * Build link: https://storage.tuxsuite.com/public/linaro/lkft/builds/2v9EdO7KHQCCZBICM0Mv… * Kernel config: https://storage.tuxsuite.com/public/linaro/lkft/builds/2v9EdO7KHQCCZBICM0Mv… ## Steps to reproduce - tuxmake --runtime podman --target-arch arm --toolchain clang-nightly --kconfig nhk8815_defconfig LLVM=1 LLVM_IAS=1 - tuxmake --runtime podman --target-arch powerpc --toolchain clang-nightly --kconfig defconfig LLVM=1 LLVM_IAS=0 LD=powerpc64le-linux-gnu-ld - tuxmake --runtime podman --target-arch s390 --toolchain clang-nightly --kconfig defconfig LLVM_IAS=1 -- Linaro LKFT https://lkft.linaro.org

3 weeks, 6 days

High-Quality Thermoplastic Road Marking Paint – Competitive Prices

by heyue pack

Dear Sir or Madam, Greetings to you, This is Heyue from Guangdong Bole Road Sign Technology Co., Ltd. in China. We specialize in manufacturing and supplying thermoplastic road marking paint and road marking machines, with over 15 years of experience in the industry. Our thermoplastic road marking paint is known for its high durability, strong reflectivity, and cost-effectiveness, making it an ideal choice for road safety projects. We also provide a range of road marking machines to meet different application needs. If you are interested in our products, please feel free to contact me at any time. Thanks and best regards, Heyue (Marketing Representative) Guangdong Bole Road Sign Technology Co., Ltd. 📍 Website: www.boleroadpaint.com 📞 Mob./WhatsApp: +86 13600459155 📧 Email: sales01(a)gdbllb.cn

3 weeks, 6 days

Daily cts/vts report for lkft - 2025-Apr-02

by lava＠validation.linaro.org

Total jobs: 142 Total errors: 27 (19.01%) LAVA errors: 0 (0.00%) Test errors: 26 (18.31%) Job errors: 0 (0.00%) Infra errors: 1 (0.70%) Canceled jobs: 0 (0.00%) Device type: dragonboard-845c Total jobs: 77 Total errors: 16 (20.78%) Error type: Test Error count: 16 (20.78%) Error: No match for error type 'Test', message 'lava-docker-test-shell timed out after 598 seconds' Count: 3 (3.90%) IDs: db845c-02: 8192807 db845c-09: 8193706 db845c-12: 8193756 Error: No match for error type 'Test', message 'The network seems not available, as the ping command failed' Count: 6 (7.79%) IDs: db845c-02: 8193700 db845c-04: 8192773 db845c-09: 8193661 8193676 8193683 8193685 Error: No match for error type 'Test', message 'lava-docker-test-shell timed out after 595 seconds' Count: 1 (1.30%) IDs: db845c-02: 8193684 Error: Device NOT found! Count: 3 (3.90%) IDs: db845c-02: 8192840 8193678 db845c-07: 8192841 Error: No match for error type 'Test', message 'lava-docker-test-shell timed out after 591 seconds' Count: 1 (1.30%) IDs: db845c-02: 8192857 Error: No match for error type 'Test', message 'lava-test-interactive timed out after 600 seconds' Count: 1 (1.30%) IDs: db845c-10: 8192854 Error: No match for error type 'Test', message 'tradefed - adb device lost[dd3b965f]' Count: 1 (1.30%) IDs: db845c-02: 8192811 Device type: qrb5165-rb5 Total jobs: 41 Total errors: 8 (19.51%) Error type: Test Error count: 8 (19.51%) Error: No match for error type 'Test', message 'lava-docker-test-shell timed out after 598 seconds' Count: 3 (7.32%) IDs: rb5-03: 8192776 8192873 rb5-07: 8192932 Error: Device NOT found! Count: 2 (4.88%) IDs: rb5-03: 8192792 8192850 Error: No match for error type 'Test', message 'tradefed - adb device lost[74d67c95]' Count: 2 (4.88%) IDs: rb5-03: 8192793 8192847 Error: No match for error type 'Test', message 'tradefed - adb device lost[d8a1879f]' Count: 1 (2.44%) IDs: rb5-07: 8192783 Device type: rk3399-rock-pi-4b Total jobs: 1 Total errors: 0 (0.00%) Device type: sm8550-hdk Total jobs: 23 Total errors: 3 (13.04%) Error type: Test Error count: 2 (8.70%) Error: No match for error type 'Test', message 'tradefed - adb device lost[124d1c34]' Count: 1 (4.35%) IDs: sm8550-hdk-01: 8191856 Error: No match for error type 'Test', message 'lava-docker-test-shell timed out after 899 seconds' Count: 1 (4.35%) IDs: sm8550-hdk-01: 8191025 Error type: Infrastructure Error count: 1 (4.35%) Error: Connection closed Count: 1 (4.35%) IDs: sm8550-hdk-01: 8191026

3 weeks, 6 days

Daily report for validation - 2025-Apr-02

by lava＠validation.linaro.org

Total jobs: 116 Total errors: 13 (11.21%) LAVA errors: 0 (0.00%) Test errors: 0 (0.00%) Job errors: 13 (11.21%) Infra errors: 0 (0.00%) Canceled jobs: 0 (0.00%) Device type: dragonboard-845c Total jobs: 14 Total errors: 0 (0.00%) Device type: dragonboard-410c Total jobs: 11 Total errors: 10 (90.91%) Error type: Job Error count: 10 (90.91%) 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: 10 (90.91%) IDs: dragonboard-410c-01: 4140404 4140420 4140438 4140470 4140473 4140489 4140497 4140513 4140530 4140547 Device type: x15 Total jobs: 32 Total errors: 3 (9.38%) Error type: Job Error count: 3 (9.38%) Error: No match for error type 'Job', message 'login-action timed out after 275 seconds' Count: 2 (6.25%) IDs: x15-01: 4140463 4140464 Error: No match for error type 'Job', message 'login-action timed out after 274 seconds' Count: 1 (3.12%) IDs: x15-01: 4140427 Device type: beaglebone-black Total jobs: 38 Total errors: 0 (0.00%) Device type: bcm2837-rpi-3-b-32 Total jobs: 19 Total errors: 0 (0.00%) Device type: imx93-11x11-evk Total jobs: 1 Total errors: 0 (0.00%) Device type: hi6220-hikey-r2 Total jobs: 1 Total errors: 0 (0.00%)

3 weeks, 6 days

Daily cts/vts report for lkft - 2025-Apr-01

by lava＠validation.linaro.org

Total jobs: 173 Total errors: 35 (20.23%) LAVA errors: 0 (0.00%) Test errors: 33 (19.08%) Job errors: 1 (0.58%) Infra errors: 1 (0.58%) Canceled jobs: 0 (0.00%) Device type: dragonboard-845c Total jobs: 94 Total errors: 22 (23.40%) Error type: Test Error count: 22 (23.40%) Error: No match for error type 'Test', message 'lava-test-interactive timed out after 1500 seconds' Count: 12 (12.77%) IDs: db845c-01: 8192016 db845c-02: 8191951 db845c-03: 8192022 db845c-04: 8191960 db845c-06: 8191947 db845c-07: 8191957 8191969 db845c-11: 8191949 db845c-12: 8191536 db845c-13: 8191531 8191971 db845c-14: 8191537 Error: Device NOT found! Count: 4 (4.26%) IDs: db845c-02: 8191052 8191510 8191906 db845c-11: 8191926 Error: No match for error type 'Test', message 'lava-docker-test-shell timed out after 594 seconds' Count: 1 (1.06%) IDs: db845c-02: 8191914 Error: No match for error type 'Test', message 'lava-docker-test-shell timed out after 598 seconds' Count: 3 (3.19%) IDs: db845c-02: 8190982 8191010 8191193 Error: No match for error type 'Test', message 'tradefed - adb device lost[dd3b965f]' Count: 1 (1.06%) IDs: db845c-02: 8191002 Error: No match for error type 'Test', message 'lava-docker-test-shell timed out after 586 seconds' Count: 1 (1.06%) IDs: db845c-02: 8191000 Device type: qrb5165-rb5 Total jobs: 56 Total errors: 13 (23.21%) Error type: Test Error count: 11 (19.64%) Error: No match for error type 'Test', message 'lava-docker-test-shell timed out after 1498 seconds' Count: 2 (3.57%) IDs: rb5-03: 8191962 8191968 Error: Device NOT found! Count: 5 (8.93%) IDs: rb5-03: 8190993 8191044 8191911 8191952 rb5-07: 8190994 Error: No match for error type 'Test', message 'tradefed - adb device lost[4fc7b22]' Count: 1 (1.79%) IDs: rb5-06: 8191946 Error: No match for error type 'Test', message 'lava-docker-test-shell timed out after 598 seconds' Count: 1 (1.79%) IDs: rb5-03: 8191884 Error: No match for error type 'Test', message 'tradefed - adb device lost[d8a1879f]' Count: 1 (1.79%) IDs: rb5-07: 8191877 Error: No match for error type 'Test', message 'lava-docker-test-shell timed out after 592 seconds' Count: 1 (1.79%) IDs: rb5-06: 8190996 Error type: Infrastructure Error count: 1 (1.79%) Error: Connection closed Count: 1 (1.79%) IDs: rb5-05: 8191967 Error type: Job Error count: 1 (1.79%) Error: No match for error type 'Job', message 'login-action timed out after 873 seconds' Count: 1 (1.79%) IDs: rb5-07: 8190997 Device type: rk3399-rock-pi-4b Total jobs: 1 Total errors: 0 (0.00%) Device type: x86 Total jobs: 1 Total errors: 0 (0.00%) Device type: sm8550-hdk Total jobs: 21 Total errors: 0 (0.00%)

4 weeks

Daily report for validation - 2025-Apr-01

by lava＠validation.linaro.org

Total jobs: 143 Total errors: 13 (9.09%) LAVA errors: 0 (0.00%) Test errors: 0 (0.00%) Job errors: 13 (9.09%) Infra errors: 0 (0.00%) Canceled jobs: 0 (0.00%) Device type: dragonboard-410c Total jobs: 13 Total errors: 12 (92.31%) Error type: Job Error count: 12 (92.31%) 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: 12 (92.31%) IDs: dragonboard-410c-01: 4140192 4140216 4140228 4140251 4140260 4140276 4140289 4140316 4140333 4140339 4140370 4140383 Device type: dragonboard-845c Total jobs: 16 Total errors: 0 (0.00%) Device type: x15 Total jobs: 38 Total errors: 1 (2.63%) Error type: Job Error count: 1 (2.63%) Error: No match for error type 'Job', message 'login-action timed out after 274 seconds' Count: 1 (2.63%) IDs: x15-01: 4140234 Device type: beaglebone-black Total jobs: 49 Total errors: 0 (0.00%) Device type: bcm2837-rpi-3-b-32 Total jobs: 25 Total errors: 0 (0.00%) Device type: imx93-11x11-evk Total jobs: 1 Total errors: 0 (0.00%) Device type: hi6220-hikey-r2 Total jobs: 1 Total errors: 0 (0.00%)

4 weeks

2025

2024

2023

2022

2021

2020

2019

2018

2017

Lkft-triage April 2025