Created attachment 1765289 [details] kernel log from boot to kernel-5.11.7-200.fc33.x86_64 1. Please describe the problem: Making "dnf upgrade" upgraded kernel from kernel-5.10.23-200.fc33.x86_64 to kernel-5.11.7-200.fc33.x86_64. Booting to the new kernel destroys the mouse cursor arrow shape. It seems, that the cursor is shown two times higher than normal, blank lines added between every graphic line. Booting back to the old kernel shows mouse cursor as normal. The same problem happens to other cursor shapes, I -type text cursor becomes two times higher as well. It is difficult to work with such cursors. I have two almost similar HP Laptops, same problem is in both machines. HP EliteBook 8570w, Intel Core i7, NVidia graphics: [root@P2012 ~]# lspci|grep VGA 01:00.0 VGA compatible controller: NVIDIA Corporation GK107GLM [Quadro K2000M] (rev a1) [root@P2012 ~]# I am using Nouveau driver at the moment. Not tried with Nvidia driver. 2. What is the Version-Release number of the kernel: kernel-5.11.7-200.fc33.x86_64 3. Did it work previously in Fedora? If so, what kernel version did the issue *first* appear? Old kernels are available for download at https://koji.fedoraproject.org/koji/packageinfo?packageID=8 : Works OK with kernel-5.10.23-200.fc33.x86_64 4. Can you reproduce this issue? If so, please provide the steps to reproduce the issue below: I do not know, if the problem is HW dependent, but just upgrade to kernel kernel-5.11.7-200.fc33.x86_64 shows the problem, booting to kernel-5.10.23-200.fc33.x86_64 is removing it. 5. Does this problem occur with the latest Rawhide kernel? To install the Rawhide kernel, run ``sudo dnf install fedora-repos-rawhide`` followed by ``sudo dnf update --enablerepo=rawhide kernel``: not checked 6. Are you running any modules that not shipped with directly Fedora's kernel?: no 7. Please attach the kernel logs. You can get the complete kernel log for a boot with ``journalctl --no-hostname -k > dmesg.txt``. If the issue occurred on a previous boot, use the journalctl ``-b`` flag.
This is a known issue with 5.11.y kernels and a fix is on its way: https://gitlab.com/cki-project/kernel-ark/-/merge_requests/979 The next (after 5.11.8) 5.11 kernel should have this fix, in the mean time it is easiest to just stick with a 5.10 kernel for now. *** This bug has been marked as a duplicate of bug 1941291 ***