Re: Heads-up: Kernel module symbol resolution changing

On Mon, 31 Mar 2025 10:57:45 -0400 Ed Maste wrote: > On Fri, 14 Mar 2025 at 23:03, Tomoaki AOKI wrote: > > > > On Wed, 12 Mar 2025 13:07:58 -0400 > > Ed Maste wrote: > > > > > Our in-kernel module linker currently performs symbol resolution > > > against local symbols from other modules, which

Can't enable IRQ/MSI because no handler is installed

Dear followers of the main, I updated my desktop on Sunday, March 30th, to commit |83d13d836b32af86bba62ddf86c2ef78389d13fd|. The previous update was on March 21st, so only a small number of commits were added to the main repository in between. FWIW: Everything appears to be functioning corr

FreeBSD-15.0-CURRENT-arm64-aarch64-zfs.vhd.xz fails to boot under Hyper-V v2 on Windows 11 Pro; possibly tied to: "stand: add comconsole backwards compatibility shim for aarch64"

In order to try to help test: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=285681 I again tried to get main FreeBSD booting on the Windows DevKit 2023 under Windows 11 Pro, this time using: FreeBSD-15.0-CURRENT-arm64-aarch64-zfs.vhd.xz (expanded to .vhd and then the .vhd converted to .vhdx