Return-Path: Received: from mail-ed1-x52e.google.com (mail-ed1-x52e.google.com [IPv6:2a00:1450:4864:20::52e]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mail.server123.net (Postfix) with ESMTPS for ; Tue, 15 Dec 2020 11:42:39 +0100 (CET) Received: by mail-ed1-x52e.google.com with SMTP id r5so20442813eda.12 for ; Tue, 15 Dec 2020 02:42:39 -0800 (PST) Received: from [192.168.1.3] (93-48-172-72.ip258.fastwebnet.it. [93.48.172.72]) by smtp.googlemail.com with ESMTPSA id h16sm1051588eji.110.2020.12.15.02.42.38 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 15 Dec 2020 02:42:38 -0800 (PST) From: Germano Massullo Message-ID: Date: Tue, 15 Dec 2020 11:42:37 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: quoted-printable Content-Language: en-US Subject: [dm-crypt] LUKS2 SSD swap and system freeze List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: dm-crypt@saout.de 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. =A0 type:=A0=A0=A0 LUKS2 =A0 cipher:=A0 aes-xts-plain64 =A0 keysize: 512 bits =A0 key location: keyring =A0 device:=A0 /dev/sdc =A0 sector size:=A0 512 =A0 offset:=A0 32768 sectors =A0 size:=A0=A0=A0 500085424 sectors =A0 mode:=A0=A0=A0 read/write =A0 flags:=A0=A0 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 =3D=3D=3D=3D=3D=3D=3D=3D Message from syslogd@localhost at Dec 15 01:14:32 ... =A0kernel:watchdog: BUG: soft lockup - CPU#0 stuck for 124s! [0x564a0d4baad0-:1924] =3D=3D=3D=3D=3D=3D=3D=3D 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