ddb panic on 7.3 after applying 2023-07-24 zenbleed patches

Hey gang,

After applying today's zenbleed patches and running fw_update and
installboot -v sd0, ALL of our AMD servers running 7.3 at Vultr that
were--as part of the patch process--rebooted are now dead in the water and
won't boot.

Intel Vultr virtual machines appear to be unaffected, as are all of my
Intel bare metal machines, laptops, desktops, and servers alike.

(Thankfully, with one exception everything running an AMD cpu is redundant
OR the patches have been applied but haven't yet been rebooted, so we're
not completely dead in the water.... just close.

I was waiting for the machines to come up after reboot to reboot the
sibling servers, which are now patched but not being rebooted 'til we have
a fix.)

All machines are single CPU and were rebooted via SSH (and when that didn't
work via the Vultr console).

All ddbs look similar to these. (Sorry for the screenshots, but it's the
best I can do given these are remote virtual instances.)

[image: Screen Shot 2023-07-24 at 23.18.40.png]
[image: Screen Shot 2023-07-24 at 23.19.10.png]
[image: Screen Shot 2023-07-24 at 23.19.27.png]
[image: Screen Shot 2023-07-24 at 23.19.40.png]


Any developer who wants access to one of our machines is welcome to it.

We can also easily provision a new instance with 7.3 so someone can get in
and break shit as needed.

All affected machines are Vultr's "1024.00 MB AMD High Performance"
instances.

Available to help any way I can.

Thanks,
Kevin
P.S. If this is a PEBKAC on my part, I'm happy to take the requisite 50+
lashes with the clue stick.