Martin, could you confirm that the issue is still present on SLE15-SP2 / Leap 15.2 kernels? Since TW shall be fixed after moving to 5.5, we'd need to track the bug specifically for SLE15-SP2. I wonder how is the best way to trigger the bug. I can provide a hackish patch, judging from the information in gitlab issue, a partial revert of f8c08d8faee5567803c8c533865296ca30286bbf.