From: Bart Van Assche <bvanassche@acm.org>
To: Artur Paszkiewicz <artur.paszkiewicz@intel.com>, dm-devel@redhat.com
Subject: Re: dm-crypt hard lockup
Date: Sun, 28 Jun 2020 09:50:39 -0700 [thread overview]
Message-ID: <f4e57ef4-e0df-d2e6-a00a-074a08f10dbb@acm.org> (raw)
In-Reply-To: <fb4877be-4d88-2816-9000-dcc540e8c093@intel.com>
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.
next prev parent reply other threads:[~2020-06-28 16:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-26 9:07 dm-crypt hard lockup Artur Paszkiewicz
2020-06-28 16:50 ` Bart Van Assche [this message]
2020-06-30 8:05 ` Artur Paszkiewicz
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=f4e57ef4-e0df-d2e6-a00a-074a08f10dbb@acm.org \
--to=bvanassche@acm.org \
--cc=artur.paszkiewicz@intel.com \
--cc=dm-devel@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.