Bug 98371 - Intel Corporation HD Graphics 5500 - Dell Latitude E5550 hangs after un- and redocking when switching to tty
Summary: Intel Corporation HD Graphics 5500 - Dell Latitude E5550 hangs after un- and ...
Status: CLOSED FIXED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: XOrg git
Hardware: Other All
: medium normal
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-10-21 10:37 UTC by Thomas Schneider
Modified: 2016-11-04 13:57 UTC (History)
2 users (show)

See Also:
i915 platform: BDW
i915 features: display/atomic

Attachments
first dmesg crash (85.57 KB, text/plain)
2016-10-21 10:38 UTC, Thomas Schneider 		no flags Details
dmesg output 4.7.5 restart lxdm (81.40 KB, text/plain)
2016-10-21 10:39 UTC, Thomas Schneider 		no flags Details
View All

Description Thomas Schneider 2016-10-21 10:37:29 UTC 
he machine I'm using is a "Dell Latitude E5550" and when you detach the notebook from the docking station while running X (in my test case with 2 monitors connected) and reattaching it afterwards you can't switch to the tty (ctrl+alt+fn) without freezing your pc. In this state it is still accessible via ssh, but the only (known) "solution" for getting a working X again is to reboot the system.
I'm running Arch Linux with 4.7.5, but is reproduce-able in older revisions as well (Linux version 4.7.5-1-ARCH (builduser@tobias) (gcc version 6.2.1 20160830 (GCC) ) #1 SMP PREEMPT Sat Sep 24 13:04:22 CEST 2016).
The journalctl -k output from the last crash on 4.7.5 only showed
> BUG: unable to handle kernel NULL pointer dereference at           (null)
> IP: [<ffffffff815d4ad4>] __ww_mutex_lock_slowpath+0xd4/0x210
at the end so I will include a full dmesg output of the last crash on the 4.7.4 kernel as well. 
The X server version is 1.18.4 (like above reproduce-able in other versions) and I'm using the modesetting driver instead of the intel xorg driver (but again reproduce-able with both drivers).
Here is the full lspci output

00:00.0 Host bridge: Intel Corporation Broadwell-U Host Bridge -OPI (rev 09)
00:02.0 VGA compatible controller: Intel Corporation HD Graphics 5500 (rev 09)
00:03.0 Audio device: Intel Corporation Broadwell-U Audio Controller (rev 09)
00:04.0 Signal processing controller: Intel Corporation Broadwell-U Processor Thermal Subsystem (rev 09)
00:14.0 USB controller: Intel Corporation Wildcat Point-LP USB xHCI Controller (rev 03)
00:16.0 Communication controller: Intel Corporation Wildcat Point-LP MEI Controller #1 (rev 03)
00:19.0 Ethernet controller: Intel Corporation Ethernet Connection (3) I218-LM (rev 03)
00:1b.0 Audio device: Intel Corporation Wildcat Point-LP High Definition Audio Controller (rev 03)
00:1c.0 PCI bridge: Intel Corporation Wildcat Point-LP PCI Express Root Port #1 (rev e3)
00:1c.3 PCI bridge: Intel Corporation Wildcat Point-LP PCI Express Root Port #4 (rev e3)
00:1c.4 PCI bridge: Intel Corporation Wildcat Point-LP PCI Express Root Port #5 (rev e3)
00:1d.0 USB controller: Intel Corporation Wildcat Point-LP USB EHCI Controller (rev 03)
00:1f.0 ISA bridge: Intel Corporation Wildcat Point-LP LPC Controller (rev 03)
00:1f.2 SATA controller: Intel Corporation Wildcat Point-LP SATA Controller [AHCI Mode] (rev 03)
00:1f.3 SMBus: Intel Corporation Wildcat Point-LP SMBus Controller (rev 03)
01:00.0 SD Host controller: O2 Micro, Inc. SD/MMC Card Reader Controller (rev 01)
02:00.0 Network controller: Intel Corporation Wireless 7265 (rev 59)
03:00.0 3D controller: NVIDIA Corporation GM108M [GeForce 840M] (rev a2)

And I will gladly add any wished additional output.
Comment 1 Thomas Schneider 2016-10-21 10:38:42 UTC 
Created attachment 127448 [details]
first dmesg crash

I couldn't attach the dmesg somehow so here it is
Comment 2 Thomas Schneider 2016-10-21 10:39:29 UTC 
Created attachment 127449 [details]
dmesg output 4.7.5 restart lxdm

The journalctl entry had no information since I didn't try to restart lxdm.
I reproduced the bug again and was confused because dmesg didn't have any oops or similar message so I tried to restart the DM which resulted in the (soon to be attached) dmesg output. Xorg.0.log doesn't have any error message as well.


After restarting lxdm at 329.
"USB disconnect" signals a detaching of the docking station "input: PixArt USB Optical Mouse" the attaching
Comment 3 Thomas Schneider 2016-11-04 10:34:29 UTC 
It seems like with the newest releases of X/mesa/linux this problem doesn't occur anymore.
Marking this as resolved
Comment 4 yann 2016-11-04 13:57:04 UTC 
(In reply to Thomas Schneider from comment #3)
> It seems like with the newest releases of X/mesa/linux this problem doesn't
> occur anymore.
> Marking this as resolved

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.