[Bug 97242] [SKL] Bad mouse cursor flickering since 4.8-rc1 with dual-screen [regression]

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Mon Aug 22 14:01:12 UTC 2016


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

Direx <direx at betriebsdirektor.de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |direx at betriebsdirektor.de

--- Comment #6 from Direx <direx at betriebsdirektor.de> ---
Created attachment 125942
  --> https://bugs.freedesktop.org/attachment.cgi?id=125942&action=edit
dmesg from drm-intel-next-queued (34730fed)

(In reply to Maarten Lankhorst from comment #5)
> Some watermark fixes have also been applied to drm-intel-next-queued,
> so can you retest on that branch?

The heavy cursor flickering is gone in drm-intel-next-queued, but the cursor
now behaves funny when moving between screens:

1. It usually moves directly to the opposite edge of the screen. It seems like
the acceleration cannot be calculated correctly. This might also be an X issue.

2. Whenever the mouse cursor changes screens, I get a short screen
distortion/flickering in the upper left-hand corner of the display which the
cursor has left.

But at least the machine is usable again. I hope these fixes will make it into
4.8, as otherwise this Kernel release will be a no-go for dual-screen users.

And finally, I am encountering a completely new issue (I'll open a separate bug
report for this):

The screens now flicker randomly (like once or twice every other minute). This
is unrelated to cursor movements, so it probably does not have anything to do
with this bug report.

I have attached a system log with drm.debug=0xe.

-- 
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/20160822/4307a379/attachment.html>


More information about the intel-gfx-bugs mailing list