Created attachment 1734919 [details] log with nouveau driver timeout 1. Please describe the problem: This bug is being raised as a follow on from discussion in bug https://bugzilla.redhat.com/show_bug.cgi?id=1896904 Nouveau driver is getting a timeout, sometimes on initial boot, sometimes when removing/inserting an external monitor 2. What is the Version-Release number of the kernel: 5.9.10 and 5.10-rc5 tested 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 : Unknown - I don't think so 4. Can you reproduce this issue? If so, please provide the steps to reproduce the issue below: Yes - boot and if the problem hasn't occured remove/insert external monitor. Note - Karol's patch from the other bug is needed to prevent some crashes with mis-identification of the monitor Booting with nouveau.runpm=0 helps a little bit with this issue 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``: Yes 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.
Created attachment 1734920 [details] Log with Karols patched version of 5.10-rc5
*** Bug 1897251 has been marked as a duplicate of this bug. ***
Note - this issue seems specific to the RTX4000 (and was seen on the P17 with this graphics card too).
*** Bug 1899060 has been marked as a duplicate of this bug. ***
P17 with RTX4000 sent to Ben Skeggs for investigation Driver team in Japan have reproduced the issue on the RTX3000 and RTX2000 on the P17. We're still trying to confirm if the P15 is impacted with these cards as well but suspicions are that it is, just maybe slightly less susceptible as it's a timing issue. We are working with Nvidia on this, and Nvidia have contacted Ben directly as they may have some ideas to help on it. Mark
I believe this can all be closed as the issue with the firmware links was closed.
This message is a reminder that Fedora 33 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '33'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 33 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 33 changed to end-of-life (EOL) status on 2021-11-30. Fedora 33 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.