On Fri, Jan 26, 2018 at 04:29:47AM -0800, David Wolfskill wrote: > This is on my "build machine" (laptop is still building updated ports > for today, so I don't know yet whether or not it encounters this.) > ....
The laptop did the same source-based update, and did not exhibit the
panic.
(On the laptop) following the "make delete-old-libs", I did a normal
"shutdown -r now" (as I normally continue using the laptop throughout
the day); when it started to boot, I coerced it to boot head again, then
logged in an ran "poweroff" -- to which it complied without issue.
The build machine went from
FreeBSD 12.0-CURRENT #83 r328393M/328393:1200056: Thu Jan 25 04:37:47 PST 2018
[email protected]:/common/S4/obj/usr/src/amd64.amd64/sys/GENERIC
amd64
to
FreeBSD 12.0-CURRENT #84 r328436M/328436:1200056: Fri Jan 26 04:02:06 PST 2018
[email protected]:/common/S4/obj/usr/src/amd64.amd64/sys/GENERIC
amd64
The laptop went from
FreeBSD 12.0-CURRENT #80 r328393M/328393:1200056: Thu Jan 25 04:56:41 PST 2018
[email protected]:/common/S4/obj/usr/src/amd64.amd64/sys/CANARY
amd64
to
FreeBSD 12.0-CURRENT #81 r328436M/328436:1200056: Fri Jan 26 05:41:19 PST 2018
[email protected]:/common/S4/obj/usr/src/amd64.amd64/sys/CANARY
amd64
Peace,
david
--
David H. Wolfskill [email protected]
"unfortunately, no trust!” -- well, of course! You reap what you sow.
See http://www.catwhisker.org/~david/publickey.gpg for my public key.
signature.asc
Description: PGP signature
