Bug 1941291 - Since kernel 5.11.7, cursor on Kepler GPU is broken
Summary: Since kernel 5.11.7, cursor on Kepler GPU is broken
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 33
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 1941149 1941168 1941263 1941300 1941348 1941637 1941849 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-03-21 11:55 UTC by Roy
Modified: 2021-03-29 01:12 UTC (History)
34 users (show)

Fixed In Version: kernel-5.11.9-300.fc34 kernel-5.11.9-200.fc33 kernel-5.11.10-100.fc32
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-03-26 00:16:47 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Roy 2021-03-21 11:55:01 UTC
1. Please describe the problem:
Since kernel 5.11.7, cursors on my Kepler GK107 GPU with nouveau look broken. It required the following fix by Lyude Paul (CC):
[PATCH v2] drm/nouveau/kms/nve4-nv108: Don't advertise 256x256 cursor support yet
Which has not yet been backported to kernel 5.11. System is hard to use without.

2. What is the Version-Release number of the kernel:
5.11.7

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 :
Yes, kernel 5.10 works. This is a regression introduced by cursor work that was merged in kernel 5.11.

4. Can you reproduce this issue? If so, please provide the steps to reproduce
   the issue below:
* Boot system with Kepler GPU to a kernel 5.11.7 with nouveau.

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``:
Unknown. I don't think this fix went in for 5.12 yet either.

6. Are you running any modules that not shipped with directly Fedora's kernel?:
Not relevant.

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.
Not relevant.

Comment 1 Roy 2021-03-21 23:02:04 UTC
Further to my report, I can confirm that the patch available on the nouveau mailinglist since the 5th of March titled "[PATCH v2] drm/nouveau/kms/nve4-nv108: Don't advertise 256x256 cursor support yet" indeed resolves this issue.

Comment 2 Hans de Goede 2021-03-22 09:51:39 UTC
*** Bug 1941348 has been marked as a duplicate of this bug. ***

Comment 3 Hans de Goede 2021-03-22 09:52:28 UTC
*** Bug 1941300 has been marked as a duplicate of this bug. ***

Comment 4 Hans de Goede 2021-03-22 09:53:12 UTC
*** Bug 1941149 has been marked as a duplicate of this bug. ***

Comment 5 Hans de Goede 2021-03-22 09:53:43 UTC
*** Bug 1941168 has been marked as a duplicate of this bug. ***

Comment 6 Roy 2021-03-22 10:47:31 UTC
FWIW: the mentioned patch is found on https://lists.freedesktop.org/archives/nouveau/2021-March/038113.html

Comment 7 Hans de Goede 2021-03-22 10:59:37 UTC
I have submitted a merge-request to get the fix for this added to the Fedora 5.11 kernels:
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/979

Comment 8 Hans de Goede 2021-03-22 14:37:45 UTC
*** Bug 1941637 has been marked as a duplicate of this bug. ***

Comment 9 Heiko 2021-03-22 20:05:04 UTC
Same issue for me with Kepler GK208B (Geforce GT730). Downgrading the kernel from 5.11.7 to 5.10.23 helped.

Comment 10 fusero 2021-03-22 21:03:05 UTC
same happening here

Comment 11 Hans de Goede 2021-03-22 22:08:39 UTC
*** Bug 1941849 has been marked as a duplicate of this bug. ***

Comment 12 Erkki Ruohtula 2021-03-23 07:20:55 UTC
What does your broken cursor look like? Asking because I wonder if this is the problem I started seeing after I ran update for Fedora 33 today:
The Cursor appears a to be vertically streched, and made of separate scanlines, like on a broken tube TV.
My hardware is a HP EliteBook 8570w with "NVIDIA Corporation GK107GLM [Quadro K1000M]" and using the nouveau driver.

Comment 13 Ian Laurie 2021-03-23 07:35:42 UTC
@Erkki there is a screen shot posted on duplicate bug #1941300 which looks how mine did.  There are other example screen shots on some of the other duplicate bugs you may like to check out.

