Comment 2 for bug 1935880

I filed this issue on the kernel because it initially appeared to follow the host kernel version. While it's very reproducible w/ v5.4, I wasn't able to reproduce it with v5.8 or v5.7. However, I've now found that was a false negative - it is still reproducible with v5.13, so the kernel may not be the correct component.