[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <CA+G9fYtqv_S+nK2cZB623yUuQS7HL18ELARpq_6W3_5m9ci7zA@mail.gmail.com>
Date: Fri, 31 Jan 2025 16:07:24 +0530
From: Naresh Kamboju <naresh.kamboju@...aro.org>
To: open list <linux-kernel@...r.kernel.org>, lkft-triage@...ts.linaro.org,
Linux Regressions <regressions@...ts.linux.dev>, Netdev <netdev@...r.kernel.org>
Cc: Kunihiko Hayashi <hayashi.kunihiko@...ionext.com>, Yanteng Si <si.yanteng@...ux.dev>,
Paolo Abeni <pabeni@...hat.com>, Arnd Bergmann <arnd@...db.de>,
Dan Carpenter <dan.carpenter@...aro.org>, Theodore Grey <theodore.grey@...aro.org>,
Anders Roxell <anders.roxell@...aro.org>
Subject: next-20250129: rk3399-rock-pi-4b NFS mount and boot failed
The arm64 rk3399-rock-pi-4b boot failed on Linux next-20250129
while mounting rootfs via NFS. Whereas other arm64 devices boot fine.
rk3399-rock-pi-4b:
boot:
* gcc-13-lkftconfig
First seen on the the Linux next-20250129..next-20250130
Good: next-20250128
Bad: next-20250129
Theodore Grey bisected this to,
first bad commit:
[8865d22656b442b8d0fb019e6acb2292b99a9c3c]
net: stmmac: Specify hardware capability value when FIFO size isn't specified
Anyone have noticed this boot problem on rk3399-rock-pi-4b running the
Linux next-20250129 and next-20250130 kernel.
Boot regression: arm64 rk3399-rock-pi-4b nfs mount and boot failed
Reported-by: Linux Kernel Functional Testing <lkft@...aro.org>
Boot log:
----
[ 0.000000] Linux version 6.13.0-next-20250129 (tuxmake@...make)
(aarch64-linux-gnu-gcc (Debian 13.3.0-5) 13.3.0, GNU ld (GNU Binutils
for Debian) 2.43.50.20241215) #1 SMP PREEMPT @1738124074
[ 0.000000] KASLR disabled due to lack of seed
[ 0.000000] Machine model: Radxa ROCK Pi 4B
...
[ 111.599122] VFS: Unable to mount root fs via NFS.
[ 111.599909] devtmpfs: mounted
[ 111.625869] Freeing unused kernel memory: 4800K
[ 111.626817] Run /sbin/init as init process
[ 111.627364] Run /etc/init as init process
[ 111.627858] Run /bin/init as init process
[ 111.628350] Run /bin/sh as init process
[ 111.628828] Kernel panic - not syncing: No working init found. Try
passing init= option to kernel. See Linux
Documentation/admin-guide/init.rst for guidance.
[ 111.630076] CPU: 0 UID: 0 PID: 1 Comm: swapper/0 Not tainted
6.13.0-next-20250129 #1
[ 111.630769] Hardware name: Radxa ROCK Pi 4B (DT)
[ 111.631185] Call trace:
[ 111.631411] show_stack+0x20/0x38 (C)
[ 111.631761] dump_stack_lvl+0x34/0xd0
[ 111.632110] dump_stack+0x18/0x28
[ 111.632428] panic+0x3b8/0x420
[ 111.632716] kernel_init+0x1ac/0x1f0
[ 111.633052] ret_from_fork+0x10/0x20
[ 111.633395] SMP: stopping secondary CPUs
[ 111.633894] Kernel Offset: disabled
[ 111.634209] CPU features: 0x100,0000002c,00800000,8200421b
[ 111.634701] Memory Limit: none
[ 111.634985] ---[ end Kernel panic - not syncing: No working init
found. Try passing init= option to kernel. See Linux
Documentation/admin-guide/init.rst for guidance. ]---
metadata:
---
kernel: 6.13.0
git_repo: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
git_sha: da7e6047a6264af16d2cb82bed9b6caa33eaf56a
git_describe: next-20250129
test details: https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20250129
boot log: https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20250129/testrun/27058414/suite/boot/test/gcc-13-lkftconfig-no-kselftest-frag/log
details: https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20250129/testrun/27058414/suite/boot/test/gcc-13-lkftconfig-no-kselftest-frag/details/
history: https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20250129/testrun/27058414/suite/boot/test/gcc-13-lkftconfig-no-kselftest-frag/history/
test job link: https://lkft.validation.linaro.org/scheduler/job/8100579
--
Linaro LKFT
https://lkft.linaro.org
Powered by blists - more mailing lists