Re: [dm-devel] dm-crypt hard lockup

2020-06-30 Thread Artur Paszkiewicz 
On 6/28/20 6:50 PM, Bart Van Assche wrote:
> 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?

It could by another driver. I tried with a different filesystem (xfs),
without any I/O scheduler and even with the sources on a different drive
without dm-crypt, and the results were more or less the same - lockups
involving dm-crypt. Maybe I'm just abusing the system - I'm actually
running "make -j", so the number of tasks is unlimited. With a limited
number it does not hang. I know it's not a good idea to do this but it
used to work, and I think it shouldn't cause the kernel to die like
this.

Artur

--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel

Re: [dm-devel] dm-crypt hard lockup

2020-06-28 Thread Bart Van Assche 
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.

--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel

[dm-devel] dm-crypt hard lockup

2020-06-26 Thread Artur Paszkiewicz 
Hi,

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.

Regards,
Artur

[  248.471327] BUG: workqueue lockup - pool cpus=8 node=0 flags=0x0 nice=0 
stuck for 50s!
[  248.480317] Showing busy workqueues and worker pools:
[  248.486434] workqueue events: flags=0x0
[  248.491364]   pwq 16: cpus=8 node=0 flags=0x0 nice=0 active=1/256 refcnt=2
[  248.495357] pending: dbs_work_handler
[  248.504479]   pwq 0: cpus=0 node=0 flags=0x0 nice=0 active=1/256 refcnt=2
[  248.508474] pending: dbs_work_handler
[  248.517546] workqueue events_power_efficient: flags=0x80
[  248.523989]   pwq 0: cpus=0 node=0 flags=0x0 nice=0 active=1/256 refcnt=2
[  248.527980] pending: fb_flashcursor
[  248.536942] workqueue events_freezable_power_: flags=0x84
[  248.543494]   pwq 16: cpus=8 node=0 flags=0x0 nice=0 active=1/256 refcnt=2
[  248.547486] in-flight: 2357:disk_events_workfn
[  248.557530] workqueue mm_percpu_wq: flags=0x8
[  248.563075]   pwq 16: cpus=8 node=0 flags=0x0 nice=0 active=2/256 refcnt=4
[  248.567068] pending: vmstat_update, drain_local_pages_wq BAR(160)
[  248.578883] workqueue writeback: flags=0x4a
[  248.584305]   pwq 48: cpus=0-23 flags=0x5 nice=0 active=2/256 refcnt=6 MAYDAY
[  248.588300] in-flight: 188(RESCUER):wb_workfn wb_workfn
[  248.599547] workqueue kcryptd/254:0: flags=0x2a
[  248.605332]   pwq 48: cpus=0-23 flags=0x5 nice=0 active=24/24 refcnt=279754
[  248.609327] in-flight: 169:kcryptd_crypt [dm_crypt], 173:kcryptd_crypt 
[dm_crypt], 161:kcryptd_crypt [dm_crypt], 8:kcryptd_crypt [dm_crypt], 
165:kcryptd_crypt [dm_crypt], 155:kcryptd_crypt [dm_crypt], 164:kcryptd_crypt 
[dm_crypt], 174:kcryptd_crypt [dm_crypt], 163:kcryptd_crypt [dm_crypt], 
158:kcryptd_crypt [dm_crypt], 156:kcryptd_crypt [dm_crypt], 168:kcryptd_crypt 
[dm_crypt], 159:kcryptd_crypt [dm_crypt], 157:kcryptd_crypt [dm_crypt], 
166:kcryptd_crypt [dm_crypt], 1090(RESCUER):kcryptd_crypt [dm_crypt], 
160:kcryptd_crypt [dm_crypt], 154:kcryptd_crypt [dm_crypt], 162:kcryptd_crypt 
[dm_crypt], 171:kcryptd_crypt [dm_crypt], 167:kcryptd_crypt [dm_crypt], 
175:kcryptd_crypt [dm_crypt], 170:kcryptd_crypt [dm_crypt], 172:kcryptd_crypt 
[dm_crypt]
[  248.651333] delayed: kcryptd_crypt [dm_crypt], kcryptd_crypt [dm_crypt], 
kcryptd_crypt [dm_crypt], kcryptd_crypt [dm_crypt], kcryptd_crypt [dm_crypt], 
kcryptd_crypt [dm_crypt], kcryptd_crypt [dm_crypt], kcryptd_crypt [dm_crypt], 
kcryptd_crypt [dm_crypt], kcryptd_crypt [dm_crypt], kcryptd_crypt [dm_crypt], 
kcryptd_crypt [dm_crypt], kcryptd_crypt [dm_crypt], kcryptd_crypt [dm_crypt], 
kcryptd_crypt [dm_crypt], kcryptd_crypt [dm_crypt], kcryptd_crypt [dm_crypt], 
kcryptd_crypt [dm_crypt], kcryptd_crypt [dm_crypt], kcryptd_crypt [dm_crypt], 
kcryptd_crypt [dm_crypt], kcryptd_crypt [dm_crypt], kcryptd_crypt [dm_crypt], 
kcryptd_crypt [dm_crypt], kcryptd_crypt [dm_crypt], kcryptd_crypt [dm_crypt], 
kcryptd_crypt [dm_crypt], kcryptd_crypt [dm_crypt], kcryptd_crypt [dm_crypt], 
kcryptd_crypt [dm_crypt], kcryptd_crypt [dm_crypt], kcryptd_crypt [dm_crypt], 
kcryptd_crypt [dm_crypt], kcryptd_crypt [dm_crypt], kcryptd_crypt [dm_crypt], 
kcryptd_crypt [dm_crypt], kcryptd_crypt [dm_crypt]
[  248.651333] , kcryptd_crypt [dm_crypt], kcryptd_crypt [dm_crypt], 
kcryptd_crypt [dm_crypt], kcryptd_crypt [dm_crypt], kcryptd_crypt [dm_crypt], 
kcryptd_crypt [dm_crypt], kcryptd_crypt [dm_crypt], kcryptd_crypt [dm_crypt], 
kcryptd_crypt [dm_crypt], kcryptd_crypt [dm_crypt], kcryptd_crypt [dm_crypt], 
kcryptd_crypt [dm_crypt], kcryptd_crypt [dm_crypt], kcryptd_crypt [dm_crypt], 
kcryptd_crypt [dm_crypt], kcryptd_crypt [dm_crypt], kcryptd_crypt [dm_crypt], 
kcryptd_crypt [dm_crypt], kcryptd_crypt [dm_crypt], kcryptd_crypt [dm_crypt], 
kcryptd_crypt [dm_crypt], kcryptd_crypt [dm_crypt], kcryptd_crypt [dm_crypt], 
kcryptd_crypt [dm_crypt], kcryptd_crypt [dm_crypt], kcryptd_crypt [dm_crypt], 
kcryptd_crypt [dm_crypt], kcryptd_crypt [dm_crypt], kcryptd_crypt [dm_crypt], 
kcryptd_crypt [dm_crypt], kcryptd_crypt [dm_crypt], kcryptd_crypt [dm_crypt], 
kcryptd_crypt [dm_crypt], kcryptd_crypt [dm_crypt], kcryptd_crypt [dm_crypt], 
kcryptd_crypt [dm_crypt], kcryptd_crypt [dm_crypt], kcryptd_crypt [dm_c
 rypt]
[  248.779324] , kcryptd_crypt [dm_crypt], kcryptd_crypt [dm_crypt], 
kcryptd_crypt [dm_crypt], kcryptd_crypt [dm_crypt], kcryptd_crypt [dm_crypt], 
kcryptd_crypt [dm_crypt], kcryptd_crypt [dm_crypt], kcryptd_crypt [dm_crypt], 
kcryptd_crypt [dm_crypt], kcryptd_crypt [dm_crypt], kcryptd_crypt [dm_crypt], 
kcryptd_crypt [dm_crypt], kcryptd_crypt [dm_crypt], kcryptd_crypt [dm_crypt], 
kcryptd_crypt