Bug 102339 - QXL driver hangs on virt guest login, kernel 4.12
Summary: QXL driver hangs on virt guest login, kernel 4.12
Status: NEW
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/other (show other bugs)
Version: unspecified
Hardware: Other All
: high normal
Assignee: Default DRI bug account
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-08-21 15:22 UTC by Chuck Ebbert
Modified: 2017-09-11 17:18 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Chuck Ebbert 2017-08-21 15:22:17 UTC
From https://bugzilla.redhat.com/show_bug.cgi?id=1481365

Description of problem:
Using KVM, QXL driver emits error message over and over, I never get to my home screen. It seems to be happening while attempting to switch resolution. Another user reports that everything works if he uses 1024x768.

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.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.