Based on comment #78, I expect the main task at the top of this bug should close when kernel 5.19 is (soon) released to Ubuntu 22.10. Assuming there's no regression in 5.19.
I don't know if or when such a fix will ever reach Ubuntu 22.04 because we really thought it was the same fix at play in both 5.17.7 and 5.15.0-40. Turns out we need two different fixes, unless...
Can you double check that 5.15.0-40 or 5.15.0-41 still has the bug?
Based on comment #78, I expect the main task at the top of this bug should close when kernel 5.19 is (soon) released to Ubuntu 22.10. Assuming there's no regression in 5.19.
I don't know if or when such a fix will ever reach Ubuntu 22.04 because we really thought it was the same fix at play in both 5.17.7 and 5.15.0-40. Turns out we need two different fixes, unless...
Can you double check that 5.15.0-40 or 5.15.0-41 still has the bug?