Date: Sat, 29 Jul 2023 08:05:06 +0000 From: Pero Orsolic <bsd@orsolic.org> To: "freebsd-current@freebsd.org" <freebsd-current@freebsd.org> Subject: CURRENT with ZFS not bootable when built with LLVM from ports Message-ID: <ui0Ay3uhHlE2HZBGBJ_iXxvvbu_sHYBfeysm0KypBOW0fitwvS2kH70GxWVqUgg2Q3r1vGGptMjv_T8Wcf3wCDh-3pkbYtFxt6bvBDGGWGA=@orsolic.org>
next in thread | raw e-mail | index | archive | help
Building -CURRENT (2023-07-17 be4c7f273508) without system compiler (with L= LVM16 from ports) results in unbootable system:Preloaded elf kernel "/boot/= kernel/kernel" at 0xffffffff82328000. Preloaded elf obj module "/boot/kernel/zfs.ko" at 0xffffffff82329090. Preloaded boot_entropy_cache "/boot/entropy" at 0xffffffff823298f8. Preloaded elf obj module "/boot/kernel/cryptodev.ko" at 0xffffffff82329950. Preloaded hostuuid "/etc/hostid" at 0xffffffff8232a140. kldload: unexpected relocation type 42, symbol index 8662 link_elf_obj: symbol __stack_chk_guard undefined KLD file zfs.ko - could not finalize loading Patching and rebuilding LLVM16 with this patch results in bootable system: Patch was taken from: https://cgit.freebsd.org/src/commit/?h=3Dstable/13&id=3De8e5d75e6a9676e76c3= bfd6d1d52561ffbb40846 Few months ago it was possible to use LLVM from ports to build kernel and w= orld, but I don't remember the details. This patch was tested in bhyve VM and on real hardware. On real hardware it was possible to boot system without patched compiler wh= en zfs.ko (options ZFS and GEOM_ELI with devices crypto and cryptodev) is b= uilt into the kernel. But then other modules (acpi_ibm, iic, drm, i915kms, acpi_video, ... pf, va= rious ng_* and so on) will fail to load with same reason. Didn't try including zfs.ko into the kernel in the VM. Bug report: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D272740
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ui0Ay3uhHlE2HZBGBJ_iXxvvbu_sHYBfeysm0KypBOW0fitwvS2kH70GxWVqUgg2Q3r1vGGptMjv_T8Wcf3wCDh-3pkbYtFxt6bvBDGGWGA=>