From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bart Van Assche Subject: Re: dm-crypt hard lockup Date: Sun, 28 Jun 2020 09:50:39 -0700 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Content-Language: en-US List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: dm-devel-bounces@redhat.com Errors-To: dm-devel-bounces@redhat.com To: Artur Paszkiewicz , dm-devel@redhat.com List-Id: dm-devel.ids On 2020-06-26 02:07, Artur Paszkiewicz wrote: > I'm getting regular lockups which seem to be caused by dm-crypt. I > reproduced it on vanilla v5.8-rc2, but I started regularly seeing this > some time ago on openSUSE Tumbleweed kernels. It's easily reproducible > (every time, after about a minute) when I run "make -j" on the linux > kernel sources, sometimes it occurs also when doing other IO intensive > tasks on multiple CPUs. I'm using LVM and ext4 on dm-crypt devices, > Intel SSDSC2KW010X6 and SSDSC2BA200G3 SSDs. Since considerable time I'm doing kernel builds (make -j8) on an openSUSE Tumbleweed system on top of dm-crypt and an NVMe SSD but I have not yet encountered any kind of lockup. Maybe another driver, e.g. an I/O scheduler, is responsible for the lockups? Bart.