Comment 14 Hans de Goede 2021-03-23 09:18:56 UTC
> My hardware is a HP EliteBook 8570w with "NVIDIA Corporation GK107GLM [Quadro K1000M]" and using the nouveau driver

The GK107 is affected by this bug. For now you can stick with a 5.10 kernel as a workaround. The next Fedora 5.11 kernel (the one after the 5.11.8 release) will contain the fix for this.

Comment 15 Hans de Goede 2021-03-23 19:11:44 UTC
*** Bug 1941263 has been marked as a duplicate of this bug. ***

Comment 16 eric.pouech 2021-03-24 08:03:07 UTC
(following up here from https://bugzilla.redhat.com/show_bug.cgi?id=1941263)
just tried proposed solution with kernel 5.11.8
it doesn't fix the issue (same broken behavior as 5.11.7)

Comment 17 Hans de Goede 2021-03-24 08:16:32 UTC
(In reply to eric.pouech from comment #16)
> (following up here from https://bugzilla.redhat.com/show_bug.cgi?id=1941263)
> just tried proposed solution with kernel 5.11.8
> it doesn't fix the issue (same broken behavior as 5.11.7)

That is because 5.11.8 does not contain the fix, in bug 1941263 I wrote:

"fixed in the *next* Fedora 5.11 kernel (the one which will be released after the current 5.11.8 one)."

Note the "next" bit in there as well as "released after the current 5.11.8 one".

So when 5.11.9 comes out in a couple of days, then the 5.11.9 Fedora build will include the fix.

Comment 18 eric.pouech 2021-03-24 08:48:57 UTC
sorry Hans, I read too fast (my bad)

bumping installonly_limit to 5 in /etc/dnf/dnf.conf just in case <g>

Comment 19 Fedora Update System 2021-03-24 14:59:20 UTC
FEDORA-2021-25441d8137 has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2021-25441d8137

Comment 20 Fedora Update System 2021-03-24 14:59:47 UTC
FEDORA-2021-68b0dd2373 has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2021-68b0dd2373

Comment 21 Fedora Update System 2021-03-24 15:00:14 UTC
FEDORA-2021-e636ce53df has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-e636ce53df

Comment 22 Fedora Update System 2021-03-25 01:23:57 UTC
FEDORA-2021-e636ce53df has been pushed to the Fedora 34 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-e636ce53df`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-e636ce53df

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 23 Fedora Update System 2021-03-25 01:32:00 UTC
FEDORA-2021-68b0dd2373 has been pushed to the Fedora 33 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-68b0dd2373`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-68b0dd2373

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 24 Fedora Update System 2021-03-25 02:07:32 UTC
FEDORA-2021-25441d8137 has been pushed to the Fedora 32 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-25441d8137`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-25441d8137

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 25 Ian Laurie 2021-03-25 04:23:19 UTC
Confirmed at my end that 5.11.9 fixes this problem on Fedora 33.

Comment 26 eric.pouech 2021-03-25 12:17:45 UTC
confirming as that 5.11.9 fixes the regression
rgds

Comment 27 A. Galama 2021-03-25 18:02:58 UTC
5.11.9 fixes the problem for me, too. Thanks.

Comment 28 Fedora Update System 2021-03-26 00:16:47 UTC
FEDORA-2021-e636ce53df has been pushed to the Fedora 34 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 29 John Griffiths 2021-03-26 03:39:51 UTC
The cursor is corrupted in Fedora 32 5.10.22-100.fc32.x86_64

Comment 30 John Griffiths 2021-03-26 03:45:24 UTC
Sorry. Just saw the fix has been pushed to Fedora 32.

Comment 31 Fedora Update System 2021-03-26 17:54:29 UTC
FEDORA-2021-68b0dd2373 has been pushed to the Fedora 33 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 32 Fedora Update System 2021-03-27 02:06:04 UTC
FEDORA-2021-9503fffad9 has been pushed to the Fedora 32 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-9503fffad9`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-9503fffad9

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 33 Fedora Update System 2021-03-29 01:12:04 UTC
FEDORA-2021-9503fffad9 has been pushed to the Fedora 32 stable repository.
If problem still persists, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.