Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1650224
Summary: | kernel 4.19.2 and nvidia issue | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Sammy <umar> |
Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 29 | CC: | airlied, bskeggs, cdf481f6, chrisa, ewk, fedora, hdegoede, ichavero, itamar, jarodwilson, jcline, jglisse, john.j5live, jonathan, josef, kernel-maint, linville, mchehab, mjg59, nige, steved, tovilyis |
Target Milestone: | --- | Keywords: | Reopened |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | kernel-4.19.5-200.fc28 kernel-4.19.5-300.fc29 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2018-12-01 02:05:43 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Sammy
2018-11-15 15:51:29 UTC
Hi Sammy, It usually takes NVidia a while after a new kernel is released to update their closed source drivers to work with it. Unfortunately, there's nothing we can do about that. You'll need to run 4.18 in the meantime or try to use the nouveau driver. Unfortunately nouveau also froze after an hour of using. No major activity other than browser use (firefox, google-chrome). I went back to 4.18.18 and nvidia drivers (410.78) for which everything works fine. *** Bug 1652510 has been marked as a duplicate of this bug. *** It seems there was a patch submitted for this issue on the LKML https://lkml.org/lkml/2018/11/19/93 Interesting. Even more interesting is that I am personally using and have access to nine other Linux distributions running kernel 4.19, all using NVIDIA drivers, and none of them exhibit this problem, only Fedora 29. Linux Mint 19 and Ubuntu 18.10 with mainline kernel 4.19.4-041904-generic and NVIDIA 415.13, openSUSE Leap 15.0 with kernel 4.19.3-2.1.gedac906 and NVIDIA 410.78, Sabayon Linux with kernel 4.19.2 and NVIDIA 410.57, Arch Linux and Antergos Linux with kernel 4.19.2-arch1-1-ARCH and NVIDIA 415.18, openSUSE Tumbleweed with kernel 4.19.2-1.3 and NVIDIA 410.78 and Solus 3 with kernel 4.19.1 and NVIDIA 410.73. Ironically, I've also tested Korora 28, an offshoot of Fedora, using kernel 4.19.3-200.fc28 and NVIDIA 410.78 from RPMFusion, and it worked perfectly. So it seems that only on Fedora 29 have I encountered this problem. Good that there is a patch, but for those of us who do not compile their own systems, is this problem going to be fixed for Fedora 29? Since kernel 4.18 was just EOLed, that leaves no upgrade path forward. Setting nvidia-drm.modeset=0 at the kernel line in grub.cfg results in working system and the bug message goes away as well. Naturally, this is not the optimal solution. Could we add this patch to the Fedora kernel? I would build the kernel rpm myself with the patch but for some reason when I try to build the kernel it tremendous amount of disk space and fill my root partition. Is there a way to build without this much disk space? Why was this closed as cantfix? Longer thread for the patch: https://patchwork.kernel.org/patch/10688303/ I believe it was closed because an earlier responder quickly blamed the NVIDIA drivers as being responsible. While it has often been true that new kernel releases occasionally broke NVIDIA drivers until such time as NVIDIA could produce an updated version, I do believe that the culprit this time is the Linux kernel itself, indicated by the fact that a kernel patch is being worked on. This wouldn't be done for a third-party driver issue, especially not for NVIDIA. There is much hostility for NVIDIA within the open-source community. I agree that this bug should be reopened. As long as it remains as it is, no other bug can be opened for the same problem as they are then flagged as duplicates. Hopefully the patch for this problem will be eventually added to the mainstream kernel code and show up in a future release. Please re-open. Nvidia driver works fine with kernel-4.18.18. And i don't see the issue in rawhide with kernel-4.20. rc1 So why this should be a problem with nvidia driver? And using nouveau driver as alternative is not a solution for newer cards. With my geforce-1030 card i have serious glitches with nouveau driver. As fedora maintainer i need a working fedora system. Btw. In kernel changelog for 4.19.2 are a few commits related to `drm` or `HDMI` outputs. I built a patched kernel 4.19.4 using the above patch and Fedora koji kernel source rpm. Everything is working well with nvidia-drm.modeset=1. (In reply to Sammy from comment #6) > Setting nvidia-drm.modeset=0 at the kernel line in grub.cfg results in > working system and the bug message goes away as well. Naturally, this is not > the optimal solution. Could we add this patch to the Fedora kernel? The patch is Cc'd for a future v4.19 stable update. I will add it to the next kernel build (v4.19.5). > > I would build the kernel rpm myself with the patch but for some reason when > I try to build the kernel it tremendous amount of disk space and fill my > root partition. Is there a way to build without this much disk space? > > Why was this closed as cantfix? It was closed because typically, nothing can be done from our side for NVidia driver problems. There seems to be a v2 of the patch that is checked to drm-misc-fixes git: https://cgit.freedesktop.org/drm-misc/commit/?h=drm-misc-fixes&id=afca3f41dc386e9020ab560937d52bb6f19bb6d4 *** Bug 1651452 has been marked as a duplicate of this bug. *** kernel-headers-4.19.5-300.fc29 kernel-4.19.5-300.fc29 kernel-tools-4.19.5-300.fc29 has been submitted as an update to Fedora 29. https://bodhi.fedoraproject.org/updates/FEDORA-2018-87ba0312c2 kernel-headers-4.19.5-200.fc28 kernel-tools-4.19.5-200.fc28 kernel-4.19.5-200.fc28 has been submitted as an update to Fedora 28. https://bodhi.fedoraproject.org/updates/FEDORA-2018-3857a8b41a kernel-4.19.5-200.fc28, kernel-headers-4.19.5-200.fc28, kernel-tools-4.19.5-200.fc28 has been pushed to the Fedora 28 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-3857a8b41a kernel-4.19.5-300.fc29, kernel-headers-4.19.5-300.fc29, kernel-tools-4.19.5-300.fc29 has been pushed to the Fedora 29 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-87ba0312c2 I'm happy to report that kernel 4.19.5-300.fc29 does indeed seem to fix the problem, at least on my platform. Hopefully the patch will be accepted into the mainstream kernel so that the next iteration does not need to be manually patched. Thank you for helping with this. kernel-4.19.5-200.fc28, kernel-headers-4.19.5-200.fc28, kernel-tools-4.19.5-200.fc28 has been pushed to the Fedora 28 stable repository. If problems still persist, please make note of it in this bug report. kernel-4.19.5-300.fc29, kernel-headers-4.19.5-300.fc29, kernel-tools-4.19.5-300.fc29 has been pushed to the Fedora 29 stable repository. If problems still persist, please make note of it in this bug report. |