Comment 30 for bug 1966793

This seems to be a an issue on 5.19 aswell jonathan's workaround works but doing that after every kernel upgrade, including within 5.15 is cumbersome.

I have filed a separate bug report for 5.19 with ubuntu-bug linux, feedback if there's any additional information i can provide is appreciated

So far i've found this is a regression from 5.10