| What | Removed | Added |
|---|---|---|
| CC | tiwai@suse.com |
The gitlab issue 224 looks somehow inconsistent: some people reported that 5.11 solved the problem while some people reported they still have the problem, and in your case, it appeared at first on 5.11.x. Hmm. Could you run with drm.debug=0x1e boot option and get the dmesg output? I don't think it points out the exact culprit, but this information is needed in anyway for further debugging.