[Bug 111517] New: No screen issues for extended period on xorg/lxde (HP systems)

[bugzilla-daemon at freedesktop.org]

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

            Bug ID: 111517
           Summary: No screen issues for extended period on xorg/lxde (HP
                    systems)
           Product: DRI
           Version: XOrg git
          Hardware: Other
                OS: All
            Status: NEW
          Severity: not set
          Priority: not set
         Component: DRM/Intel
          Assignee: intel-gfx-bugs at lists.freedesktop.org
          Reporter: freaky at bananateam.nl
        QA Contact: intel-gfx-bugs at lists.freedesktop.org
                CC: intel-gfx-bugs at lists.freedesktop.org

Created attachment 145206
  --> https://bugs.freedesktop.org/attachment.cgi?id=145206&action=edit
dmesg with drm.debug=0x1e -- XZ compressed

Hi there,

I'm not sure where to file this I'm afraid, I think it's supposed to go here.

We build a kiosk like distribution for taking exams with. It's based of Fedora
30 currently and runs Xorg with LXDE. We have no issues with stock Fedora 30
(which used Wayland/Gnome) on these machines. Besides our application (modified
browser), all packages are from Fedora. Some config files have been modified
and Xorg/LXDM isn't the default on Fedora, but they are in their repo's.

Our modified Fedora works fine nearly everywhere, but on some older HP machines
GUI will not appear for an extended amount of time (Xorg, console is fine).
After you see the LXDM service starting the console seems stuck there. After
waiting 10-20 minutes GUI will appear and all seems well.

On some of the systems the GUI instantly comes to live after moving the mouse a
few seconds after LXDM has started. Presume the mouse forces a redraw or
something which makes it come to live.

The systems all concern older HP systems, 8200, 8300, & 6560B so far with
various BIOS versions. Newer BIOS versions actually seem to have more issues.

On the 8200's the mouse will activate GUI, it does not on the 8300's from what
we got. We have a 8200 to test with, we don't have 8300's ourselves but I can
ask people to test those (more cumbersome tho' as there are several parties in
between).

In order to gather logging we have a script active, if users plug in a USB
stick which contains a file with a certain name it will output logs to the
stick. This process also runs xrandr, which also seems to 'unfreeze?' the GUI.

We have tested with a lot of kernel versions (all stock Fedora kernels,
although some come from older Fedora versions, we only replace the kernel (and
the modules in /lib/modules oc) and nothing else).

With 4.16.x they all seem to work without any issues.
With 4.17.x about half works without issues, most of the time.
4.18 and higher they all exhibit issues.

I'm not sure where to start as the systems work fine when using Fedora 30 live,
but then Wayland and gnome are used which probably address the GPU very
differently.

As reverting the kernel to 4.16 solves it, my first guess would be the kernel
driver. There's nothing in the logs that are indicative of the source, not to
me anyways.

Hope we can tackle this. I've attached logs from a system, I moved the mouse on
it to activate the GUI after waiting some time. Did pass along  drm.debug=0x1e
log_buf_len=1M as mentioned on
https://01.org/linuxgraphics/documentation/how-report-bugs

I can provide logging, test stuff, compile things, etc., but no clue where to
start here I'm afraid, C driver code is beyond my skills. Hope someone can help
us narrow this down.

Thanks in advance!

-- 
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/20190829/7b385529/attachment.html>