Bug 98569 - Screen comes up blank when booting Thinkpad X230 with VGA connected to docking station
Summary: Screen comes up blank when booting Thinkpad X230 with VGA connected to dockin...
Status: CLOSED FIXED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-11-03 12:21 UTC by Patrik Flykt
Modified: 2017-08-31 16:29 UTC (History)
2 users (show)

See Also:
i915 platform: IVB
i915 features: display/DP


Attachments
Kernel logs from boot to poweroff (227.80 KB, text/plain)
2016-11-03 12:21 UTC, Patrik Flykt
no flags Details

Description Patrik Flykt 2016-11-03 12:21:44 UTC
Created attachment 127718 [details]
Kernel logs from boot to poweroff

Hardware is a Thinkpad x230 connected to a ThinkPad UltraBase Series 3 docking station. Kernel uname is Linux 4.8.6 #2 SMP PREEMPT Thu Nov 3 11:32:32 EET 2016 x86_64 GNU/Linux and the system is running latest Debian testing.

Software versions used from Debian testing
libdrm-intel1:amd64         2.4.71-1
xserver-xorg-video-intel    2:2.99.917+git20160706-1
gdm3                        3.22.1-1

lspci -v reports
00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09) (prog-if 00 [VGA controller])
        Subsystem: Lenovo 3rd Gen Core processor Graphics Controller
        Flags: bus master, fast devsel, latency 0, IRQ 26
        Memory at f0000000 (64-bit, non-prefetchable) [size=4M]
        Memory at e0000000 (64-bit, prefetchable) [size=256M]
        I/O ports at 5000 [size=64]
        [virtual] Expansion ROM at 000c0000 [disabled] [size=128K]
        Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
        Capabilities: [d0] Power Management version 2
        Capabilities: [a4] PCI Advanced Features
        Kernel driver in use: i915

The CPUs are identified as 
processor       : 0
vendor_id       : GenuineIntel
cpu family      : 6
model           : 58
model name      : Intel(R) Core(TM) i7-3520M CPU @ 2.90GHz
stepping        : 9
microcode       : 0x1c
...

Booting with an external display connected to the DisplayPort on the docking station and laptop lid open/closed works perfectly well; gdm login screen is shown on the external display and everything works fine. Connecting another external display via VGA once the system has booted up works perfectly as well, both the DisplayPort and VGA screens are combined to form one big desktop.

What does not work is to boot with both the DisplayPort and VGA displays connected. The laptop boots up, launches gdm, but ends up with:
 - background pattern/color on the screen connected to DisplayPort
 - nothing on the screen connected to VGA where the monitor goes to power
   saving due to no input signal
 - laptop LCD shows the same background pattern/color
 - laptop LCD shows a mouse pointer
 - neither the touch pad or the external USB mouse works
 - neither the built in or the external keyboard works

In this situation the only option is to press the power key and reboot.
Comment 1 Dorota Czaplejewicz 2016-11-23 13:03:25 UTC
Hi,

for the sake of easier reproducing - the dock is not that common - could you provide a bit more info?

1. You mentioned the lid - does the position make a difference when you boot with 2 displays?
2. What happens when displays are connected to the ports on the laptop chassis (mini-DP and VGA)?

Nice to know:
1. Does this happen when you use a different display/cable on the VGA port? Logs welcome.
2. Does the computer respond to ping when this happens (if ping is allowed otherwise)?
Comment 2 Dorota Czaplejewicz 2016-11-25 18:49:42 UTC
I might have reproduced this bug.

The main difference between my attempt and the one of the reporter is that my system did not hang.

Multiple display handling definitely has problems - I didn't find a single useful configuration.

For the record, the test was done on ThinkPad x230 with no dock, display HDMI + VGA, on Fedora 24 (4.8.8-200.fc24.x86_64 #1 SMP Tue Nov 15 19:41:51 UTC 2016), with sddm as the display manager.

As soon as the DM started, the display went blank. I also haven't had any luck making the HDMI display go out of power saving when plugged after boot.

Patrik, does your system respond to Ctrl+Alt+Del, or perhaps Alt+Ctrl+PrintScreen+B?
Comment 3 Patrik Flykt 2016-11-28 12:23:21 UTC
I think you have reproduced the issue as it sounds very similar to a colleague of mine who is also using Fedora. So with your findings a docking station is not necessary to reproduce behavior.

When the issue happens, the keyboard is "dead", even an Alt+Ctrl+Del is not going through. But I can log in remotely, so the system is mostly working except for a dead keyboard and mouse and only background color + a mouse pointer visible on screen. Also noticed that the gnome-shell gdm attempts to start consumes 100% CPU.

To add more details, if I have the laptop lid open, bios and grub are visible on screen, but when gdm is started, keyboard, mouse and gdm stop working as described. If I start with the laptop lid closed, bios and grub are also visible on the VGA screen, which then goes to power save mode immediately after completing grub. As I have to type in the hard disk password, I do that completely in the blind, but in this setup I get a gdm screen up and running with working keyboarda and mouse! After selecting my user id and typing my password, the laptop decides to go to power saving sleep mode(!) immediately. Waking it up gets the system back to gdm login screen, and logging in gets the laptop into power saving again. This scenario repeats then infinitely.

So with grub/bios screen and keyboard work, but when the kernel and X takes over, it is not setup correctly at all.
Comment 4 Jari Tahvanainen 2016-12-08 16:21:20 UTC
Patrik and Dorota - sorry about the delay.
Could you try v4.9-rc3 (or newer) kernel or drm-intel-nightly branch of http://cgit.freedesktop.org/drm-intel
This was fixing things for SKL at least - see https://bugs.freedesktop.org/show_bug.cgi?id=98500
Comment 5 Patrik Flykt 2016-12-13 11:23:55 UTC
No change for my 3520M system on kernel 4.9.0 and the very latest in Debian testing as of today.
Comment 6 Ricardo 2017-02-23 22:03:06 UTC
submitted responded and issue still present in his system, removing needinfo status
Comment 7 soulsonceonfire 2017-06-04 07:24:17 UTC
Hi,

I'm running Debian Stretch with Gnome and Mate desktop (setup in different drives), with Mate it works fine, when the computer is docked and powered on it shows the login prompt on the laptop's screen and after login the desktop is shown on both external screens.

With Gnome I can't login, only a background color and a cursor is shown on the laptop screen.
If I add nomodeset to the boot parameters at least I see the login prompt but can't see desktop.
Enabling automatic login I'm able to get to desktop and everything works fine.

Could it be a gdm bug?
Comment 8 Elizabeth 2017-07-25 17:17:37 UTC
(In reply to Patrik Flykt from comment #5)
> No change for my 3520M system on kernel 4.9.0 and the very latest in Debian
> testing as of today.

Hello Patrik,
Still valid on 4.12 or higher? 
Thanks.

(In reply to soulsonceonfire from comment #7)
> 
Hello Souls,
Is this still reproducible in latest kernel https://www.kernel.org/? The HW is the same as Patrik? If this is different could you please open a new bug with HW, SW, reproducing steps and workarounds listed, also attached the dmesg with drm.bug=0xe on grub and clean kern.log?
Thank you.
Comment 9 Elizabeth 2017-08-31 16:29:28 UTC
Closing due lack of response. From 4.12 and up a lot of patches to improve docking station features have been merge. If problem arise on mainline https://www.kernel.org/ or latest drm-tip https://cgit.freedesktop.org/drm-tip please file a new bug with HW and SW information and required logs. Thank you.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.