Comment # 13 on bug 1165535 from Ulrich Windl

Created attachment 842196 [details]
Screenshot with top running when freeze occurred

(In reply to Miroslav Bene�� from comment #11)
> Frankly, I am not sure what to do here. It would be too easy to blame it on
> HW incompatibility, which Sebastian mentioned.

Counter-argument: On a completely different and new hardware (Machine with four
Xeon Gold (72 cores, 144 threads, > 700GB RAM) I had a kernel "freeze" while
performing some memory load test that just uses a few processes that shuffle
process-local memory around. The machine in question only had SSDs, configured
as two RAIDs via PERC: RAID1 for base OS, and RAID6 for additional data.
When performing the test without having any swap configured, the kernel started
to use the OOM killer to terminate a few processes.
After having configured 5GB swap @ prio=4 and >700GB swap @prio=2 the kernel
froze shortly after having used swap. The special thing about the new setup was
that the bug swap was configured via LVM and a thin volume.
The kernel in question was 5.3.18-24.15-default (actually from SLES15 SP2), and
there was plenty of swap space available when this had happened.
Interestingly the kernel still responded to PING, but that was all: No
VT-switching, not console getty, no ssh connection, no reaction on existing SSH
connections. However I had a "top" with sleep time 1s running at the moment
when the kernel froze.
I gave it more than 10 minutes to recover, but nothing had happened and there
was no message in /var/log/messages after the date top last had refreshed.