Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem?
If it is a regression, we can perform a kernel bisect to narrow down which commit introduced it.
Also, it might be good to test the latest mainline kernel to see if this bug was already fixed upstream. If it was, can investigate to find the commit that fixes the bug.
Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem?
If it is a regression, we can perform a kernel bisect to narrow down which commit introduced it.
Also, it might be good to test the latest mainline kernel to see if this bug was already fixed upstream. If it was, can investigate to find the commit that fixes the bug.