Why does ubuntu 20.04 freeze when resuming from hibernation?

Question

linux

On a huawei MateBook D14 laptop with ubuntu 20.04, sometimes the system freezes after waking up from sleep mode. Doesn't respond to keyboard and mouse clicks. Only a hard reboot helps. It doesn't happen often, maybe a couple of times a month.
The dmesg output shows the following:

dmesg -l err,warn
[ 0.473827] pci 0000:00:00.2: can't derive routing for PCI INT A
[ 0.473829] pci 0000:00:00.2: PCI INT A: not connected
[ 0.642056] i8042 : PNP: PS/2 appears to have AUX port disabled, if this is incorrect please boot with i8042.nopnp
[ 0.644971] platform eisa.0: EISA: Cannot allocate resource for mainboard
[ 0.644973] platform eisa.0: Cannot allocate resource for EISA slot 1
[ 0.644974] platform eisa.0: Cannot allocate resource for EISA slot 2
[ 0.644976] platform eisa.0: Cannot allocate resource for EISA slot 3
[ 0.644977] platform eisa.0: Cannot allocate resource for EISA slot 4
[ 0.644978] platform eisa .0: Cannot allocate resource for EISA slot 5
[ 0.644979] platform eisa.0: Cannot allocate resource for EISA slot 6
[ 0.644981] platform eisa.0: Cannot allocate resource for EISA slot 7
[ 0.644982] platform eisa.0: Cannot allocate resource for EISA slot 8
[ 0.850287] i2c_hid i2c-ELAN2204:00: supply vdd not found, using dummy regulator
[ 0.850337] i2c_hid i2c-ELAN2204:00: supply vddl not found, using dummy regulator
[ 0.870364] nvme nvme0: missing or invalid SUBNQN field.
[ 3.190059] systemd-journald[396]: File /var/log/journal/1d262f721d7aa919dc9d471361389336/system.journal corrupted or uncleanly shut down, renaming and replacing.
[ 3.389297] FAT-fs (nvme0n1p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[ 10.370081] systemd-journald[396]: File /var/log/journal/1d262f721d7aa919dc9d471361389336/user-1000.journal corrupted or uncleanly shut down, renaming and replacing.

I understand correctly that there is some kind of problem with the disk?

Answer 1

For the first time in 10 years I saw an uncleanly shut down and was very surprised, I thought if the log was disabled, and then I looked closely and saw a FAT in which there is no log.
The device was turned off incorrectly and garbage was written to the disk. Do fsck as he suggests.