Comment # 27 on bug 1159882 from Robert Delahunt

I had reinstalled OpenSUSE LEAP 15.2 using the DVD but with network enabled, so
what I should've gotten was a fresh installation of the most current stable
OpenSUSE LEAP 15.2.

VMSTAT information as requested:

http://www.puresimplicity.net/~delahunt/vmstat/swapon/

http://www.puresimplicity.net/~delahunt/vmstat/swapoff/

Basically, I had reinstalled OpenSUSE LEAP 15.2 with the LUKS-contained LVM of
/dev/system/home and /dev/system/swap but I had deleted the LV of swap and ran
the system without swap.  So the swapoff is a recording of vmstat while I was
doing

dd if=/dev/zero of=/dev/sdb bs=4K status=progress

and the swapon directory is after I went back into the partitioner, recreated
the swap LV, turned swap on, then ran the dd command above all over again.

The system immediately dug into swap to about the 40MB mark.  Running free -m
second by second, I could see available RAM plummet and swap climb.

I put other assorted diagnostic information in
http://www.puresimplicity.net/~delahunt/vmstat such as dmesg, cpuinfo, lsmod,
rpms, etc.

I noted that the partitioner installed a package called
nvme-cli-1.10-lp152.1.3.x86_64 when I clicked "accept" to add the swap LV.

I am very determined to help get this fixed, so please notify me immediately if
there's anything else I can help with.