https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260406
--- Comment #57 from tech-li...@zyxst.net --- Hi, Reporting that the rpi4 arm64.aarch64 is still running ok. I did however encounter a similar error with an amd64-based bhyve vm. This vm is unmodified in comparison to the arm64.aarch64 device. It runs 13.0-p5 and updates via freebsd-update. The symptoms were a bit different though, in that: 1. the script ran without error 2. no services were accessible. No ping, smtp, nothing, from anywhere. (this is the best failure mode honestly. The worst nightmare would be not-to-load-leaving-everything-open). I checked the tables for blocked IPs and made sure my accessing IP wasn't listed and it wasn't. 3. on reboot, services didn't come back. I had to access via the console. I was able to bring services back by disabling pf, updating the ruleset then re-enabling it. maybe this would need a different ticket & diags -- You are receiving this mail because: You are the assignee for the bug.