Bug 955365

Summary:	External (DP) monitor turns off occasionally
Product:	[openSUSE] openSUSE Tumbleweed	Reporter:	Fabian Vogt <fvogt>
Component:	Kernel	Assignee:	E-mail List <kernel-maintainers>
Status:	RESOLVED INVALID	QA Contact:	E-mail List <qa-bugs>
Severity:	Normal
Priority:	P5 - None	CC:	fvogt, tiwai
Version:	Current
Target Milestone:	---
Hardware:	x86-64
OS:	Other
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	Xorg.0.log dmesg shortly after "flicker" dmesg shortly after "flicker" with updated i915 module

Description Fabian Vogt 2015-11-17 09:44:43 UTC

Created attachment 656178 [details]
Xorg.0.log

Moved from bug 954757.
Ocasionally, the monitor connected to DP turns black for a few moments (1-10 seconds). It is followed by an inrush of "The master control interrupt lied" messages.
Dmesg and Xorg.0.log shortly after the "flicker" occured are attached.

Hardware:
Lenovo ThinkPad X250 (Intel Core i7-5600U, Broadwell graphics).
First Monitor connected via the docking station's DP.
Second monitor connected via DVI is not affected by this issue.

Comment 1 Fabian Vogt 2015-11-17 09:45:14 UTC

Created attachment 656179 [details]
dmesg shortly after "flicker"

Comment 2 Takashi Iwai 2015-11-17 09:55:57 UTC

It's a regression in 4.3 kernel?  It wasn't clear in the previous report.

Also, which one is the affected DP?  The one with 1920x1080?

Comment 3 Fabian Vogt 2015-11-17 10:01:40 UTC

It's not a regression, AFAIK it's present since I originally installed TW on the laptop, on the 1st Sep.

The affected display is DP2-1, with 1920x1080.

BTW: "AccelMethod" is "uxa" to prevent plasma 5 crashes.

Comment 4 Lars Marowsky-Bree 2015-11-17 10:57:25 UTC

https://support.lenovo.com/de/de/documents/ht081248

Comment 5 Takashi Iwai 2015-11-17 11:00:54 UTC

(In reply to Lars Marowsky-Bree from comment #4)
> https://support.lenovo.com/de/de/documents/ht081248

That sounds promising, thanks.

If this firmware update doesn't help, try i915-quickfix-KMP in OBS home:tiwai:bnc955365 repo.  Install the package (*-default one), rebuild initrd if not done automatically, reboot and retest.

Comment 6 Fabian Vogt 2015-11-17 11:07:53 UTC

(In reply to Takashi Iwai from comment #5)
> (In reply to Lars Marowsky-Bree from comment #4)
> > https://support.lenovo.com/de/de/documents/ht081248
> 
> That sounds promising, thanks.
Looks promising indeed, but please tell me how I should update the firmware
using a windows .exe.
I don't have windows on this machine and it doesn't seem like it runs with Wine either (I didn't expect it to, but maybe I could've got a FW blob).

> If this firmware update doesn't help, try i915-quickfix-KMP in OBS home:tiwai:bnc955365 repo.  Install the package (*-default one), rebuild initrd if not done automatically, reboot and retest.

Should I still do that?

Comment 7 Takashi Iwai 2015-11-17 11:15:29 UTC

You can test KMP beforehand, too.  It's for another bug workaround, but the cause might be same as this, the unexpected hotplug storm.

The package seems being built now, so fetch it a bit later.

Comment 8 Fabian Vogt 2015-11-17 11:48:22 UTC

Ok, installed your quickfix, I'll report back if it occurs again or in about a week, if it doesn't.

Comment 9 Fabian Vogt 2015-11-23 11:01:09 UTC

Happened again, so the quickfix does not fix this issue.

Comment 10 Takashi Iwai 2015-11-23 11:05:51 UTC

Please give the dmesg with drm.debug=0x0e.  Also, make sure that i915 module comes really from KMP, see "modinfo i915 | grep filename"

Comment 11 Fabian Vogt 2015-11-23 12:36:56 UTC

Created attachment 656950 [details]
dmesg shortly after "flicker" with updated i915 module

filename:       /lib/modules/4.3.0-2-default/weak-updates/updates/drivers/gpu/drm/i915/i915.ko
dmesg: attached

Looks like the exact same thing again, it seems that a dock update is indeed the only possible solution...

Comment 12 Takashi Iwai 2015-11-26 12:05:52 UTC

Around which time stamp did the problem occur?  In the last half of the log, I don't see anything obvious there.  If so, it's possibly really a firmware issue.

Comment 13 Fabian Vogt 2015-11-26 12:16:07 UTC

I don't recall when about it happened, but AFAIK there's nothing special to see in the log indeed. So it's probably unfixable without a FW update.

Comment 14 Swamp Workflow Management 2015-12-08 20:14:35 UTC

openSUSE-SU-2015:2232-1: An update that solves 5 vulnerabilities and has 16 fixes is now available.

Category: security (moderate)
Bug References: 883192,944978,945825,948758,949936,951533,952384,952579,952976,953527,953559,953717,954404,954421,954647,954757,954876,955190,955363,955365,956856
CVE References: CVE-2015-5307,CVE-2015-6937,CVE-2015-7799,CVE-2015-7990,CVE-2015-8104
Sources used:
openSUSE Leap 42.1 (src):    kernel-debug-4.1.13-5.1, kernel-default-4.1.13-5.1, kernel-docs-4.1.13-5.4, kernel-ec2-4.1.13-5.1, kernel-obs-build-4.1.13-5.2, kernel-obs-qa-4.1.13-5.1, kernel-obs-qa-xen-4.1.13-5.1, kernel-pae-4.1.13-5.1, kernel-pv-4.1.13-5.1, kernel-source-4.1.13-5.1, kernel-syms-4.1.13-5.1, kernel-vanilla-4.1.13-5.1, kernel-xen-4.1.13-5.1

Comment 15 Fabian Vogt 2016-01-11 08:45:56 UTC

Closing as invalid as apparently a FW/HW problem.