[Bug 104184] New: DP-1 display panel can't be used

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Sat Dec 9 22:17:00 UTC 2017 

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

            Bug ID: 104184
           Summary: DP-1 display panel can't be used
           Product: DRI
           Version: unspecified
          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: robsmithy at gmail.com
        QA Contact: intel-gfx-bugs at lists.freedesktop.org
                CC: intel-gfx-bugs at lists.freedesktop.org

Created attachment 136059
  --> https://bugs.freedesktop.org/attachment.cgi?id=136059&action=edit
journalctl output filtered for kernel or drm

Unable to enable the outer/top screen of Asus Taichi laptop (TAICHI21 variant,
Ivy bridge/HD4000 integrated graphics) with the i915 driver on Ubuntu 17.10.
This worked previously (Ubuntu 16.x) as long as the laptop was booted with the
lid closed (see background below). The Taichi has 2 screens, 1 on the outside
of the lid and one on the underside. To use the Taichi as a tablet, one closes
the lid and uses the outer (touch)screen. Opening the lid should switch off the
outer screen so that the Taichi acts as a normal laptop using the screen on the
underside.

With drm.debug verbose output turned on, the following warnings appear
(summary/headers here, the kernel/drm related journalctl output is attached):

Dec 09 20:44:45 ras-TAICHI kernel: WARN_ON(len <= 0)
Dec 09 20:44:45 ras-TAICHI kernel: WARNING: CPU: 3 PID: 211 at
/home/kernel/COD/linux/drivers/gpu/drm/i915/intel_dp.c:1539
intel_dp_max_link_rate+0x5e/0x80 [i915]
Dec 09 20:44:45 ras-TAICHI kernel: WARN_ON(len <= 0)
Dec 09 20:44:45 ras-TAICHI kernel: WARNING: CPU: 3 PID: 211 at
/home/kernel/COD/linux/drivers/gpu/drm/i915/intel_dp.c:1539
intel_dp_max_link_rate+0x5e/0x80 [i915]
Dec 09 20:44:45 ras-TAICHI kernel: WARN_ON(common_len <= 0)
Dec 09 20:44:45 ras-TAICHI kernel: WARNING: CPU: 3 PID: 211 at
/home/kernel/COD/linux/drivers/gpu/drm/i915/intel_dp.c:1638
intel_dp_compute_config+0xf1/0x990 [i915]
Dec 09 20:44:45 ras-TAICHI kernel: WARN_ON(common_len <= 0)
Dec 09 20:44:45 ras-TAICHI kernel: WARNING: CPU: 3 PID: 211 at
/home/kernel/COD/linux/drivers/gpu/drm/i915/intel_dp.c:1638
intel_dp_compute_config+0xf1/0x990 [i915]
Dec 09 20:44:45 ras-TAICHI kernel: WARN_ON(len <= 0)
... <truncated, these warnings repeat>

Accompanied by the following errors:

