Bug 1399384 - Kernel oops when plugging in external monitor in display port
Summary: Kernel oops when plugging in external monitor in display port
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-intel
Version: 25
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Adam Jackson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-28 23:52 UTC by Brandon Bennett
Modified: 2017-12-12 10:11 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-12-12 10:11:22 UTC
Type: Bug


Attachments (Terms of Use)

Description Brandon Bennett 2016-11-28 23:52:27 UTC
Description of problem:
When plugging in an external monitor the computer freezes and it must hard cycled.  Happens immedately when external display is plugged in for both waland and xorg.


Version-Release number of selected component (if applicable):

Kernel:      4.8.8-300.fc25.x86_64
xorg-x11-drv-intel: 26.20160929.fc25


How reproducible:

Every time i plug in the external monitor 100%

Steps to Reproduce:

Plugging an external monitor in the mini-display port.  

Actual results:

Laptop freezes (sometimes with output on the laptop built-in display, sometimes not).  Nothing on the external display.

Expected results:

No freeze.  Use both screens for my desktop

Additional info:

sysinfo: https://paste.fedoraproject.org/492151/76218148/
Kernel oops: https://paste.fedoraproject.org/492154/80376540/

Comment 1 Brandon Bennett 2016-11-28 23:53:04 UTC
The system is a Lenovo X1 Yoga

Comment 2 Joe Doss 2016-11-29 18:10:28 UTC
We are seeing this happen with some Lenovo T460s at work as well using 

kernel-4.8.8-300.fc25.x86_64
xorg-x11-drv-intel-2.99.917-26.20160929.fc25.x86_64

that have the discrete NVIDIA GeForce 930M card. 

$ lspci |grep -E "VGA|3D"
00:02.0 VGA compatible controller: Intel Corporation HD Graphics 520 (rev 07)
06:00.0 3D controller: NVIDIA Corporation GM108M [GeForce 930M] (rev a2)

Same behavior that Brandon is seeing. We plug in an external monitor via mini-display port or if we dock it into a ThinkPad Ultra Dock Wayland totally locks up and the system becomes totally unresponsive.

Comment 3 Joe Doss 2016-11-29 18:51:30 UTC
I will note that I am not seeing this issue on my T450s. Here are some sysinfos for each system:

T450s: https://paste.fedoraproject.org/493300/04432861

T460s: http://paste.fedoraproject.org/493319/80444785

Comment 4 Brandon Bennett 2016-11-29 18:55:39 UTC
Testing out a newer kernel Linux strongbad 4.8.10-300.fc25.x86_64 #1 SMP Mon Nov 21 18:59:16 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux.  Issue still persists.

Given what Joe is seeing it seems to be the Skylake processors with the Intel 520 integrated graphics on it.

Comment 5 Joe Doss 2016-11-29 20:09:55 UTC
We did some more testing and it happens with HDMI too. We have had some cases where the system will lock up and as soon as you unplug the HDMI or Displayport cable it unfreezes.

Comment 6 Joe Doss 2016-11-30 16:16:46 UTC
We received a new T460s without the  discrete NVIDIA GeForce 930M card and with a fresh F25 install it does not have any issues lock up issues when plugging in an external monitor. The fpaste --sysinfo is below.

https://paste.fedoraproject.org/494188/05221321/

Comment 7 Joe Doss 2016-12-01 17:36:34 UTC
We figured out a temporary workaround yesterday. We set the same resolution on both the external monitor and the laptop monitor and the lockups have gone away.

Lockups happen

2560x1440 Laptop Monitor
3840x2160 Dell Ultra HD 4k Monitor P2715Q 27-Inch

Lockups stop 

1920x1080 Laptop Monitor
1920x1080 Dell Ultra HD 4k Monitor P2715Q 27-Inch

Comment 8 Brandon Bennett 2016-12-01 18:48:07 UTC
I plugged my laptop into my Dell ultrawide 34" at home and it seems to be working fine.  I haven't tried my 30" monitor at work again,

Resolutions are
  2048x1152 Laptop
  3440x1440 34 display.


Not sure what the trigger is.  There were some updates and I am testing the 3.8.10 kernel now: 

Linux strongbad 4.8.10-300.fc25.x86_64 #1 SMP Mon Nov 21 18:59:16 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

Comment 9 Fedora End Of Life 2017-11-16 19:29:18 UTC
This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '25'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 25 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 10 Fedora End Of Life 2017-12-12 10:11:22 UTC
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.