|Summary:||i915 / drm crash when undocking from DP monitors|
|Product:||DRI||Reporter:||Vadim Lobanov <vadimplobanov>|
|Component:||DRM/Intel||Assignee:||Intel GFX Bugs mailing list <intel-gfx-bugs>|
|Status:||CLOSED FIXED||QA Contact:||Intel GFX Bugs mailing list <intel-gfx-bugs>|
|Priority:||highest||CC:||alejandro_aero, freedesktop, intel-gfx-bugs, nutello|
|i915 platform:||BDW||i915 features:||display/DP|
Description Vadim Lobanov 2016-10-12 02:45:43 UTC
Comment 1 Vadim Lobanov 2016-10-12 02:46:42 UTC
Created attachment 127229 [details] dmesg booting with drm.debug=14
Comment 2 Vadim Lobanov 2016-10-12 18:31:44 UTC
Note that bisect_pending is a bit of a misnomer since I have no idea how to make forward progress on the bisect with the intervening compile/disconnected-port issues that crop up, noted above.
Comment 3 Alejandro Lorenzo 2016-10-24 20:29:32 UTC
I Also seem to be affected by this. My system is a Dell precision 9550 connected to the Dell TB15 dock station and using DisplayPort Kernel 4.6 works well, 4.7 hangs when trying to switch a tty if at some past time the DisplayPort display has been disconnected (That's why it freezes the system when logging out or powering off; switches to tty) In my case, the device: 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 530 (rev 06) (prog-if 00 [VGA controller]) DeviceName: Onboard IGD Subsystem: Dell HD Graphics 530 Flags: bus master, fast devsel, latency 0, IRQ 141 Memory at db000000 (64-bit, non-prefetchable) [size=16M] Memory at 70000000 (64-bit, prefetchable) [size=256M] I/O ports at f000 [size=64] [virtual] Expansion ROM at 000c0000 [disabled] [size=128K] Capabilities: <access denied> Kernel driver in use: i915 Kernel modules: i915
Comment 4 Alejandro Lorenzo 2016-10-24 20:32:44 UTC
Correction, the docking station is the WD15
Comment 5 Alejandro Lorenzo 2016-10-24 21:17:03 UTC
Could this be related (or even a duplicate) of #98211 ?
Comment 6 Alejandro Lorenzo 2016-10-24 21:17:32 UTC
(In reply to Alejandro Lorenzo from comment #5) > Could this be related (or even a duplicate) of #98211 ? I meant 96938.
Comment 7 Jani Nikula 2016-10-25 09:29:22 UTC
(In reply to Alejandro Lorenzo from comment #6) > (In reply to Alejandro Lorenzo from comment #5) > > Could this be related (or even a duplicate) of #98211 ? > > I meant 96938. And if you say bug 96938 you'll get a nice link.
Comment 8 Alejandro Lorenzo 2016-11-29 08:55:33 UTC
Kernel 4.8.11 seems to improve the situation a lot. The computer no longer crashes. Still i think something is not quite right in the GPU after the disconnection because of some funny behavior i saw, but more testing is still required However, for those of you affected by this, i would give the 4.8.11 a spin :D
Comment 9 Vadim Lobanov 2016-11-29 23:55:09 UTC
Running on the most up-to-date Fedora 25 environment (kernel 4.8.8-300.fc25.x86_64) and I no longer see crashes described here. Not sure if it's fixed upstream in vanilla or if it's a local patch that Fedora is carrying.
Comment 10 Alejandro Lorenzo 2016-11-30 09:06:51 UTC
When i tested the 4.8.8 indeed the crashes stopped, but DP would not work fine. At least with my MST DP, the monitor would work ok as long as it was plugged it at boot time. However, if you unplug and plug the monitor the computer wouldn't crash, but i wouldn't have signal for the DP monitor either. In 4.8.11 this works
Comment 11 Andreas Kloeckner 2016-12-01 01:52:31 UTC
Bug 98919 is possibly related.
Comment 12 Jari Tahvanainen 2016-12-19 10:56:16 UTC
Highest+Blocker as being regression w/o workaround.
Comment 13 Jari Tahvanainen 2017-01-27 14:04:37 UTC
Vadim, Alejandro, I'm proposing this to be closed due to comment 9 and comment 10, where you said that crash does not happen anymore. Let's follow the "i wouldn't have signal for the DP monitor either." either in bug 98919 or if that does not apply then please create a new bug.
Comment 14 Vadim Lobanov 2017-01-27 17:27:56 UTC
Hi Jari, I would agree. This bug does not happen on my latest kernels any longer.
Comment 15 yann 2017-01-29 09:23:25 UTC
(In reply to Vadim Lobanov from comment #14) > Hi Jari, > > I would agree. This bug does not happen on my latest kernels any longer. Thanks for your feedback Vadim Lobanov. So closing this bug as fixed/
Comment 16 Alejandro Lorenzo 2017-01-30 09:54:16 UTC
Sorry for the late answer. I agree, this doesn't happen in new releases of the kernel.