Dec 09 20:44:45 ras-TAICHI kernel: [drm:intel_crt_get_edid [i915]] CRT GMBUS
EDID read failed, retry using GPIO bit-banging
Dec 09 20:44:45 ras-TAICHI kernel: [drm:intel_atomic_check.part.134 [i915]]
Encoder config failure
Dec 09 20:44:45 ras-TAICHI kernel: [drm:intel_dump_pipe_config [i915]]
[CRTC:37:pipe A][failed]
Dec 09 20:44:45 ras-TAICHI kernel: [drm:intel_atomic_check.part.134 [i915]]
Encoder config failure
Dec 09 20:44:45 ras-TAICHI kernel: [drm:intel_dump_pipe_config [i915]]
[CRTC:37:pipe A][failed]
Dec 09 20:44:45 ras-TAICHI kernel: [drm:intel_crt_get_edid [i915]] CRT GMBUS
EDID read failed, retry using GPIO bit-banging
Dec 09 20:44:45 ras-TAICHI kernel: [drm:intel_atomic_check.part.134 [i915]]
Encoder config failure
Dec 09 20:44:45 ras-TAICHI kernel: [drm:intel_dump_pipe_config [i915]]
[CRTC:37:pipe A][failed]
Dec 09 20:44:45 ras-TAICHI kernel: [drm:intel_crt_get_edid [i915]] CRT GMBUS
EDID read failed, retry using GPIO bit-banging
Dec 09 20:44:45 ras-TAICHI kernel: [drm:intel_atomic_check.part.134 [i915]]
Encoder config failure
Dec 09 20:44:45 ras-TAICHI kernel: [drm:intel_dump_pipe_config [i915]]
[CRTC:37:pipe A][failed]
Dec 09 20:44:45 ras-TAICHI kernel: [drm:intel_atomic_check.part.134 [i915]]
Encoder config failure
Dec 09 20:44:45 ras-TAICHI kernel: [drm:intel_dump_pipe_config [i915]]
[CRTC:37:pipe A][failed]
Dec 09 20:44:45 ras-TAICHI kernel: [drm:intel_crt_get_edid [i915]] CRT GMBUS
EDID read failed, retry using GPIO bit-banging
Dec 09 20:44:45 ras-TAICHI kernel: [drm:intel_atomic_check.part.134 [i915]]
Encoder config failure
Dec 09 20:44:45 ras-TAICHI kernel: [drm:intel_dump_pipe_config [i915]]
[CRTC:37:pipe A][failed]
Dec 09 20:44:45 ras-TAICHI kernel: [drm:intel_atomic_check.part.134 [i915]]
Encoder config failure
Dec 09 20:44:45 ras-TAICHI kernel: [drm:intel_dump_pipe_config [i915]]
[CRTC:37:pipe A][failed]
Dec 09 20:44:46 ras-TAICHI kernel: [drm:intel_atomic_check.part.134 [i915]]
Encoder config failure
Dec 09 20:44:46 ras-TAICHI kernel: [drm:intel_dump_pipe_config [i915]]
[CRTC:37:pipe A][failed]
Dec 09 20:44:46 ras-TAICHI kernel: [drm:intel_atomic_check.part.134 [i915]]
Encoder config failure
Dec 09 20:44:46 ras-TAICHI kernel: [drm:intel_dump_pipe_config [i915]]
[CRTC:37:pipe A][failed]
Dec 09 20:44:46 ras-TAICHI kernel: [drm:intel_atomic_check.part.134 [i915]]
Encoder config failure
Dec 09 20:44:46 ras-TAICHI kernel: [drm:intel_dump_pipe_config [i915]]
[CRTC:37:pipe A][failed]
Dec 09 20:44:46 ras-TAICHI kernel: [drm:intel_atomic_check.part.134 [i915]]
Encoder config failure
Dec 09 20:44:46 ras-TAICHI kernel: [drm:intel_dump_pipe_config [i915]]
[CRTC:37:pipe A][failed]
Dec 09 20:45:00 ras-TAICHI kernel: [drm:intel_crt_get_edid [i915]] CRT GMBUS
EDID read failed, retry using GPIO bit-banging

The laptop begins booting with the Plymouth background/spinner showing. However
at the stage where GDM should be loaded, the login screen is not displayed:

* If the inner screen is not disabled by kernel parameter it is switched on and
the login screen is displayed there, the outer screen goes blank. 
* With kernel params 'video=eDP-1:1920x1080d video=DP-1:1920x1080 at 60D' the
inner screen stays off but the outer screen is now stuck on the Plymouth
background.

I have updated to the latest nightly intel_drm kernel (4.15.0-994-generic from
http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel-nightly/2017-12-08/).

-------------------------------------------------------------------------------

Background information. The Taichi has never been completely functional under
linux (see https://bugs.freedesktop.org/show_bug.cgi?id=73156). However it has
been possible on previous Ubuntu versions to enable the the outer screen using
the following workaround:

1. Boot with the lid closed - this causes the BIOS to set the outer screen on
and the underside screen off.
2. Pass the kernel parameter video=DP-1:1920x1080e
3. Wait for X to startup, then either screen can be used.

The outer screen would become disabled if the laptop were suspended (it seems
it can only be powered on by the BIOS). However a workaround for this was to
use pm-hibernate in place of suspend. When the laptop was resumed from
hibernate with the lid closed, the BIOS would re-enable the screen.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
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-gfx-bugs/attachments/20171209/65fc1437/attachment-0001.html>

More information about the intel-gfx-bugs mailing list