Switching back from Kernel 5.13.0 to 5.11.0 has fixed the issue. So this appears to be a kernel regression.
Switching back from Kernel 5.13.0 to 5.11.0 has fixed the issue. So this appears to be a kernel regression.