I'm tracking head/amd64 daily twice on each of two machines: my "build machine" ("freebeast") and my laptop, each first using the traditional Forth loader, then (on a different slice), the Lua loader. Each is using BIOS and MBR (not UEFI; not GPT). Yesterday's update was to r337738, and was uneventful for each of the four environments. Today's was to r337834, and was uneventful for the build machine (both Forth and Lua loaders -- though there remains no means of interacting with the loader on the build machine if it's booted using the Lua loader). The laptop had no issues using the Forth loader, but the boot process was ... severely abbreviated ... using the Lua loader. I don't have a serial consoloe on the laptop, so I snapped a photo; it may be found at <http://www.catwhisker.org/~david/FreeBSD/head/r337834/BYX_halted.jpg>. As the name suggests, the final message was: BTX halted at which point, I found no way to get the laptop to respond to anything but a power cycle. Additional information (including, e.g., a verbose dmesg.boot from the laptop running: FreeBSD g1-215.catwhisker.org 12.0-ALPHA1 FreeBSD 12.0-ALPHA1 #80 r337834M/337834:1200077: Wed Aug 15 04:34:45 PDT 2018 root_at_g1-215.catwhisker.org:/common/S4/obj/usr/src/amd64.amd64/sys/CANARY amd64 -- using the Forth loader) may be found at <http://www.catwhisker.org/~david/FreeBSD/history/>. Peace, david -- David H. Wolfskill david_at_catwhisker.org Trump is gaslighting us: https://www.bbc.com/news/world-us-canada-44959300 See http://www.catwhisker.org/~david/publickey.gpg for my public key.
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:41:17 UTC
