From mboxrd@z Thu Jan 1 00:00:00 1970 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 From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.0 required=3.0 tests=BAYES_00,DKIM_ADSP_CUSTOM_MED, DKIM_INVALID,DKIM_SIGNED,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, URIBL_BLOCKED,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 45C42C4361B for ; Tue, 15 Dec 2020 10:43:32 +0000 (UTC) Received: from mail.server123.net (mail.server123.net [78.46.64.186]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 7F47F20782 for ; Tue, 15 Dec 2020 10:43:30 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 7F47F20782 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=gmail.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=dm-crypt-bounces@saout.de X-Virus-Scanned: amavisd-new at saout.de Authentication-Results: mail.server123.net (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=2a00:1450:4864:20::52e; helo=mail-ed1-x52e.google.com; envelope-from=germano.massullo@gmail.com; receiver= 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) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:subject:message-id:date:user-agent:mime-version :content-transfer-encoding:content-language; bh=tws8QuMOoYgB4j0+MwZ0xkF47YfmwdKYRRsarVbDunM=; b=HZAJJdTSbsEeu1JSsqHEtgcjOrMd7A8H8QlD5mLwydrQ3B2VWiNKRM0j5GVG3OQGRE c3YNR4BIDA0JJFOJwhBYFAadKwsthhkuAJESe69X2BjU7wyI+37oxkDp6Vqa8Hy0eL9t iUuRDDxmiKIezCaQNP3ORqw5vnvlkrfPKxK2vGmDp/QNoDC3dLJM06qlpmg4Pvgg5ufw OzmQi9ECC9UPMAnowYUCzYXqpQCLBFzHPvlSBpmVdoQnej34zyCFNNj/GgQYexHWXfLN jXZe3z3AMnPEuGmP9x6H3FFqmBLau3vMzvgnYYg/rKK7jZtpvMTayPTX1Hl/cIp1RvEe 5FjQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:subject:message-id:date:user-agent :mime-version:content-transfer-encoding:content-language; bh=tws8QuMOoYgB4j0+MwZ0xkF47YfmwdKYRRsarVbDunM=; b=FLjYQfSd9GTSvtE8bWmyF8JaiXtvsNFoiEMYv1QiDRAAXx6Zk2ZvjJQP9YvOHxy+K1 Brbw8I8mPW/LE+KHchP2ZAuETlAb+yeOBlH+AhHtLPB9MVWjKg+w9KXctq2/KC+Na/9t tZ9unnLbvC/R3ryqTEf8WGqOFl+18yuKD59qlX81/EzVDEwzmRJ50E8f3HdQ9ShjTOK+ YGQ4if+pTMFJFyijihoUnjGc8T4IzSOb16t3KIZeKgF/agJzLesCcIMNVXyJesBNhu2O lwaZlbMvCjrTww9a5A4aICk4rJazZXdn6HQyHbhGVplPIfr8aij1n8OR/QdF9RH+dLDe iIQA== X-Gm-Message-State: AOAM5333iL1FAsqUHM8nABr5YGJ4wHkkqbadWo1MpfZYASmaxpxhTcMN ot/UlxHiq0qZ9N5kxL3MUjuf6c34nk0= X-Google-Smtp-Source: ABdhPJwVorsOB8MyuYzPCycjv+08BByjT3yNMKW8GXx5DEKw9loYRDoIJqDyprkke1taIZg8GvzhwQ== X-Received: by 2002:aa7:c0c2:: with SMTP id j2mr26229146edp.343.1608028958792; Tue, 15 Dec 2020 02:42:38 -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 To: dm-crypt@saout.de Message-ID: Date: Tue, 15 Dec 2020 11:42:37 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.5.0 MIME-Version: 1.0 Content-Language: en-US Subject: [dm-crypt] LUKS2 SSD swap and system freeze X-BeenThere: dm-crypt@saout.de X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: quoted-printable Errors-To: dm-crypt-bounces@saout.de Sender: "dm-crypt" Message-ID: <20201215104237.ZvAkK6iwyax75Sdf3zbI_EI3TfiJXXQp4lQow3gzHTI@z> 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 _______________________________________________ dm-crypt mailing list dm-crypt@saout.de https://www.saout.de/mailman/listinfo/dm-crypt