dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 110629] Intel i915 graphics driver issues with external monitor when laptop in docking station (opensuse bug 1132926)
Date: Mon, 06 May 2019 18:12:20 +0000	[thread overview]
Message-ID: <bug-110629-502@http.bugs.freedesktop.org/> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 2931 bytes --]

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

            Bug ID: 110629
           Summary: Intel i915 graphics driver issues with external
                    monitor when laptop in docking station (opensuse bug
                    1132926)
           Product: Mesa
           Version: unspecified
          Hardware: x86-64 (AMD64)
               URL: https://bugzilla.opensuse.org/show_bug.cgi?id=1132926
                OS: Linux (All)
            Status: NEW
          Keywords: regression
          Severity: normal
          Priority: medium
         Component: Drivers/DRI/i915
          Assignee: dri-devel@lists.freedesktop.org
          Reporter: otrebor@swissonline.ch
        QA Contact: dri-devel@lists.freedesktop.org
                CC: tiwai@suse.de

I have a HP EliteBook 840 G2 running openSUSE Leap 15.0 with all patches
applied.
The laptop runs fine when it is in normal portable mode (off dock), also with
an external monitor. When I dock it into its docking station at home, I
experience weird graphic device behaviour. It is a matter of luck if it is able
to initialize and configure the attached external monitor the way it is
expected. Sometimes it hangs in an endless config loop when trying to
initialize the monitor.
The external monitor is a SAMSUNG U28D590D connected via display port to port
#1 to the docking station.
However, if I undock the laptop and plug the very same display cable to the
onboard display port then the display and the laptop run as expected. It really
is an issue I can only experience when putting the device into the docking
station.
For comparison: I had the chance to try another device, a HP EliteBook 840 G3
with the very same docking station and monitor. It was running Windows 7 and I
did not see any strange behaviour. Additionally, I was earlier running openSUSE
42.3 on the very same device configuration and did not have any issues. The odd
behaviour only started after upgrading to Leap 15.0 and got worse with each
patch cycle, to reach total unusability as of today. Hence, thats why I am
writing this bug report.
One thing I occasionally see is this error message in the logs:
kernel: [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe C
FIFO underrun

I attaching output from dmesg, journalctl, and xrandr in different
configurations. Let me know if you need more.
Thanks for the support.

Please also refer to opensuse bug #1132926 here for more details:
https://bugzilla.opensuse.org/show_bug.cgi?id=1132926

Somehow might relate to this bug here:
https://bugs.freedesktop.org/show_bug.cgi?id=95298
However, my enviroenment refers to the Intel i915 graphics driver as I have no
Radeon hardware.

Please also see the opensuse bug first.
Let me know If you need more info.
Thanks for the support.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 4813 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

             reply	other threads:[~2019-05-06 18:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-06 18:12 bugzilla-daemon [this message]
2019-05-06 18:26 ` [Bug 110629] Intel i915 graphics driver issues with external monitor when laptop in docking station (opensuse bug 1132926) bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-110629-502@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).