This bug is back and I'm getting a bunch of emails related to it. Re-opening because the bug is back in upstream. It was fixed in kernel 5.2.5 for me but I'm getting reports of it being back in 5.3.0 and 5.5.13.
This bug is back and I'm getting a bunch of emails related to it. Re-opening because the bug is back in upstream. It was fixed in kernel 5.2.5 for me but I'm getting reports of it being back in 5.3.0 and 5.5.13.