Summary: | QXL drm driver regression in 4.7 | ||
---|---|---|---|
Product: | DRI | Reporter: | Takashi Iwai <tiwai> |
Component: | DRM/other | Assignee: | Default DRI bug account <dri-devel> |
Status: | RESOLVED INVALID | QA Contact: | |
Severity: | normal | ||
Priority: | medium | ||
Version: | unspecified | ||
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
Takashi Iwai
2016-10-19 15:56:40 UTC
OK, I found out the culprit. It's the race of dirty update callback and the dirty clip update. The schedule_work() in drm_fb_helper_dirty() must be inside the spinlock. Otherwise the concurrent calls may conflict, one clears the clip while the another is called after that with the cleared clip area. I'll post the patch soon later. I can confirm this bug remains in the 4.8 kernel as well. KVM with Archlinux guest (virt-manager defaults, except for window scaling) results in the following message displayed between every command: [TTM] Byffer eviction failed qxl 0000:00:02:0: object_init failed for (402650032, 0x00000001) [drm:qxl_alloc_bo_reserved [qxl1] *ERROR* failed to allocate VRAM BO Arch kernel package: linux-4.8.2-1-x86_64.pkg.tar.xz Hi, Freedesktop's Bugzilla instance is EOLed and open bugs are about to be migrated to http://gitlab.freedesktop.org. To avoid migrating out of date bugs, I am now closing all the bugs that did not see any activity in the past year. If the issue is still happening, please create a new bug in the relevant project at https://gitlab.freedesktop.org/drm (use misc by default). Sorry about the noise! |
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.