Bug 87327

Summary: [HSW] GPU Hang when reconnecting to an external monitor using a docked Lenovo T540p
Product: DRI Reporter: Theodore Ts'o <tytso>
Component: DRM/IntelAssignee: Intel GFX Bugs mailing list <intel-gfx-bugs>
Status: CLOSED FIXED QA Contact: Intel GFX Bugs mailing list <intel-gfx-bugs>
Severity: normal    
Priority: medium CC: intel-gfx-bugs
Version: unspecified   
Hardware: x86-64 (AMD64)   
OS: Linux (All)   
Whiteboard:
i915 platform: HSW i915 features: GPU hang
Attachments:
Description Flags
Dmesg after a resume
none
Contents of /sys/class/drm/card0/error
none
XOrg.0.log none

Description Theodore Ts'o 2014-12-15 13:02:39 UTC
Created attachment 110862 [details]
Dmesg after a resume

I've been having severe problems with docking with my Lenovo T540p using an external dock (which uses a MST hub in the dock).    The system will often hang, crash, or simply not recognize the external monitor until I restart the X server.   I've documented a number of these problems on the dri-devel mailing list for example, with the subject line "Re: WARNING:
 /usr/projects/linux/linux/drivers/gpu/drm/i915/intel_pm.c:6585
 intel_display_power_put+0x4b/0x116 [i915]()".   This is a new one.


This morning, I was docked and using a Dell 30" monitor.  I
reconfigured the X server to stop sending video to the external
monitor, suspended the laptop, and after it was suspended undocked it
and took it to work.  Then I docked it at work, where it was connected
to a powered off Dell 24" monitor, the system competely hung.  One of the things that I've learned will unwedge the system after it hangs after unsuspend is to eject the laptop from the dock, and wait.   Eventually the system did unwedge, and then I redocked it.  Afterwards, I found the following in dmesg and in /sys/class/drm/card0/error.  (See attached.)
Comment 1 Theodore Ts'o 2014-12-15 13:03:34 UTC
Created attachment 110863 [details]
Contents of /sys/class/drm/card0/error
Comment 2 Theodore Ts'o 2014-12-15 13:05:29 UTC
Created attachment 110864 [details]
XOrg.0.log
Comment 3 Jani Nikula 2015-10-23 10:28:05 UTC
We seem to have neglected this bug. Apologies. Does the problem persist with latest kernels?
Comment 4 yann 2016-09-30 15:49:23 UTC
(In reply to Jani Nikula from comment #3)
> We seem to have neglected this bug. Apologies. Does the problem persist with
> latest kernels?

Timeout. Assuming that it is fixed by now (there was ERROR: 0x00000104 (ie Invalid page directory entry error, Cacheline containing a PD was marked as invalid). If this is not the case, please re-test with latest kernel & Mesa to see if this issue is still occurring since there were improvements pushed in kernel and Mesa that will benefit to your system.

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.