Toomas Soome

We do not need UEFI vars or "well known" memory areas - we do have loader environment passed to kernel and we can use that mechanism just fine. The variables...

> Great. So one would need to: > > * Write code to compute and export the needed loader variables (can this be done in lua or is this only/better...

> I don't object to Ventoy, but would like to see if there's a way we can handle the kernel's side of map-vdisk without relying on Ventoy. (@tsoome I'm curious...

> @tsoome can you point us to a FreeBSD ISO which has the latest bootloader so we can retest it there? either current or 13 stable - latest version. I'd...

> Thanks. Added them to the overview above. Did you update the firmware on your Macs to the latest version provided by Apple for those models? > > Next step:...

> Yes, helloSystem is based on 13.0-RELEASE. Aye, well, the 13.1 is about to go to release build cycle. But you can test with one of latest current images, so...

> You might want to port the other commit too, since it is a performance improvement. Yes, it is still waiting in my queue....

> Recently, coverity static analysis found a use-after-free bug in the btree code in openzfs/zfs. It had been detected causing problems in the wild on debug builds in 2020: >...

Is that system using ECC RAM? Memory problems (if it is memory problem) can appear at any time, so several months old memtest run is only telling that memory was...

ok, no ECC errors and two similar stack traces... tbh, I find it hard to believe it is memory corruption. Exactly the same function pointer getting zeroed in those two...