Hi,
I have a system that recently shows (same kernel upgrade) the same issue.
I've also found [1] which I think the kernel team might want to participate and track.
They seem to have identified a patch that potentially needs to be reverted - at least to confirm it is what now causes this.
There are also more people on there saying that it triggers with 5.15.0-41.
Hi,
I have a system that recently shows (same kernel upgrade) the same issue.
I've also found [1] which I think the kernel team might want to participate and track.
They seem to have identified a patch that potentially needs to be reverted - at least to confirm it is what now causes this.
There are also more people on there saying that it triggers with 5.15.0-41.
[1]: https:/ /bugzilla. kernel. org/show_ bug.cgi? id=213023