Jammy kernel crashes on SiFive HiFive Unmatched

[Heinrich Schuchardt]

I am testing the daily preinstalled Ubuntu image on the SiFive HiFive Unmatched board.

After resetting I see the following:

Begin: Running /scripts/local-bottom ... done.
Begin: Running /scripts/init-bottom ... y^done.
[ 27.626148] request_module: kmod_concurrent_max (0) close to 0 (max_modprobes: 50), for module binfmt-464c, throttling...
run-init[ 32.748312] request_module: modprobe binfmt-464c cannot be processed, kmod busy with 50 threads for more than 5 seconds now
[ 32.763928] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000100
[ 32.782575] CPU: 0 PID: 1 Comm: run-init Not tainted 5.19.0-1012-generic #13~22.04.1-Ubuntu
[ 32.790908] Hardware name: SiFive HiFive Unmatched A00 (DT)
[ 32.796463] Call Trace:
[ 32.798895] [<ffffffff800061d8>] dump_backtrace+0x30/0x42
[ 32.804279] [<ffffffff80af92fe>] show_stack+0x40/0x52
[ 32.809317] [<ffffffff80b02194>] dump_stack_lvl+0x44/0x62
[ 32.814702] [<ffffffff80b021ca>] dump_stack+0x18/0x22
[ 32.819740] [<ffffffff80af9812>] panic+0x11c/0x30a
[ 32.824517] [<ffffffff8001e8bc>] do_exit+0x462/0x468
[ 32.829468] [<ffffffff8001ea00>] do_group_exit+0x38/0x94
[ 32.834766] [<ffffffff8001ea88>] __wake_up_parent+0x0/0x3c
[ 32.840239] [<ffffffff80003c62>] ret_from_syscall+0x0/0x2
[ 32.845627] SMP: stopping secondary CPUs
[ 32.849549] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000100 ]---
: can't execute '/sbin/init': Exec format error

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-5.19.0-1012-generic 5.19.0-1012.13~22.04.1
ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7
Uname: Linux 5.19.0-21-generic riscv64
ApportVersion: 2.20.11-0ubuntu82.3
Architecture: riscv64
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Thu Feb 2 14:15:58 2023
SourcePackage: linux-riscv-5.19
UpgradeStatus: No upgrade log present (probably fresh install)

[Heinrich Schuchardt (xypron)]

The appendices were collected when mounting the SD-card on an x86_64 in a chroot.

[Heinrich Schuchardt (xypron)]

Please, find appended the console output showing the crashes.

[Heinrich Schuchardt (xypron)]

The error was caused by an USB stick having the same partition label as the SD-card.

We should change our installers to create UUIDs for partitions and write them to /etc/fstab to avoid such problems.

Closing as invalid.

[Dimitri John Ledkov (xnox)]

We have a specification for this - https://wiki.ubuntu.com/FSTAB but I don't know if it needs updating or has regressed somewhere.

[Dimitri John Ledkov (xnox)]

hm, i wonder if this is a u-boot only issue, or lack of running update-grub.

the preinstalled images / installer media may boot with rootfs referenced by label; but then they should update to be bootable by-UUID upon kernel or grub updates; or call to update-grub.

Not sure if we do something like that on riscv64 already / yet, and or explicitely on u-boot-menu images.

[Heinrich Schuchardt (xypron)]

On RISC-V the preinstalled media don't update fstab to use UUIDs.

grub-install, grup-update writes UUIDs. But these are not unique at all when you have copied the preinstalled image to your SD-card.