On 2019-10-28 11:44:57 [+0100], Joerg Vehlow wrote:I testes again with 5.0.19-rt10 and 5.0.19-rt11Â and I am pretty sure
I was unable to reproduce it with 5.2.21-rt13. Do you know if somethingthe softirq/BH handling has been rewritten in the v5.0-RT cycle,
changed in network scheduling code or could it be just less likely?
v5.0.19-rt11 to be exact. So if that the cause for it (which I hope)
then you should be able to trigger the problem before that release and
not later.