Me too , I remember something like that during a recent update - not so sure for the cryptsetup warning but Iam almost sure I saw "The initramfs will attempt to resume from /dev/sda2" (it is my swap partition).
Best Regards

I too got that update and updated it after updating i am having problem with chromium browser the search bar in the chromium browser is blinking before updating to that it was fine but after this update it became very difficult to use chromium browser i think there may be a solution for downgrading to this i searched in google and found that this problem is due to driver update

those messages happen when the initramfs, which is initial ram drive that boots the rest of the system, requires updating. this happens with the intel-microcode update. intel-microcode updates intel cpu firmware.

all the resume message means is that if you use hibernate, the kernel will try to resume from the device indicated (swap partition) unless you override it with the RESUME boot code.

the cyrptsetup "warn" is expected.

so all that is perfectly normal.

the intel-microcode package has updated twice in the last week.

as to the chromium issues, well all the spectre and meltdown stuff has everything in flux, with updates coming all the time.

To reiterate as D+O has said this is a moving target. MY AMD does a little better than my intel machine with Spectre still vulnerable in all cases while the AMD only shows the first test vulnerable. So you should not think the latest intel-microcode solves all issues.

There's a new amd64-microcode in upstream Debian, the first in quite a while, which no doubt adds some Spectre protection. We are going to backport it, but

WARNING: requires at least kernel 4.15, 4.14.13, 4.9.76, 4.4.111 (or a
backport of commit f4e9b7af0cd58dd039a0fb2cd67d57cea4889abf
"x86/microcode/AMD: Add support for fam17h microcode loading") otherwise
it will not be applied to the processor.

so we'll have to patch and rebuild the 4.14 kernel to add Ryzen support for the microcode update. The 4.14-13 Liquorix kernels we building now already have that support already. Debian will no doubt eventually also add support in those older kernel versions.