Description of problem: Using KVM, QXL driver emits error message over and over, I never get to my home screen. Version-Release number of selected component (if applicable): 4.12.5 Steps to Reproduce: 1. Remove "rhgb" from kernel command line because of a possibly different QXL bug (don't have the link right now.) 2. Boot into graphical mode under KVM. Login screen appears, try to log in. 3. Desktop never appears. System log keeps getting these messages: Aug 13 14:03:40 localhost-live kernel: f 4026531862#140: failed to wait on release 22 after spincount 301 Aug 13 14:03:41 localhost-live kernel: f 4026531862#140: failed to wait on release 22 after spincount 301 Aug 13 14:03:41 localhost-live kernel: f 4026531862#140: failed to wait on release 22 after spincount 301 Aug 13 14:03:41 localhost-live kernel: f 4026531864#142: failed to wait on release 24 after spincount 301 Aug 13 14:03:42 localhost-live kernel: f 4026531864#142: failed to wait on release 24 after spincount 301 Aug 13 14:03:42 localhost-live kernel: f 4026531864#142: failed to wait on release 24 after spincount 301 Message is from drivers/gpu/drm/qxl/qxl_release.c::qxl_fence_wait() DMA fence operations are timing out. System can be shut down normally from the VM monitor, it's not frozen. The VM is only usable in text console mode.
The other QXL problem is bug 1465148, originally reported against rawhide and now happening on F26. Removing "rhgb" from the kernel command line prevents this one.
Unfortunately, removing "rhgb" from the kernel command line does not work for me.
We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. The kernel moves very fast so bugs may get fixed as part of a kernel update. Due to this, we are doing a mass bug update across all of the Fedora 26 kernel bugs. Fedora 26 has now been rebased to 4.15.4-200.fc26. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 27, and are still experiencing this issue, please change the version to Fedora 27. If you experience different issues, please open a new bug report for those.
This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. 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 '26'. 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 26 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 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26 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.
Seeing it in fc31 with 5.7.7-100.fc31.x86_64
(In reply to Laura Abbott from comment #3) > We apologize for the inconvenience. There is a large number of bugs to go > through and several of them have gone stale. The kernel moves very fast so > bugs may get fixed as part of a kernel update. Due to this, we are doing a > mass bug update across all of the Fedora 26 kernel bugs. > > Fedora 26 has now been rebased to 4.15.4-200.fc26. Please test this kernel > update (or newer) and let us know if you issue has been resolved or if it is > still present with the newer kernel. > > If you have moved on to Fedora 27, and are still experiencing this issue, > please change the version to Fedora 27. > > If you experience different issues, please open a new bug report for those. Laura, is this still on the radar?
This message is a reminder that Fedora 31 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24. 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 '31'. 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 31 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 31 changed to end-of-life (EOL) status on 2020-11-24. Fedora 31 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.