From: Germano Massullo <germano.massullo@gmail.com>
To: dm-crypt@saout.de
Subject: [dm-crypt] LUKS2 SSD swap and system freeze
Date: Tue, 15 Dec 2020 11:42:37 +0100 [thread overview]
Message-ID: <de03f33e-76cb-7eb5-836f-438815515beb@gmail.com> (raw)
Good day. I am investigating about a weird behavior of my system that
leads to frequent freezes.
The main components of my system are: Fedora 33 (kernel
5.9.13-200.fc33.x86_64), cryptsetup 2.3.4, an AMD Ryzen 5 3600, 16 GB
RAM 3200 MHz, a Samsung 860 PRO used for 32 GB swap and LVM Cache, that
is encrypted with following criteria:
# cryptsetup status ssd_cache
/dev/mapper/ssd_cache is active and is in use.
type: LUKS2
cipher: aes-xts-plain64
keysize: 512 bits
key location: keyring
device: /dev/sdc
sector size: 512
offset: 32768 sectors
size: 500085424 sectors
mode: read/write
flags: discards
During write bursts of swap (for example when booting some virtual
machines), the system completely freezes, I cannot even move the mouse
pointer. The system may remain in stuck state even for 10 minutes. When
the (host) system turns back to normal, I can see for example in virtual
machines, the following error in console
========
Message from syslogd@localhost at Dec 15 01:14:32 ...
kernel:watchdog: BUG: soft lockup - CPU#0 stuck for 124s!
[0x564a0d4baad0-:1924]
========
To check if the complete stuck of the system was caused by encryption, I
tried to disable SSD swap, and create a unencrypted swap on a regular
HDD, and then when I had write bursts, the system slowed, but it did not
freeze.
How could I proceed in my investigation to find out if it is a matter of
system configuration, a bug, etc.?
Thank you
WARNING: multiple messages have this Message-ID (diff)
From: Germano Massullo <germano.massullo@gmail.com>
To: dm-crypt@saout.de
Subject: [dm-crypt] LUKS2 SSD swap and system freeze
Date: Tue, 15 Dec 2020 11:42:37 +0100 [thread overview]
Message-ID: <de03f33e-76cb-7eb5-836f-438815515beb@gmail.com> (raw)
Message-ID: <20201215104237.ZvAkK6iwyax75Sdf3zbI_EI3TfiJXXQp4lQow3gzHTI@z> (raw)
Good day. I am investigating about a weird behavior of my system that
leads to frequent freezes.
The main components of my system are: Fedora 33 (kernel
5.9.13-200.fc33.x86_64), cryptsetup 2.3.4, an AMD Ryzen 5 3600, 16 GB
RAM 3200 MHz, a Samsung 860 PRO used for 32 GB swap and LVM Cache, that
is encrypted with following criteria:
# cryptsetup status ssd_cache
/dev/mapper/ssd_cache is active and is in use.
type: LUKS2
cipher: aes-xts-plain64
keysize: 512 bits
key location: keyring
device: /dev/sdc
sector size: 512
offset: 32768 sectors
size: 500085424 sectors
mode: read/write
flags: discards
During write bursts of swap (for example when booting some virtual
machines), the system completely freezes, I cannot even move the mouse
pointer. The system may remain in stuck state even for 10 minutes. When
the (host) system turns back to normal, I can see for example in virtual
machines, the following error in console
========
Message from syslogd@localhost at Dec 15 01:14:32 ...
kernel:watchdog: BUG: soft lockup - CPU#0 stuck for 124s!
[0x564a0d4baad0-:1924]
========
To check if the complete stuck of the system was caused by encryption, I
tried to disable SSD swap, and create a unencrypted swap on a regular
HDD, and then when I had write bursts, the system slowed, but it did not
freeze.
How could I proceed in my investigation to find out if it is a matter of
system configuration, a bug, etc.?
Thank you
_______________________________________________
dm-crypt mailing list
dm-crypt@saout.de
https://www.saout.de/mailman/listinfo/dm-crypt
next reply other threads:[~2020-12-15 10:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-15 10:42 Germano Massullo [this message]
2020-12-15 10:42 ` [dm-crypt] LUKS2 SSD swap and system freeze Germano Massullo
2020-12-15 11:59 ` Michael Kjörling
2020-12-15 11:59 ` Michael Kjörling
2020-12-22 13:31 ` Milan Broz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=de03f33e-76cb-7eb5-836f-438815515beb@gmail.com \
--to=germano.massullo@gmail.com \
--cc=dm-crypt@saout.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).