Bug 96714 - Random freezes with multiple displayport monitors connected to Thinkpad X260 with ultradock
Summary: Random freezes with multiple displayport monitors connected to Thinkpad X260 ...
Status: CLOSED FIXED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium critical
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-06-28 22:31 UTC by Kim Lidström
Modified: 2017-07-24 22:41 UTC (History)
3 users (show)

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


Attachments
Journal (426.20 KB, text/plain)
2016-06-28 22:31 UTC, Kim Lidström
no flags Details

Description Kim Lidström 2016-06-28 22:31:32 UTC
Created attachment 124769 [details]
Journal

As discussed on https://bugs.freedesktop.org/show_bug.cgi?id=96554 and https://bugs.freedesktop.org/show_bug.cgi?id=93580 I experience random freezes when I have connected two displayport monitors.

I can see no pattern in when and how it happens.

I am attaching the log from one session when it happened (booted with drm.debug=0xe).

As of this writing I am running kernel version 4.7.0-rc5 with patches from https://cgit.freedesktop.org/~ickle/linux-2.6/log/?h=for-bug93580.

The symptom is that the two external monitors just goes black and the display on the laptop sort of fades to noise that gets darker and darker until it's completely black.
The system is, from what I can see, totally unresponsive. I can't even SSH into it to try to figure out what's happening.
And as you can see in the log it simply just stops logging.

Maybe this is a hint?

Earlier today I also saw an interesting extra effect.
The system had frozen up like this while I wasn't nearby.
This has never happened before (It was always happened when I've been doing stuff) and because I wasn't nearby I didn't know how long it had been like that.
When I finally booted the computer up again some of the noise was still on the screen for an hour or so until it had slowly faded away.
It was even there in pre-bootloader.
Comment 1 Kim Lidström 2016-06-28 22:40:38 UTC
Could it be a pstates issue?

Either way I'm going to try booting with intel_pstate=no_hwp and see if that changes anything.
Comment 2 Kim Lidström 2016-07-01 10:53:56 UTC
This do indeed seem to be fixed in the nightlies.


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.