FS#69406 - Screen tearing on kernel version 5.10.9

Attached to Project: Arch Linux
Opened by Conan (ofKnN) - Friday, 22 January 2021, 19:34 GMT
Last edited by Andreas Radke (AndyRTR) - Wednesday, 21 April 2021, 12:33 GMT
Task Type Bug Report
Category Kernel
Status Closed
Assigned To No-one
Architecture x86_64
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description: After upgrading to Linux Kernel 5.10.9, screen started to tear. Downgrading to 5.10.8 fixed the issue.


Additional info:
Machine: Asus X550JK
This task depends upon

Closed by  Andreas Radke (AndyRTR)
Wednesday, 21 April 2021, 12:33 GMT
Reason for closing:  Fixed
Comment by loqs (loqs) - Monday, 25 January 2021, 02:35 GMT
If the issue is still present under 5.10.10-arch1 please try linux-mainline 5.11-rc5.
If the issue is still present in mainline please bisect between 5.10.8 and 5.10.9 to find the causal commit from that the upstream commit it is a backport of and report the issue upstream.
Comment by Conan (ofKnN) - Monday, 25 January 2021, 21:58 GMT
Thank you for suggestions,

I have tried linux-mainline 5.11-rc5 and the issue is still present.
For the second suggestion, I actually didn't understand what to do, sorry.
Comment by loqs (loqs) - Monday, 25 January 2021, 23:17 GMT
Attached file has a step by step based upon https://wiki.archlinux.org/index.php/Bisecting_bugs_with_Git
   5.10.9.bisect.txt (1.1 KiB)
Comment by Conan (ofKnN) - Thursday, 18 February 2021, 14:30 GMT
Sorry for late update. I have tried bisecting for a few steps but since it took so much time and I couldn't spare much time for this, I couldn't continue. But I have seen that a same bug has been reported on RedHat Bugzilla. https://bugzilla.redhat.com/show_bug.cgi?id=1925346

I have used the wrong word for the issue. Sorry for that. It seems that they found a solution for the problem and expect it to be included in the official release.
Comment by Emil (xexaxo) - Thursday, 18 February 2021, 18:04 GMT
For reference here is the upstream backport list/thread:

https://lore.kernel.org/intel-gfx/fe6040b5-72a0-9882-439e-ea7fc0b3935d%40redhat.com/

Edit: s/@/%40/ to make the link legible.
Comment by loqs (loqs) - Thursday, 18 February 2021, 19:13 GMT
Looks to be the same issues as  FS#69557 

@xexaxo flyspray tries to convert everything with an @ in it into an email address as a work around you can replace it with %40
Comment by Emil (xexaxo) - Thursday, 18 February 2021, 19:42 GMT
Thanks for the @ trick.

They're not the same I'm afraid. Although the proposed "fixes" should address both.
Comment by loqs (loqs) - Thursday, 18 February 2021, 20:14 GMT
e627d5923cae is in drm-next so will be merged in the 5.12 merge window.
d30bbd62b1bf and 1914911f4aa0 look to have missed it and are in drm-intel-next-fixes should be merged with the first drm fixes pull.
Comment by Conan (ofKnN) - Thursday, 04 March 2021, 12:08 GMT
I have been using 5.10.19 kernel of Fedora for 2 days and it seems that the issue has gone.
https://bugzilla.redhat.com/show_bug.cgi?id=1925346

I don't know if Arch is able to put those patches into official kernel. If not, then I must await that the solution is applied by the upstream.

Edit: The patches are in the 5.10.20 and 5.11.3. I just saw them. I must now return to Arch Linux :)
Comment by Jason Antman (jantman) - Monday, 15 March 2021, 11:24 GMT
I was experiencing an issue that I believe is the same as this one. It was resolved for me since upgrading from linux-5.11.2-arch1-1 to linux 5.11.4-arch1-1 (yeah, I skipped 5.11.3).

Loading...