[Bug 96593] New: [i915] Mouse movement jitter after 'drm/i915: Use atomic commits for legacy page_flips'

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Sun Jun 19 14:08:54 UTC 2016


https://bugs.freedesktop.org/show_bug.cgi?id=96593

            Bug ID: 96593
           Summary: [i915] Mouse movement jitter after 'drm/i915: Use
                    atomic commits for legacy page_flips'
           Product: DRI
           Version: DRI git
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: DRM/Intel
          Assignee: intel-gfx-bugs at lists.freedesktop.org
          Reporter: rafael.ristovski at gmail.com
        QA Contact: intel-gfx-bugs at lists.freedesktop.org
                CC: intel-gfx-bugs at lists.freedesktop.org

Kernel: next-20160617
OS: Gentoo Linux
xf86-video-intel: latest git
Xorg: latest git

HW:
  Dell Inspiron 3537
    i7-4500U (Haswell)
    Graphics 4400

Upon switching from next-20160615 to next-20160617,
I noticed that moving the cursor randomly causes its movement to jitter in a
lag-behind/catch-up fashion (most noticeable when dragging windows as this
applies the effect to the whole window, thus causing it not to move fluently).

Upon some bisecting I have found that this is caused by the following commit in
linux-next:

ee042aa40b66d18d465206845b0752c6a617ba3f - drm/i915: Use atomic commits for
legacy page_flips

Upon reverting this commit the issue is no longer present.

Another intriguing fact is that in some applications (ex. Games) which bind the
mouse input - the movement is fine.

// Dmesg/Xorg.0.log not attached yet as those do not seem to contain any
relevant data.

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are on the CC list for the bug.
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20160619/b8483ae0/attachment.html>


More information about the intel-gfx-bugs mailing list