Here, systemd-journal has triggered a page fault (the persistent log
file is mmap'ed) and goes into uninterruptible sleep while the kernel
attempts to load a page from the recently locked dm-crypt device.
This operation will hang, and since the journal process can not receive
signals, the machine never enters suspend-to-RAM.
While this problem is not particular to systemd-journal, it is the
most frequent trigger for the problem as the journal is recording the
operations of the suspend operation as it happens.
The deeper issue of IO on the crypt device after freezing, but before
machine suspend, is not addressed here.
Attempting to sleep a busy system often causes a suspend to fail with the following error:
Here, systemd-journal has triggered a page fault (the persistent log file is mmap'ed) and goes into uninterruptible sleep while the kernel attempts to load a page from the recently locked dm-crypt device.
This operation will hang, and since the journal process can not receive signals, the machine never enters suspend-to-RAM.
While this problem is not particular to systemd-journal, it is the most frequent trigger for the problem as the journal is recording the operations of the suspend operation as it happens.
The deeper issue of IO on the crypt device after freezing, but before machine suspend, is not addressed here.