[Bug 108085] Intel GeminiLake corruption at top of screen

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Thu Sep 27 09:07:02 UTC 2018


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

            Bug ID: 108085
           Summary: Intel GeminiLake corruption at top of screen
           Product: Mesa
           Version: 18.2
          Hardware: Other
                OS: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Drivers/DRI/i965
          Assignee: intel-3d-bugs at lists.freedesktop.org
          Reporter: dan at reactivated.net
        QA Contact: intel-3d-bugs at lists.freedesktop.org

On Intel GeminiLake platforms, a horizontal line of display corruption
frequently appears at the top of the screen.

This seems to happen on every single GeminiLake platform that we try. Affected
units include Asus E406MA and Acer Aspire XC-830.

We also have enough systems on hand to confidently say that it does not affect
ApolloLake, KabyLake, CoffeeLake nor WhiskeyLake.

It is reproducible:
 * On Fedora 28 with all updates (Linux 4.18, mesa-18.0) on both X and wayland.
 * On Fedora 29 beta (Linux 4.18, mesa 18.2) with all updates, under wayland
 * On Endless OS with Linux 4.19-rc5 and also on today's linux-next

Reproducer: at gdm, repeatedly click on the time/date to open and close the
calendar several times.

Alternative reproducer, a bit harder: open terminal, run dmesg, maximize the
terminal, then use two-finger scroll to quickly scroll up and down.

A video showing the problem under Endless. (note that Endless has modified gdm
to eliminate time/date at the top, so I instead reproduce by opening and
closing a menu repeatedly)
https://youtu.be/JUAr8sBwrmc

Another video showing that sometimes the corruption persists for a long time.
It's a bit hard to see in the video, but I can move the mouse over the
corrupted area and while the corruption persists underneath, the mouse cursor
itself is rendered just fine.
https://youtu.be/CWRgTo9KrwI

I can't reproduce if I run with LIBGL_ALWAYS_SOFTWARE=1
When the corruption persists on screen, if I take a screenshot with "DISPLAY=:0
import -window root out.png", the captured output is fine (it does not show the
corruption)

Please let me know how I can help debug further

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-3d-bugs/attachments/20180927/e153c97b/attachment-0001.html>


More information about the intel-3d-bugs mailing list