dmesg shows "[drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)!"

Bug #1488719 reported by Alexander List
742
This bug affects 140 people
Affects Status Importance Assigned to Milestone
Linux
Fix Released
Medium
linux (Ubuntu)
Confirmed
High
Unassigned

Bug Description

On a recent intel NUC using i915 graphics, I get the following errors in dmesg:

[drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)!

There are two monitors connected to this box, one with mini-HDMI->HDMI, one with mini-DP->HDMI cable.

Maybe related:

https://bugs.freedesktop.org/show_bug.cgi?id=80896

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: linux-image-generic 3.19.0.26.25
ProcVersionSignature: Ubuntu 3.19.0-26.28-generic 3.19.8-ckt4
Uname: Linux 3.19.0-26-generic x86_64
ApportVersion: 2.17.2-0ubuntu1.3
Architecture: amd64
Date: Wed Aug 26 10:07:31 2015
InstallationDate: Installed on 2015-08-01 (24 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-26-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
SourcePackage: linux
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
In , Jinxianx-guo (jinxianx-guo) wrote :

Created attachment 102239
dmesg

==System Environment==
--------------------------
Regression: Yes.
Good commit on -next-queued: b6fdd0f2b990006daba19eec676b632faa523fc8

Non-working platforms: BDW

==kernel==
--------------------------
origin/drm-intel-nightly: eb638c7fabe97a9df752aeb2f59a9463ce4aed8e(fails)
    drm-intel-nightly: 2014y-07m-03d-14h-50m-16s integration manifest
origin/drm-intel-next-queued: 5e59f7175f96550ede91f58d267d2b551cb6fbba(fails)
    drm/i915: Try harder to get FBC
origin/drm-intel-fixes: 5549d25f642a7e6cfb8744d0031a9da404f696d6(works)
    drm/i915: Drop early VLV WA to fix Voltage not getting dropped to Vmin

==Bug detailed description==
dmesg error "<3>[ 1.954836] [drm:gen8_irq_handler] *ERROR* The master control interrupt lied (SDE)!" after boot.

Output:
[root@x-bdw01 ~]# dmesg -r | egrep "<[1-3]>" |grep drm
<3>[ 1.955683] [drm:gen8_irq_handler] *ERROR* The master control interrupt lied (SDE)!
<3>[ 1.955848] [drm:gen8_irq_handler] *ERROR* The master control interrupt lied (SDE)!
<3>[ 3.683649] [drm:gen8_irq_handler] *ERROR* The master control interrupt lied (SDE)!
<3>[ 3.686870] [drm:gen8_irq_handler] *ERROR* The master control interrupt lied (SDE)!

==Reproduce steps==
----------------------------
1. boot
2. dmesg -r | egrep "<[1-3]>" |grep drm

Revision history for this message
In , Paulo Zanoni (pzanoni) wrote :

Can you please bisect this? Which one is the bad commit?

Revision history for this message
In , Damien Lespiau (damien-lespiau) wrote :

No need to bisect, the error message was introduced by Oscar in

commit 38cc46d73ed99dd7002f1406002e52d7975d16cc
Author: Oscar Mateo <email address hidden>
Date: Mon Jun 16 16:10:59 2014 +0100

    drm/i915/bdw: Ack interrupts before handling them (GEN8)

And for those reason bit 23 of master ctl is set and the SDE IIR is 0.

Revision history for this message
In , Jinxianx-guo (jinxianx-guo) wrote :

Created attachment 102730
dmesg

(In reply to comment #2)
> No need to bisect, the error message was introduced by Oscar in
>
> commit 38cc46d73ed99dd7002f1406002e52d7975d16cc
> Author: Oscar Mateo <email address hidden>
> Date: Mon Jun 16 16:10:59 2014 +0100
>
> drm/i915/bdw: Ack interrupts before handling them (GEN8)
>
> And for those reason bit 23 of master ctl is set and the SDE IIR is 0.
Revert this commit on latest -next-queued,error "<3>[ 1.955683] [drm:gen8_irq_handler] *ERROR* The master control interrupt lied (SDE)!" unable to reproduce, but here has another error. Please check the output below. Need we report a new bug for this?

Output:
[root@x-bdw01 ~]# dmesg -r | egrep "<[1-3]>" |grep drm
<3>[ 2.753243] [drm:intel_dp_start_link_train] *ERROR* failed to enable link training
<3>[ 2.768133] [drm:intel_dp_start_link_train] *ERROR* failed to enable link training
<3>[ 2.780219] [drm:intel_dp_start_link_train] *ERROR* failed to enable link training
<3>[ 2.792092] [drm:intel_dp_start_link_train] *ERROR* failed to enable link training
<3>[ 2.804271] [drm:intel_dp_start_link_train] *ERROR* failed to enable link training
<3>[ 2.813306] [drm:intel_dp_start_link_train] *ERROR* failed to enable link training
<3>[ 2.831054] [drm:intel_dp_start_link_train] *ERROR* failed to update link training
<3>[ 2.832254] [drm:intel_dp_complete_link_train] *ERROR* failed to train DP, aborting

Revision history for this message
In , Paulo Zanoni (pzanoni) wrote :

Hi

It seems you're booting with eDP+HDMI. I can't reproduce this with eDP+HDMI or just eDP. Can you please confirm whether this only happens when you boot with DP (or DP+something) attached?

Thanks,
Paulo

Revision history for this message
In , Paulo Zanoni (pzanoni) wrote :

(In reply to comment #4)
> Hi
>
> It seems you're booting with eDP+HDMI. I can't reproduce this with eDP+HDMI

What I wanted to say was: "It seems you're booting with eDP+DP."

> or just eDP. Can you please confirm whether this only happens when you boot
> with DP (or DP+something) attached?
>
> Thanks,
> Paulo

Revision history for this message
In , Huax-lu (huax-lu) wrote :

Created attachment 104474
dmesg(14bf99)

It doesn't happen on latest -queued and -nightly kernel.I guess someone fixed it.

Revision history for this message
In , Paulo Zanoni (pzanoni) wrote :

(In reply to comment #6)
> Created attachment 104474 [details]
> dmesg(14bf99)
>
> It doesn't happen on latest -queued and -nightly kernel.I guess someone
> fixed it.

Closing bug then. If it still happens, please reopen.

Revision history for this message
In , Jinxianx-guo (jinxianx-guo) wrote :

Verified on latest -nightly(723dbbfb6ce02b5662c0c4cac9be3bcdfbb11d35)

[root@x-bdw01 ~]# dmesg -r | egrep "<[1-3]>" |grep drm
[root@x-bdw01 ~]#

Revision history for this message
In , Dima Ryazanov (dima-gmail) wrote :

Created attachment 115902
dmesg

I just saw this error while running the 4.0.3 kernel (4.0.3-300.fc22.x86_64).

Revision history for this message
In , Tobias Gerschner (tobias-gerschner) wrote :

Created attachment 116126
dmesg output, post event

Revision history for this message
In , Tobias Gerschner (tobias-gerschner) wrote :

Comment on attachment 116126
dmesg output, post event

This happens on a new NUC, with

CPU0: Intel(R) Core(TM) i7-5557U CPU @ 3.10GHz (fam: 06, model: 3d, stepping: 04)

I'm running a 4K display off the miniDP port.

It happens almost every single time I walk away from the computer within 10-15 minutes.

Revision history for this message
In , Jani-nikula (jani-nikula) wrote :

*** Bug 90058 has been marked as a duplicate of this bug. ***

Revision history for this message
In , M. B. (tomboy64) wrote :

Created attachment 117855
master control interrupt lied event

Not exactly sure what I'm looking at here. Using live infrastructure (libdrm, mesa, xorg-server, xf86-video-intel, all -9999) on gentoo.

Linux hatshepsut 4.1.6-gentoo #1 SMP Thu Aug 20 13:12:11 CEST 2015 x86_64 Intel(R) Core(TM) i5-5200U CPU @ 2.20GHz GenuineIntel GNU/Linux

If you need additional info, please let me know.

Revision history for this message
Alexander List (alexlist) wrote :
Revision history for this message
Alexander List (alexlist) wrote :
Revision history for this message
Alexander List (alexlist) wrote :
Revision history for this message
Brad Figg (brad-figg) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Changed in linux (Ubuntu):
importance: Undecided → High
Revision history for this message
Timo Aaltonen (tjaalton) wrote :
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Alexander List (alexlist) wrote :

Nope. Still get that message.

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Alexander List (alexlist) wrote :
Changed in linux:
importance: Unknown → High
status: Unknown → Confirmed
Revision history for this message
Peter Matulis (petermatulis) wrote :

Tried 4.3-rc1 [1] on an Asus Zenbook trying to escape bug 1492632 and I am now getting this message.

[1]: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.3-rc1-unstable/

Revision history for this message
In , Wendy-wang (wendy-wang) wrote :

Test Environment:

BDW-U
4.3.0-rc2_drm-intel-nightly_be4c33_20150923+

Reproduce steps:
1.boot up system and grep error message in dmesg
2. Will see below ERROR message.
[ 1.260036] [drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)!

Dmesg log attached.

Revision history for this message
In , Jani-nikula (jani-nikula) wrote :

(In reply to wendy.wang from comment #0)
> Dmesg log attached.

There's no attachment.

Revision history for this message
In , Yex-tian (yex-tian) wrote :

Created attachment 118408
dmesg info with drm.debug=0xe

Revision history for this message
In , Yex-tian (yex-tian) wrote :

This bug also exists on the latest drm-intel-fixes and drm-intel-next-queued branch.

Revision history for this message
In , Jani-nikula (jani-nikula) wrote :

Hmm, I'm wondering if we're handling this correctly, and if that could cause the issue:

"For each bit, the IIR can store a second pending interrupt if two or more of the same interrupt conditions occur before the first condition is cleared. Upon clearing the interrupt, the IIR bit will momentarily go low, then return high to indicate there is another interrupt pending. Only the rising edge of the PCH Display interrupt will cause the North Display IIR (DEIIR) PCH Display Interrupt event bit to be set, so all PCH Display Interrupts, including back to back interrupts, must be cleared here before a new PCH Display Interrupt can cause the DEIIR to be set."

Revision history for this message
In , Wendy-wang (wendy-wang) wrote :

Good commit:
commit b42fa27abff5970649ff07b0ce1691f6464097f3
Author: Daniel Vetter <email address hidden>
Date: Wed Jul 8 21:48:11 2015 +0200

    drm-intel-nightly: 2015y-07m-08d-19h-47m-26s UTC integration manifest

Bad commit:
commit 5b4a647fe39cf42753761b7d4ee20d695eec589c
Author: Daniel Vetter <email address hidden>
Date: Thu Jul 9 21:57:35 2015 +0200

    drm-intel-nightly: 2015y-07m-09d-19h-56m-44s UTC integration manifest

Revision history for this message
In , Mika-kuoppala (mika-kuoppala) wrote :

On my bdw after this commit the messages started to appear:

commit aaf5ec2e51ab1d9c5e962b4728a1107ed3ff7a3e
Author: Sonika Jindal <email address hidden>
Date: Wed Jul 8 17:07:47 2015 +0530

    drm/i915: Handle HPD when it has actually occurred

But when I just tried with latest nightly, I couldn't reproduce the any dmesg errors.

Revision history for this message
In , Niccolò Belli (darkbasic) wrote :

Created attachment 118478
dmesg (without drm.debug)

I was going to report the very same issue for my XPS 13 2015 9343 (Broadwell) when I saw this.
I attached dmesg (without drm.debug). Kernel is 4.3.0-rc3-mainline.

Revision history for this message
cboettig (cboettig) wrote :

Also getting this error sporadically, only with an external monitor, on the Dell XPS-13 developer edition (ships w/ ubuntu) on either 5.04 with 3.18 kernel or 5.10 beta with 4.2 kernel. Appears to be some kind of buffer overrun triggered by certain intensive tasks.

Revision history for this message
Stefan Langeland (morphuspam) wrote :

Getting this error as well on a Dell XPS-13 developer edition (ubuntu 14.04 LTE) with Kernel 4.3.0-rc2 from mainline[1].

Error occurs when I connect an external monitor on DisplayPort with 4k/60hz: Monitor flickers, turns black every five seconds and turns off completely after two or three minutes.

Error message (constantly with dmesg)

[14142.692434] [drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)!
...

After changing resolution back to 1920x1080 everything works fine again without any error messages.
Reproducable with stock kernel on ubuntu (3.13.0-37).

[1]: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.3-rc2-unstable/

Revision history for this message
In , Jani-nikula (jani-nikula) wrote :

(In reply to Mika Kuoppala from comment #6)
> But when I just tried with latest nightly, I couldn't reproduce the any
> dmesg errors.

I still see this on BDW.

Revision history for this message
In , Jani-nikula (jani-nikula) wrote :

Created attachment 118559
dmesg reproducing the problem on bdw

Curiously the errors are next to DP aux traffic.

Revision history for this message
In , Ville-syrjala-e (ville-syrjala-e) wrote :

Random idea:

--- a/drivers/gpu/drm/i915/i915_irq.c
+++ b/drivers/gpu/drm/i915/i915_irq.c
@@ -2345,6 +2345,7 @@ static irqreturn_t gen8_irq_handler(int irq, void *arg)
                u32 pch_iir = I915_READ(SDEIIR);
                if (pch_iir) {
                        I915_WRITE(SDEIIR, pch_iir);
+ POSTING_READ(SDEIIR);
                        ret = IRQ_HANDLED;

Revision history for this message
In , Jani-nikula (jani-nikula) wrote :

(In reply to Ville Syrjala from comment #10)
> + POSTING_READ(SDEIIR);

Does not help.

Revision history for this message
In , Jani-nikula (jani-nikula) wrote :

However this helps. We're missing something.

diff --git a/drivers/gpu/drm/i915/i915_irq.c b/drivers/gpu/drm/i915/i915_irq.c
index 76bd40e13391..0d524034abd7 100644
--- a/drivers/gpu/drm/i915/i915_irq.c
+++ b/drivers/gpu/drm/i915/i915_irq.c
@@ -1827,6 +1827,9 @@ static void ibx_hpd_irq_handler(struct drm_device *dev, u32 hotplug_trigger,
        dig_hotplug_reg = I915_READ(PCH_PORT_HOTPLUG);
        I915_WRITE(PCH_PORT_HOTPLUG, dig_hotplug_reg);

+ if (!hotplug_trigger)
+ return;
+
        intel_get_hpd_pins(&pin_mask, &long_mask, hotplug_trigger,
                           dig_hotplug_reg, hpd,
                           pch_port_hotplug_long_detect);
@@ -1934,8 +1937,7 @@ static void cpt_irq_handler(struct drm_device *dev, u32 pch_iir)
        int pipe;
        u32 hotplug_trigger = pch_iir & SDE_HOTPLUG_MASK_CPT;

- if (hotplug_trigger)
- ibx_hpd_irq_handler(dev, hotplug_trigger, hpd_cpt);
+ ibx_hpd_irq_handler(dev, hotplug_trigger, hpd_cpt);

        if (pch_iir & SDE_AUDIO_POWER_MASK_CPT) {
                int port = ffs((pch_iir & SDE_AUDIO_POWER_MASK_CPT) >>

Revision history for this message
In , Ville-syrjala-e (ville-syrjala-e) wrote :

(In reply to Jani Nikula from comment #12)
> However this helps. We're missing something.
>
> diff --git a/drivers/gpu/drm/i915/i915_irq.c
> b/drivers/gpu/drm/i915/i915_irq.c
> index 76bd40e13391..0d524034abd7 100644
> --- a/drivers/gpu/drm/i915/i915_irq.c
> +++ b/drivers/gpu/drm/i915/i915_irq.c
> @@ -1827,6 +1827,9 @@ static void ibx_hpd_irq_handler(struct drm_device
> *dev, u32 hotplug_trigger,
> dig_hotplug_reg = I915_READ(PCH_PORT_HOTPLUG);
> I915_WRITE(PCH_PORT_HOTPLUG, dig_hotplug_reg);

Is the read alone enough, or do you need the write too?

>
> + if (!hotplug_trigger)
> + return;
> +
> intel_get_hpd_pins(&pin_mask, &long_mask, hotplug_trigger,
> dig_hotplug_reg, hpd,
> pch_port_hotplug_long_detect);
> @@ -1934,8 +1937,7 @@ static void cpt_irq_handler(struct drm_device *dev,
> u32 pch_iir)
> int pipe;
> u32 hotplug_trigger = pch_iir & SDE_HOTPLUG_MASK_CPT;
>
> - if (hotplug_trigger)
> - ibx_hpd_irq_handler(dev, hotplug_trigger, hpd_cpt);
> + ibx_hpd_irq_handler(dev, hotplug_trigger, hpd_cpt);
>
> if (pch_iir & SDE_AUDIO_POWER_MASK_CPT) {
> int port = ffs((pch_iir & SDE_AUDIO_POWER_MASK_CPT) >>

Revision history for this message
In , Sonika-jindal (sonika-jindal) wrote :

(In reply to Jani Nikula from comment #12)
> However this helps. We're missing something.
>
> diff --git a/drivers/gpu/drm/i915/i915_irq.c
> b/drivers/gpu/drm/i915/i915_irq.c
> index 76bd40e13391..0d524034abd7 100644
> --- a/drivers/gpu/drm/i915/i915_irq.c
> +++ b/drivers/gpu/drm/i915/i915_irq.c
> @@ -1827,6 +1827,9 @@ static void ibx_hpd_irq_handler(struct drm_device
> *dev, u32 hotplug_trigger,
> dig_hotplug_reg = I915_READ(PCH_PORT_HOTPLUG);
> I915_WRITE(PCH_PORT_HOTPLUG, dig_hotplug_reg);
>
> + if (!hotplug_trigger)
> + return;
> +
Oh, but the whole point of the patch ( drm/i915: Handle HPD when it has actually occurred) was to disallaow writing to PCH_PORT_HOTPLUG register when the HPD did not occur.
And this shows stable HPD with SKL for me and was inline with other interrupts handling.

Do these "[drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)!" messages have any effect on HPD?

> intel_get_hpd_pins(&pin_mask, &long_mask, hotplug_trigger,
> dig_hotplug_reg, hpd,
> pch_port_hotplug_long_detect);
> @@ -1934,8 +1937,7 @@ static void cpt_irq_handler(struct drm_device *dev,
> u32 pch_iir)
> int pipe;
> u32 hotplug_trigger = pch_iir & SDE_HOTPLUG_MASK_CPT;
>
> - if (hotplug_trigger)
> - ibx_hpd_irq_handler(dev, hotplug_trigger, hpd_cpt);
> + ibx_hpd_irq_handler(dev, hotplug_trigger, hpd_cpt);
>
> if (pch_iir & SDE_AUDIO_POWER_MASK_CPT) {
> int port = ffs((pch_iir & SDE_AUDIO_POWER_MASK_CPT) >>

Revision history for this message
In , Jani-nikula (jani-nikula) wrote :

(In reply to Ville Syrjala from comment #13)
> (In reply to Jani Nikula from comment #12)
> > However this helps. We're missing something.
> >
> > diff --git a/drivers/gpu/drm/i915/i915_irq.c
> > b/drivers/gpu/drm/i915/i915_irq.c
> > index 76bd40e13391..0d524034abd7 100644
> > --- a/drivers/gpu/drm/i915/i915_irq.c
> > +++ b/drivers/gpu/drm/i915/i915_irq.c
> > @@ -1827,6 +1827,9 @@ static void ibx_hpd_irq_handler(struct drm_device
> > *dev, u32 hotplug_trigger,
> > dig_hotplug_reg = I915_READ(PCH_PORT_HOTPLUG);
> > I915_WRITE(PCH_PORT_HOTPLUG, dig_hotplug_reg);
>
> Is the read alone enough, or do you need the write too?

Moving the write below the !hotplug_trigger check brings the problem back, i.e. the write is also needed.

> > + if (!hotplug_trigger)
> > + return;
> > +
> > intel_get_hpd_pins(&pin_mask, &long_mask, hotplug_trigger,
> > dig_hotplug_reg, hpd,
> > pch_port_hotplug_long_detect);
> > @@ -1934,8 +1937,7 @@ static void cpt_irq_handler(struct drm_device *dev,
> > u32 pch_iir)
> > int pipe;
> > u32 hotplug_trigger = pch_iir & SDE_HOTPLUG_MASK_CPT;
> >
> > - if (hotplug_trigger)
> > - ibx_hpd_irq_handler(dev, hotplug_trigger, hpd_cpt);
> > + ibx_hpd_irq_handler(dev, hotplug_trigger, hpd_cpt);
> >
> > if (pch_iir & SDE_AUDIO_POWER_MASK_CPT) {
> > int port = ffs((pch_iir & SDE_AUDIO_POWER_MASK_CPT) >>

Revision history for this message
In , Ville-syrjala-e (ville-syrjala-e) wrote :

(In reply to Jani Nikula from comment #15)
> (In reply to Ville Syrjala from comment #13)
> > (In reply to Jani Nikula from comment #12)
> > > However this helps. We're missing something.
> > >
> > > diff --git a/drivers/gpu/drm/i915/i915_irq.c
> > > b/drivers/gpu/drm/i915/i915_irq.c
> > > index 76bd40e13391..0d524034abd7 100644
> > > --- a/drivers/gpu/drm/i915/i915_irq.c
> > > +++ b/drivers/gpu/drm/i915/i915_irq.c
> > > @@ -1827,6 +1827,9 @@ static void ibx_hpd_irq_handler(struct drm_device
> > > *dev, u32 hotplug_trigger,
> > > dig_hotplug_reg = I915_READ(PCH_PORT_HOTPLUG);
> > > I915_WRITE(PCH_PORT_HOTPLUG, dig_hotplug_reg);
> >
> > Is the read alone enough, or do you need the write too?
>
> Moving the write below the !hotplug_trigger check brings the problem back,
> i.e. the write is also needed.

Are the status bits actually showing long/short pulses when this happens?

Maybe we can just do something like this:

dig_hotplug_reg = I915_READ(PCH_PORT_HOTPLUG);
if (!hotplug_trigger)
    dig_hotplug_reg &= ~(*_HOTPLUG_STATUS_MASK);
I915_WRITE(PCH_PORT_HOTPLUG, dig_hotplug_reg
if (!hotplug_trigger)
    return;

Revision history for this message
Stephen Thirlwall (l-sdt) wrote :

I've just started getting this after updating to linux-image-3.19.0-30-generic from linux-image-3.19.0-28-generic.

NUC 5i3RYH connected via the mini-hdmi port to a 720p tv.

100% repeatable for me using Kodi 15.1. If I play a video I get audio, but the video is all black. If I activate the on-screen display items they render fine, but the video content itself is missing. Audio is fine.

Entering and exiting a video I get this each time:

[ 29.275053] [drm:gen8_irq_handler [i915_bpo]] *ERROR* The master control interrupt lied (SDE)!
[ 29.275763] [drm:gen8_irq_handler [i915_bpo]] *ERROR* The master control interrupt lied (SDE)!
[ 29.316539] sound hdaudioC0D0: HDMI: ELD buf size is 0, force 128
[ 29.316579] sound hdaudioC0D0: HDMI: invalid ELD data byte 0
[ 29.348980] [drm:gen8_irq_handler [i915_bpo]] *ERROR* The master control interrupt lied (SDE)!
[ 29.363813] [drm:gen8_irq_handler [i915_bpo]] *ERROR* The master control interrupt lied (SDE)!

Always the first six lines, sometimes more of the (SDE!) lines follow. Always one set when playback begins, and another when playback ends.

Further to this, if I disable VAAPI acceleration in Kodi, the video playback works again, but the kernel messages still appear.

Both the black-video and the messages are completely new in 3.19.0-30 - haven't seen either in earlier kernels.

Revision history for this message
Billy Olsen (billy-olsen) wrote :

Just saw this new after updating to the 3.19.0-30-generic kernel in vivid.

Revision history for this message
Alex (leo-tv) wrote :

Have the same problem on NUC5i5RYH connected to monitor via DisplayPort

> Ubuntu Server 14.04.3 LTS (GNU/Linux 3.19.0-30-generic x86_64)

Revision history for this message
In , Jani-nikula (jani-nikula) wrote :

Also http://<email address hidden>

Revision history for this message
In , Kimc (kimc) wrote :

Created attachment 118836
The master control interrupt lied

kernel output on a
Lenovo X1 Carbon (3rd gen) connected to a lenovo onelink pro dock

Revision history for this message
In , Kimc (kimc) wrote :

(In reply to Kim Carlsen from comment #14)
> Created attachment 118836 [details]
> The master control interrupt lied
>
> kernel output on a
> Lenovo X1 Carbon (3rd gen) connected to a lenovo onelink pro dock

Outputting 2560x1440@60 works fine, outputting 3840x2160@60 produces no picture on external monitor.

When removing the onelink prodock and connecting the dp cable directly to the laptop then all resolutions works (3840x2160@60).

Whenever running xrandr it adds 36 lines to kernel log of 'The master control interrupt lied'

Revision history for this message
In , Kimc (kimc) wrote :

When 4k resolution is working, these error message is still present in kernel.log. Maybe resolution issue is unrelated to IRQ issue

Revision history for this message
In , Jani-nikula (jani-nikula) wrote :

(In reply to Kim Carlsen from comment #16)
> When 4k resolution is working, these error message is still present in
> kernel.log. Maybe resolution issue is unrelated to IRQ issue

Please file that as a separate bug to not conflate this one, thanks.

Revision history for this message
In , Jani-nikula (jani-nikula) wrote :

*** Bug 92454 has been marked as a duplicate of this bug. ***

Revision history for this message
Brian Neltner (neltnerb) wrote :

I can verify that I also am getting this error now that I am running 3.19.0-30 on Intel NUC5i7RYH with Iris 6100 graphics.

I don't know what the error means, but definitely getting it. Upon update now my boot screen doesn't properly load and I have to decrypt the disk with nothing on the screen, clear regression from 3.19.0-28, but not sure if it's related.

Revision history for this message
stan383 (stan383) wrote :

I have Lenovo Thinkpad L450 with Intel HD Graphics 5500 and I can confirm the issue is present in the mainline kernel 4.3.0-040300rc. I did not have real noticeable issue - I just see the error messages in the log. It can be reproduced by executing xrandr while an external monitor is connected to the laptop. Any time I execute it, it will produce the error messages. Also connecting the external monitor to DP2 (analog VGA) will produce the error messages in dmesg.

When there is only laptop screen on and no external display connected, it looks executing xrandr will not produce the errors.

The problem is present in 3.19.0-30 but it is not present in 3.19.0-15.
I tried also 3.19.0-28, but using this kernel, my external monitor and even my external USB mouse and keyboard did not work.

Revision history for this message
rolfinator (seb2) wrote :

Affects me too on HP 820 G2 with Xubuntu 15.04 on Kernel 3.19.0-31-generic.

Revision history for this message
In , Daniel-ffwll (daniel-ffwll) wrote :

commit 97e5ed1111dcc5300a0f59a55248cd243937a8ab
Author: Daniel Vetter <email address hidden>
Date: Fri Oct 23 10:56:12 2015 +0200

    drm/i915: shut up gen8+ SDE irq dmesg noise

Revision history for this message
In , Daniel-ffwll (daniel-ffwll) wrote :

commit 97e5ed1111dcc5300a0f59a55248cd243937a8ab
Author: Daniel Vetter <email address hidden>
Date: Fri Oct 23 10:56:12 2015 +0200

    drm/i915: shut up gen8+ SDE irq dmesg noise

Changed in linux:
status: Confirmed → Fix Released
Revision history for this message
Morten Clausen (morten-c) wrote :

Maybe I don't get it, but: Is the fix only shutting up the kernel messages or is this fixing the cause?

I'm expiriencing this messages on a Lenovo T450 (20BX011GE) running 15.10 with 4.2.0-16-generic kernel. I see this messages wether external monitor is connected or not, although with much higher frequency with external monitor connected (dp via dock).

It seems like this messages is related to random GDM crashes. I tried to reproduce this behaviour, but I've got no clue when this is happening so far. I will try to investigate this further.

Revision history for this message
In , Jani-nikula (jani-nikula) wrote :

This also gets rid of the messages, and does *not* print the ### debug msg, i.e. the status bits are clear.

diff --git a/drivers/gpu/drm/i915/i915_irq.c b/drivers/gpu/drm/i915/i915_irq.c
index 6e0a5683bbdc..7716181473dc 100644
--- a/drivers/gpu/drm/i915/i915_irq.c
+++ b/drivers/gpu/drm/i915/i915_irq.c
@@ -1825,7 +1825,21 @@ static void ibx_hpd_irq_handler(struct drm_device *dev, u32 hotplug_trigger,
  u32 dig_hotplug_reg, pin_mask = 0, long_mask = 0;

  dig_hotplug_reg = I915_READ(PCH_PORT_HOTPLUG);
+ if (!hotplug_trigger) {
+ u32 mask = PORTA_HOTPLUG_STATUS_MASK |
+ PORTD_HOTPLUG_STATUS_MASK |
+ PORTC_HOTPLUG_STATUS_MASK |
+ PORTB_HOTPLUG_STATUS_MASK;
+
+ if (dig_hotplug_reg & mask)
+ DRM_DEBUG_KMS("### %08x\n", dig_hotplug_reg & mask);
+
+ dig_hotplug_reg &= ~mask;
+ }
+
  I915_WRITE(PCH_PORT_HOTPLUG, dig_hotplug_reg);
+ if (!hotplug_trigger)
+ return;

  intel_get_hpd_pins(&pin_mask, &long_mask, hotplug_trigger,
       dig_hotplug_reg, hpd,
@@ -1840,8 +1854,7 @@ static void ibx_irq_handler(struct drm_device *dev, u32 pch_iir)
  int pipe;
  u32 hotplug_trigger = pch_iir & SDE_HOTPLUG_MASK;

- if (hotplug_trigger)
- ibx_hpd_irq_handler(dev, hotplug_trigger, hpd_ibx);
+ ibx_hpd_irq_handler(dev, hotplug_trigger, hpd_ibx);

  if (pch_iir & SDE_AUDIO_POWER_MASK) {
   int port = ffs((pch_iir & SDE_AUDIO_POWER_MASK) >>
@@ -1934,8 +1947,7 @@ static void cpt_irq_handler(struct drm_device *dev, u32 pch_iir)
  int pipe;
  u32 hotplug_trigger = pch_iir & SDE_HOTPLUG_MASK_CPT;

- if (hotplug_trigger)
- ibx_hpd_irq_handler(dev, hotplug_trigger, hpd_cpt);
+ ibx_hpd_irq_handler(dev, hotplug_trigger, hpd_cpt);

  if (pch_iir & SDE_AUDIO_POWER_MASK_CPT) {
   int port = ffs((pch_iir & SDE_AUDIO_POWER_MASK_CPT) >>

Revision history for this message
Puggan (from-ubuntu-b) wrote :

Got this error in my dmesg, and gets daily KDM crashes.

Have an Asus X555L with 2 external monitors connected,
each morning when i get back to the computer, the laptop screen dosn't start,
and I have no working window managment => I can use the active window, but can't change active window.

Also, if i activate the wireless-card, I can see the si (software interupt) in top raise to 100%, and then I lose all controll.
And all I found so far is this error message 1836 times in the dmesg-log

Revision history for this message
Jeroko (jeroko) wrote :
Download full text (3.1 KiB)

I get this error on my new Toshiba P50t-C-104, with kernel 4.3. No monitors attached, just the default laptop screen. I get a black screen after this message on boot. The only way to boot is to use the 'nomodeset' kernel parameter, but that dissables the intel graphics card.

[ 6.254918] [drm:i915_gem_open]
[ 6.254990] [drm:drm_mode_getresources] CRTC[3] CONNECTORS[2] ENCODERS[2]
[ 6.254993] [drm:drm_mode_getresources] [CRTC:21]
[ 6.254995] [drm:drm_mode_getresources] [CRTC:25]
[ 6.254996] [drm:drm_mode_getresources] [CRTC:29]
[ 6.254997] [drm:drm_mode_getresources] [ENCODER:31:TMDS-31]
[ 6.254999] [drm:drm_mode_getresources] [ENCODER:39:TMDS-39]
[ 6.255000] [drm:drm_mode_getresources] [CONNECTOR:32:eDP-1]
[ 6.255002] [drm:drm_mode_getresources] [CONNECTOR:40:HDMI-A-1]
[ 6.255003] [drm:drm_mode_getresources] CRTC[3] CONNECTORS[2] ENCODERS[2]
[ 6.255008] [drm:drm_mode_getconnector] [CONNECTOR:32:?]
[ 6.255010] [drm:drm_helper_probe_single_connector_modes_merge_bits] [CONNECTOR:32:eDP-1]
[ 6.255011] [drm:intel_dp_detect] [CONNECTOR:32:eDP-1]
[ 6.255018] [drm:edp_panel_vdd_on] Turning eDP port A VDD on
[ 6.255024] [drm:edp_panel_vdd_on] PP_STATUS: 0x80000008 PP_CONTROL: 0xabcd000f
[ 6.255476] [drm:drm_edid_to_eld] ELD: no CEA Extension found
[ 6.255480] [drm:drm_helper_probe_single_connector_modes_merge_bits] [CONNECTOR:32:eDP-1] probed modes :
[ 6.255483] [drm:drm_mode_debug_printmodeline] Modeline 33:"3840x2160" 60 533250 3840 3888 3920 4000 2160 2163 2168 2222 0x48 0xa
[ 6.255487] [drm:drm_mode_getconnector] [CONNECTOR:32:?]
[ 6.255497] [drm:drm_mode_getconnector] [CONNECTOR:40:?]
[ 6.255498] [drm:drm_helper_probe_single_connector_modes_merge_bits] [CONNECTOR:40:HDMI-A-1]
[ 6.255500] [drm:intel_hdmi_detect] [CONNECTOR:40:HDMI-A-1]
[ 6.255657] [drm:gmbus_xfer] GMBUS [i915 gmbus dpb] NAK for addr: 0050 w(1)
[ 6.255658] [drm:gmbus_xfer] GMBUS [i915 gmbus dpb] NAK on first message, retry
[ 6.255815] [drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)!
[ 6.255817] [drm:gmbus_xfer] GMBUS [i915 gmbus dpb] NAK for addr: 0050 w(1)
[ 6.255819] [drm:drm_do_probe_ddc_edid] drm: skipping non-existent adapter i915 gmbus dpb
[ 6.255821] [drm:drm_helper_probe_single_connector_modes_merge_bits] [CONNECTOR:40:HDMI-A-1] disconnected
[ 6.255824] [drm:drm_mode_getconnector] [CONNECTOR:40:?]
[ 6.255826] [drm:drm_helper_probe_single_connector_modes_merge_bits] [CONNECTOR:40:HDMI-A-1]
[ 6.255828] [drm:intel_hdmi_detect] [CONNECTOR:40:HDMI-A-1]
[ 6.255986] [drm:gmbus_xfer] GMBUS [i915 gmbus dpb] NAK for addr: 0050 w(1)
[ 6.255988] [drm:gmbus_xfer] GMBUS [i915 gmbus dpb] NAK on first message, retry
[ 6.256147] [drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)!
[ 6.256149] [drm:gmbus_xfer] GMBUS [i915 gmbus dpb] NAK for addr: 0050 w(1)
[ 6.256150] [drm:drm_do_probe_ddc_edid] drm: skipping non-existent adapter i915 gmbus dpb
[ 6.256152] [drm:drm_helper_probe_single_connector_modes_merge_bits] [CONNECTOR:40:HDMI-A-1] disconnected
[ 6.302099] init: alsa-restore main process (976) terminated with status 99
...

Read more...

Revision history for this message
Tim Holy (holy-wustl) wrote :

I'm still getting this on 4.2.0-17-generic with a Lenovo W550s. Moreover, [if you read the patch](http://www.spinics.net/lists/intel-gfx/msg78796.html) you'll see it just affects whether it prints the warning, and doesn't correct the underlying problem. Related or not, I'm also seeing the blank-screen symptoms [reported here](https://github.com/NixOS/nixpkgs/issues/9755).

Revision history for this message
fcourchesne@gmail.com (fcourchesne) wrote :

I am getting this as well WITHOUT any external monitors plugged.
4.2.0-17-generic

I was getting similar behavior on arch Linux with 4.2.x

I also get this error prior:
[drm:intel_pipe_config_compare [i915]] *ERROR* mismatch in base.adjusted_mode.crtc_clock (expected 138780, found 92519)

Revision history for this message
Daniel Herrmann (daniel-herrmann1) wrote :

Also getting this error with my Dell Latitude E7450 with two external displays connected using DP->mDP cables (E-Dock Port Replicator), together with screen freeze. DM restarts automatically after some time, no need to reboot. However all applications are killed then.

Revision history for this message
Tomer Cohen (tomerc) wrote :

I got this issue while connecting Lenovo G70 to an external monitor using HDMI cable. I was able to workaround this by replacing Nvidia proprietary driver with Nouveau.

Revision history for this message
darkhawk (info-sarazin) wrote :

I'm running an T450s with 2 external DELL monitors, one 24" and a DELL 27", both are connected by Displayport.

After locking the desktop by windows+L key and returning after some time (minutes) the 27" DELL isn't working anymore and i have to reconfigure the whole display settings, the dmesg output bring up the following lines:

[19707.593875] [drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)!
[19707.594307] [drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)!
[19707.595068] [drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)!

Revision history for this message
Ronan Mooney (roomey) wrote :

Running dell latitude E5450 with nVidea card and seeing this - both the error and sometimes when unlocking screen the monitor keeps flashing on and off every 5 seconds until you change the resolution and change it back.
The best way to do this is CTRL+ALT+F6 then CTRL+ALT+F7

I am also seeing the issue where X is not showing the docked monitors (eDP) as active if I:

suspend -> undock -> resume -> suspend dock -> resume

apport is reporting crashes frequently (using the non free Nvidea driver so I assumed this was the issue).

The bit of information I can add is that apparently Windows users are effected by the screen flashing also (in a company so everyone has the same laptop)!

Dell released a BIOS update to fix the flashing, but it didn't help. Just wanted to add this as it may be a firmware issue.

#uname -a
Linux 4.2.0-18-generic #22-Ubuntu SMP Fri Nov 6 18:25:50 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

#lspci
00:00.0 Host bridge: Intel Corporation Broadwell-U Host Bridge -OPI (rev 09)
00:02.0 VGA compatible controller: Intel Corporation Broadwell-U Integrated Graphics (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 Camarillo Device (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 RAID bus controller: Intel Corporation 82801 Mobile SATA Controller [RAID 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)

Revision history for this message
Manu Cogolludo (makova) wrote :

Lenovo Thinkpad X1 carbon Intel® Core™ i7-5600U CPU @ 2.60GHz × 4
Intel® HD Graphics 5500 (Broadwell GT2)
Ubuntu 15.10 Gnome-shell Kernel 4.2 and 4.3 bug

dmesg
[drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)!

Revision history for this message
ajoffre (alexandre-joffre) wrote :
Download full text (10.9 KiB)

Toshiba Z30B 11W Intel® Core™ i7-5600U CPU @ 2.60GHz × 4
Kunbuntu 15.10

When I plug in a second monitor (HDMI ) The computer freezes.
Thank you for your support

Nov 19 09:12:12 ajoffre-PORTEGE-Z30-B kernel: [ 111.273294] [drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)!
Nov 19 09:12:12 ajoffre-PORTEGE-Z30-B kernel: [ 111.293273] [drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)!
Nov 19 09:12:13 ajoffre-PORTEGE-Z30-B rtkit-daemon[1947]: Supervising 3 threads of 1 processes of 1 users.
Nov 19 09:12:13 ajoffre-PORTEGE-Z30-B rtkit-daemon[1947]: Successfully made thread 2837 of process 1946 (n/a) owned by '1000' RT at priority 5.
Nov 19 09:12:13 ajoffre-PORTEGE-Z30-B rtkit-daemon[1947]: Supervising 4 threads of 1 processes of 1 users.
Nov 19 09:12:13 ajoffre-PORTEGE-Z30-B kernel: [ 112.161804] ------------[ cut here ]------------
Nov 19 09:12:13 ajoffre-PORTEGE-Z30-B kernel: [ 112.161819] WARNING: CPU: 1 PID: 1472 at /build/linux-jJX2Dm/linux-4.2.0/drivers/gpu/drm/drm_irq.c:1171 drm_wait_one_vblank+0x1b8/0x1c0 [drm]()
Nov 19 09:12:13 ajoffre-PORTEGE-Z30-B kernel: [ 112.161820] vblank wait timed out on crtc 1
Nov 19 09:12:13 ajoffre-PORTEGE-Z30-B kernel: [ 112.161821] Modules linked in: rfcomm drbg ansi_cprng ctr ccm ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter ip_tables x_tables pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) binfmt_misc bnep uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core v4l2_common videodev btusb cdc_mbim media btrtl btbcm btintel cdc_wdm bluetooth cdc_ncm usbnet mii arc4 intel_rapl iosf_mbi x86_pkg_temp_thermal intel_powerclamp coretemp crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel iwlmvm aes_x86_64 lrw gf128mul mac80211 glue_helper ablk_helper cryptd joydev input_leds serio_raw iwlwifi snd_hda_codec_realtek snd_hda_codec_generic snd_hda_codec_hdmi cfg80211 rtsx_pci_ms snd_soc_rt5640 mei_me snd_soc_rl6231 memstick snd_soc_core snd_hda_intel lpc_ich snd_compress shpchp ac97_bus snd_pcm_dmaengine mei snd_hda_codec snd_seq_midi snd_seq_midi_event snd_hda_core snd_hwdep snd_pcm snd_rawmidi toshiba_acpi sparse_keymap snd_seq toshiba_haps toshiba_bluetooth snd_seq_device snd_timer snd tpm_infineon dw_dmac soundcore dw_dmac_core snd_soc_sst_acpi 8250_dw i2c_designware_platform spi_pxa2xx_platform i2c_designware_core mac_hid kvm_intel kvm nfsd auth_rpcgss nfs_acl parport_pc lockd grace sunrpc ppdev lp parport autofs4 rtsx_pci_sdmmc i915 i2c_algo_bit drm_kms_helper psmouse drm ahci e1000e libahci ptp rtsx_pci pps_core wmi sdhci_acpi video sdhci
Nov 19 09:12:13 ajoffre-PORTEGE-Z30-B kernel: [ 112.161881] CPU: 1 PID: 1472 Comm: Xorg Tainted: G W OE 4.2.0-18-generic #22-Ubuntu
Nov 19 09:12:13 ajoffre-PORTEGE-Z30-B kernel: [ 112.161882] Hardware name: TOSHIBA PORTEGE Z30-B/PORTEGE Z30-B, BIOS Version 3.40 06/26/2015
Nov 19 09:12:13 ajoffre-PORTEGE-Z30-B kernel: [ 112.161883] 0000000000000000 000000002169d6e8 ffff8804076279e8 ffffffff817e8c09
Nov 19 09:12:13 ajoffre-PORTEGE-Z30-B kernel: [ 112.161886] 0000000000000000 ffff880407627a40 ffff880407627a28 ffffffff8107b3c6
Nov 19 09:12:13 ajoffre-PORT...

Revision history for this message
Paul (oldcoderexception) wrote :

Had it happen today for the first time. Other than Ubuntu updates no changes to the configuration in months so it seems to be a very recent change. The last time I used the dual monitor config was 5 days ago, with no troubles at all. Now the 2nd monitor (4k) goes blank and comes back about every 5 seconds. Tried resetting display resolution (and then back again) and may have helped for now.

Latest Dell XPS13 dev edition running Ubuntu 15.04.

uname
Linux crom 3.19.0-33-generic #38-Ubuntu SMP Fri Nov 6 18:18:12 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

dmesg
[27734.104083] [drm:gen8_irq_handler [i915_bpo]] *ERROR* The master control interrupt lied (SDE)!
(many times)

lspci
00:00.0 Host bridge: Intel Corporation Broadwell-U Host Bridge -OPI (rev 09)
00:02.0 VGA compatible controller: Intel Corporation Broadwell-U Integrated Graphics (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 Camarillo Device (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: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: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)
00:1f.6 Signal processing controller: Intel Corporation Wildcat Point-LP Thermal Management Controller (rev 03)
01:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5249 PCI Express Card Reader (rev 01)
02:00.0 Network controller: Broadcom Corporation BCM4352 802.11ac Wireless Network Adapter (rev 03)

Revision history for this message
Yuri Ribeiro Sucupira (yuri-sucupira) wrote :

This bug also affects me. Well, now it doesn't anymore, because I've downgraded my system kernel.

Device: notebook Dell Inspiron 5548

Operating system: 64-bit XUbuntu Linux 14.04

Processor: Intel Core i7-5500U

Video: dual chip. These are the two display controllers:
- Advanced Micro Devices, Inc. [AMD/ATI] Topaz XT [Radeon R7 M260] display controller 33000000Hz (requires kernel module / device driver "fglrx"); and
- Intel Corporation Broadwell-U Integrated Graphics VGA compatible controller 33000000Hz (requires kernel module / device driver "i915").

Problem: the message "[drm:gen8_irq_handler [i915_bpo]] *ERROR* The master control interrupt lied (SDE)!" floods my dmesg, and from time to time my system crashes and my computer powers off. If I 'cat /var/log/kern.log |grep -i i915' i see a huge amount of messages exactly like this one, hence I can only assume that the kernel module i915_bpo is buggy (or these kernels are buggy while they interact with that kernel module). My notebook is subtly powering off from time to time (unrelated with overheat, I'm pretty sure 'coz I've already monitored temperature parameters and also 'coz I'm using a cooling laptop base/pad, besides the fact that my notebook is brand-new: only 1 week old).

Kernels I've tested which have this issue:
- 3.19.0-18-generic
- 3.19.0-23-generic
- 3.19.0-28-generic
- 3.19.0-33-generic
- 4.2.0-18-generic

All of them have the same problem: the kernel module "i915.ko" (in 4.2.0-18-generic) and the kernel module "i915_bpo.ko" (in kernels 3.19.0-??-generic) randomly cause subtle system shutdown (halt / poweroff) in my notebook.

Solution: I downgraded to kernel 3.13.0-36-generic, which isn't buggy with its "i915_bdw.ko" (version 3.0) kernel object (module). Full path for this module: /lib/modules/3.13.0-36-generic/kernel/ubuntu/i915/i915_bdw.ko

Notes:
- "bdw" stands for "Broadwell"
- "bpo", I believe, stands for "backport"

IMO, this bug is pretty serious and is taking a lot of time to get fixed: my notebook could get damaged if it kept subtly powering off several times a day, on an everyday basis, like it was doing because of this bug. Hence, my strong suggestion to those who are experiencing this issue is to downgrade to a stable kernel version (I recommend kernel 3.13.0-36-generic).

If you don't want to downgrade your kernel: become root ('sudo su'), then open '/etc/default/grub' for edition (e.g. 'gedit /etc/default/grub'), then add the 'nomodeset' option to "GRUB_CMDLINE_LINUX_DEFAULT=" (e.g. GRUB_CMDLINE_LINUX_DEFAULT="nomodeset"), then save the file, exit the text editor and, still as root, run the command 'update-grub && telinit 6'. Your GRUB will be updated and your system will be restarted. After that you won't be able to see OpenGL graphics anymore (e.g. Xscreensaver openGL screensavers won't load), but your system will stop subtly powering off.

Revision history for this message
In , Jani-nikula (jani-nikula) wrote :

commit 6a39d7c986be4fd18eb019e9cdbf774ec36c9f77
Author: Jani Nikula <email address hidden>
Date: Wed Nov 25 16:47:22 2015 +0200

    drm/i915: fix the SDE irq dmesg warnings properly

Revision history for this message
Tom Lime (0x6d3468) wrote :

This issue affect lenovo t450s as well. As result when connected to docking station with two monitors attached (vga and dvi) monitors are not recognized and dmesg flooded with infamous error ([ 743.432704] [drm:gen8_irq_handler [i915_bpo]] *ERROR* The master control interrupt lied (SDE)!). It doesn't crash the computer but in some cases make displays unrecognizable when undock
|dock.

- device: lenovo t450s
- proc: i7-5600U
- OS: ubuntu 14.04.03
    - kernel: 3.19.0-33-generic x86_64
- video:
        *-display
             description: VGA compatible controller
             product: Broadwell-U Integrated Graphics
             vendor: Intel Corporation
             physical id: 2
             bus info: pci@0000:00:02.0
             version: 09
             width: 64 bits
             clock: 33MHz
             capabilities: msi pm vga_controller bus_master cap_list rom
             configuration: driver=i915_bpo latency=0
             resources: irq:45 memory:e0000000-e0ffffff memory:d0000000-dfffffff ioport:3000(size=64)

Revision history for this message
darkhawk (info-sarazin) wrote :

True @Tom i'm running Ubuntu 15.10 also on a Lenovo T450s (20BX000TGE - BIOS 1.16) and have these issues.

Since upgrading to Kernel 4.2.0-19-generic i can't remember that the screen issue has occured again...both external displays are working as expected.

I only see this issue:

[ 14.334606] [drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)!

sometimes after a fresh boot inside dmesg.

Revision history for this message
Andreas Scherbaum (ads-launchpad) wrote :

I see the same error message when I try the following:

* laptop is in docking station, external monitor is connected
* send laptop to sleep
* undock laptop
* wake laptop up

The error message is present on the terminal, my KDE session is logged out. Nothing useful in .xsession-errors though.
The laptop is a new T450s, running Kubuntu 15.10.

Revision history for this message
zeine77 (mohamed-eyil) wrote :

I got this error on my HP Notebook 15-ac131ne (i3-5005U) with Ubuntu Gnome 15.10 freshly installed. Errors show just before login prompt. I can log in to my desktop after that.

[26255.192670] [drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)!
[26255.194650] [drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)!
[26255.202474] [drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)!
[26255.203480] [drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)!
[26255.210467] [drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)!
[26255.211472] [drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)!

Revision history for this message
Michel Weimerskirch (michel-weimerskirch) wrote :

When connecting my Lenovo T450s to the dock, the screen gets black after logging in and I have the same error message:
[drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)!

This is with Ubuntu 15.10 and Kernel 4.2.0-19.
Updating to 4.4.0-rc4 didn't help. The problem remained.

Downgrading to 3.13 worked though: The error message is gone and the external screen works again.

Revision history for this message
Joakim Koed (vooze) wrote :

So I have this issue as well.

X1 carbon 2015 (broadwell) i5 5200U.

For me this happens without any external monitor, the system just crashes/freezes at random.
[drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)!

I have tried the following kernels:

4.2.0-18
4.2.5
4.3.3

It would seem as this is an upstream issue, am I correct?

Revision history for this message
In , Chris Wilson (ickle) wrote :

Still present as of

commit 0035ecf934fae0492c2d90390f88b8c79e806ffa
Author: Daniel Vetter <email address hidden>
Date: Mon Dec 14 10:41:10 2015 +0100

    drm-intel-nightly: 2015y-12m-14d-09h-40m-37s UTC integration manifest

will look into the debug printk next time I have the box connected to a display.

Revision history for this message
Morten Clausen (morten-c) wrote :

Bug 80896 is closed with fix released (which isn't fixing the issue), but there is another one open on freedesktop bugtracker.

Changed in linux:
importance: High → Unknown
status: Fix Released → Unknown
Revision history for this message
Morten Clausen (morten-c) wrote :

@joakimkoed Yes this seems to be an upstream issue, see (updated) related freedesktop bug above, with no (working) fix released yet.

I can confirm the behaviour with an without connected external monitor (already confirmed for 4.2. 0-16 genirc, can also confirm for 4.3.3-040303-generic).

Changed in linux:
importance: Unknown → Medium
status: Unknown → Confirmed
Revision history for this message
Joakim Koed (vooze) wrote :

I'm considering downgrading to 3.13 like others have said.

Is there any downsides to this for new-ish broadwell machines? Stuff thats not working etc.?

Revision history for this message
Joakim Koed (vooze) wrote :

Sorry for spam.

I can confirm 3.13 is okay regarding this issue. Not really a good kernel for broadwell laptops, since some FN-keys don't work etc. but it will do for exam tomorrow :)

Revision history for this message
In , Joakim Koed (vooze) wrote :

Hello.

Just wanted to let you know (if you were unaware) this bug does also make the system freeze randomly. I have tried to figure out what triggers it, but it seems just random. If anything it happens after 2-3 hours of activity and then 2-5 mins idle?

On kernel 3.13 it works.

Please feel free to ask me to test fixes if you need. I can compile myself (with a patch) or I can test a kernel you compile.

Hope its okay to write here as a non-dev.

Revision history for this message
hitchhiker54 (hitchhiker54) wrote :

I see this bug on Ubuntu Gnome 15.10 with standard kernel only (4.2.0-22-generic at time of writing) with intel microcode active from additional drivers. The only freezes I have noticed appear to be connected to a bug in asus_nb_wmi so are unlikey to help in this case.

Hardware : Asus X555LAB laptop with BIOS revision 503 using i5 5200U processor and integrated graphics.

Revision history for this message
Matt (reg-launchpad-net) wrote :

Also experiencing this with 14.04 dell XPS 9350 Intel(R) Core(TM) i7-5500U

Revision history for this message
Londé Ngosso (londe-ngosso) wrote :

I have the same error and random freeze with kernel 3.19.0-42-generic (and other kernels), not with kernel 3.13.

on Dell Inc. Inspiron 5558 with Ubuntu 14.04.3 LTS 64 bits - Bios A07 - Intel® Core™ i5-5200U CPU @ 2.20GHz × 4 - Intel® HD Graphics 5500

Revision history for this message
Carroarmato0 (carroarmato0) wrote :

I had to give a presentation with my laptop recently which has the same issue of having the second screen randomly turn black and then back on again.

Interestingly the presentation went without a hickup.

The thing that was different, was that I am having the issue when the secondary screen was connected through HDMi ( with a minidisplay to HDMI adaptor).

I wasn't having the issue using a mini display to VGA connector to a projector with a far lower resolution as my secondary screen.

Revision history for this message
ming (mctiew) wrote :

Want to mention that I am hit by this problem too.

HP-ProBook-430-G2 3.19.0-42-generic x86_64

Downgraded to 3.13.0-74 did not work out because hit by another different problem which shows up in 3.13.0-74, ie when wake up from suspend, the display got messed up. The display will not be restored correctly.

Revision history for this message
Manu Cogolludo (makova) wrote :

Current Kernel 4.4 RC6 is not problem.
System Information
 Manufacturer: LENOVO
 Product Name: 20BSCTO1WW
 Version: ThinkPad X1 Carbon 3rd

uname -r
4.4.0-040400rc6-generic

uname -a
Linux Lucy 4.4.0-040400rc6-generic #201512202030 SMP Mon Dec 21 01:32:09 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

Revision history for this message
Joakim Koed (vooze) wrote :

#88

Great!! Good to hear. Now we just have to wait to 4.4 stable and this and go away for good =)

Revision history for this message
Manu Cogolludo (makova) wrote : Re: [Bug 1488719] Re: dmesg shows "[drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)!"

Hi, yes .D

2015-12-26 19:44 GMT+01:00 Joakim Koed <email address hidden>:

> #88
>
> Great!! Good to hear. Now we just have to wait to 4.4 stable and this
> and go away for good =)
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1488719
>
> Title:
> dmesg shows "[drm:gen8_irq_handler [i915]] *ERROR* The master control
> interrupt lied (SDE)!"
>
> Status in Linux:
> Confirmed
> Status in linux package in Ubuntu:
> Confirmed
>
> Bug description:
> On a recent intel NUC using i915 graphics, I get the following errors
> in dmesg:
>
> [drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt
> lied (SDE)!
>
> There are two monitors connected to this box, one with mini-
> HDMI->HDMI, one with mini-DP->HDMI cable.
>
> Maybe related:
>
> https://bugs.freedesktop.org/show_bug.cgi?id=80896
>
> ProblemType: Bug
> DistroRelease: Ubuntu 15.04
> Package: linux-image-generic 3.19.0.26.25
> ProcVersionSignature: Ubuntu 3.19.0-26.28-generic 3.19.8-ckt4
> Uname: Linux 3.19.0-26-generic x86_64
> ApportVersion: 2.17.2-0ubuntu1.3
> Architecture: amd64
> Date: Wed Aug 26 10:07:31 2015
> InstallationDate: Installed on 2015-08-01 (24 days ago)
> InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
> ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-26-generic.efi.signed
> root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
> SourcePackage: linux
> UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
> UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/linux/+bug/1488719/+subscriptions
>

--
Manu

Revision history for this message
Londé Ngosso (londe-ngosso) wrote :

Kernel 4.4 RC6 did not solve the problem on my laptop when i plugged a hdmi cable to the tv => same error.

System information: Dell Inc. Inspiron 5558 with Ubuntu 14.04.3 LTS 64 bits - Bios A07 - Intel® Core™ i5-5200U CPU @ 2.20GHz × 4 - Intel® HD Graphics 5500

Revision history for this message
Joakim Koed (vooze) wrote :

Just testet RC7 from mainline, and it seems to be gone here as well. No messages in /var/log/syslog.

Revision history for this message
Peter Bodrovics (bodrovics) wrote :

Also tested 4.4.0 RC7 and error is gone.

Dell Latitude E5250 with Linux Mint 17.3, BIOS A10, Intel Core i5

Revision history for this message
Londé Ngosso (londe-ngosso) wrote :

Also tested Kernel 4.4 RC7 did not solve the problem on my laptop when i plugged a hdmi cable to the tv => the same error appears in /var/log/syslog. Error disappears when i unplugged the hdmi cable.

System information: Dell Inc. Inspiron 5558 with Ubuntu 14.04.3 LTS 64 bits - Bios A07 - Intel® Core™ i5-5200U CPU @ 2.20GHz × 4 - Intel® HD Graphics 5500

$ uname -a
Linux portable-londe 4.4.0-040400rc7-generic #201512272230 SMP Mon Dec 28 03:32:16 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

Revision history for this message
Arnau (arnaubcn) wrote :
Download full text (86.0 KiB)

Hi gents,

Also, it is happening on a toshiba portege with intel corei7:
happening a lot when using Mixxx.

uname -a:
Linux warlock 4.2.0-22-generic #27-Ubuntu SMP Thu Dec 17 22:57:08 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

dmesg -r | egrep "<[1-3]>" |grep drm

<3>[ 4.286665] [drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)!
<3>[ 5.006249] [drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)!
<3>[ 22.784920] [drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)!
<3>[ 22.785111] [drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)!
<3>[ 22.785409] [drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)!
<3>[ 22.785594] [drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)!
<3>[ 22.785878] [drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)!
<3>[ 22.786051] [drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)!
<3>[ 22.786340] [drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)!
<3>[ 22.786497] [drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)!
<3>[ 22.786667] [drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)!
<3>[ 22.786819] [drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)!
<3>[ 22.786986] [drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)!
<3>[ 22.787137] [drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)!
<3>[ 22.787290] [drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)!
<3>[ 22.787459] [drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)!
<3>[ 22.787610] [drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)!
<3>[ 22.787778] [drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)!
<3>[ 22.787929] [drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)!
<3>[ 22.788081] [drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)!
<3>[ 22.788250] [drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)!
<3>[ 22.788401] [drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)!
<3>[ 22.788688] [drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)!
<3>[ 22.788979] [drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)!
<3>[ 22.789269] [drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)!
<3>[ 22.789559] [drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)!
<3>[ 22.789851] [drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)!
<3>[ 22.790141] [drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)!
<3>[ 22.790432] [drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)!
<3>[ 22.790722] [drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)!
<3>[ 22.790877] [drm:ge...

Revision history for this message
Jan Pfeifer (pfjan) wrote :

Also on Dell XPS-13, Ubuntu 15.10, kernel 4.2.0-22.

X doesn't start here :(

Revision history for this message
Joakim Koed (vooze) wrote :

We now know the problem is in 3.16, 3.19, 4.2 etc. No need to keep reporting that :)

Please check if 4.4RC7 works, thats helps more.

Revision history for this message
Falx (thomasdupont100) wrote :

A bit more contex:

 I run lubuntu 5.10 with 4.4.0 RC7 now and it still happens. Quickly reproducable when doing in-home streaming to my lubuntu client. The stream (h264 decoding) crashes quite rapidly, and the typical dmesg output is present.

Revision history for this message
Morten Clausen (morten-c) wrote :

Tested 4.4.0 RC7 on Thinkpad T450s with i7-5600U. Error is still present like before, the log message is present with and without ext. display connected, although still much higher frequency of log msgs with ext. display connected.

Revision history for this message
Raniz (raniz-1) wrote :

Happening here as well with 4.4.0 RC7

$ uname -r v
4.4.0-040400rc7-generic #201512272230 SMP Mon Dec 28 03:32:16 UTC 2015

$ dmesg | egrep '(intel|i915)'
[ 0.149154] pci 0000:00:14.0: reg 0x10: [mem 0xe1220000-0xe122ffff 64bit]
[ 0.649005] [<ffffffff81f661fd>] intel_uncore_init+0xe2/0x2e1
[ 0.649435] audit: type=2000 audit(1451915134.644:1): initialized
[ 0.985552] intel_idle: MWAIT substates: 0x11142120
[ 0.985553] intel_idle: v0.4 model 0x3D
[ 0.985554] intel_idle: lapic_timer_reliable_states 0xffffffff
[ 1.114161] rtc_cmos 00:02: setting system clock to 2016-01-04 13:45:35 UTC (1451915135)
[ 1.453450] fb: switching to inteldrmfb from VESA VGA
[ 1.475347] [drm] Initialized i915 1.6.0 20151010 for 0000:00:02.0 on minor 0
[ 1.580736] fbcon: inteldrmfb (fb0) is primary device
[ 2.687961] [drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)!
-- Repeated 44 times --
[ 2.752695] [drm] GMBUS [i915 gmbus dpb] timed out, falling back to bit banging on pin 5
[ 2.817096] [drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)!
-- Repeated 56 times --
[ 2.851265] i915 0000:00:02.0: fb0: inteldrmfb frame buffer device
[ 2.902734] [drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)!
-- Repeated 91 times --
[ 3.467690] snd_hda_intel 0000:00:03.0: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915])
[ 3.785259] intel_rapl: Found RAPL domain package
[ 3.785262] intel_rapl: Found RAPL domain core
[ 3.785264] intel_rapl: Found RAPL domain uncore
[ 3.785265] intel_rapl: Found RAPL domain dram
[ 6.732430] [drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)!
-- Repeated 44 times --
[ 47.125136] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun
[ 47.128273] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe B FIFO underrun
[ 70.590927] [drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)!
-- Repeated 98 times --

Revision history for this message
Joakim Koed (vooze) wrote :

Just testet RC7 again.

I do not get any errors before I put in HDMI cable. Before I got error messages even without cable, now it only happens with cable. So something got better, but just not good enough :)

Revision history for this message
ddalex (ddalex) wrote :

Can confirm this bug on Macbook12,1 running 4,4rc7 and a single display on a miniDP connector.

Revision history for this message
Morten Clausen (morten-c) wrote :

I have to revice my comment from January 4th. The error is gone without external display connected with 4.4.0 rc7 for me too, still occuring with ext. display connected. I'm not sure what I was looking at, maybe booted the wrong kernel, stupid me.

Since yesterday 4.4.0 rc8 is released, same behaviour without external display connected, error is gone. I will check rc8 with external display connected later this day when I'm at home.

Revision history for this message
Londé Ngosso (londe-ngosso) wrote :

Also tested Kernel 4.4 RC8 => the same error appears in /var/log/syslog when i connect my laptop to the tv with a hdmi cable.
The error appears only at the moment when i plug the hdmi cable. Then it stops.
Then i change the configuration of the sound to hdmi display port. And the same error occurs at the moment i changed the sound configuration. see dmesg in attachment.

System information: Dell Inc. Inspiron 5558 with Ubuntu 14.04.3 LTS 64 bits - Bios A07 - Intel® Core™ i5-5200U CPU @ 2.20GHz × 4 - Intel® HD Graphics 5500

Revision history for this message
Falx (thomasdupont100) wrote :

Just tested 4.4.0-040400rc8-generic (4.4.0 RC8).

Still get the [drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)! in dmesg output though.

See attached file for my dmesg output after login.

Revision history for this message
Sera (seraphim6x7) wrote :

I've just rebooted with kernel 4.4.0-040400rc8 as well and also continue to see the 'interrupt lied' line. The situation has improved though.

Quick summary, just ask if you want more details/logs.

System information: HP EliteBook, Ubuntu 15.10, i7-5600U, Broadwell-U Integrated Graphics (rev 09)

Previously with the stock Ubuntu 15.10 kernel I was unable to attach a second display unless I connected the display before startup / early in the boot process and closed the laptop lid. Attaching a display over displaylink worked fine in that case. Attaching it over VGA limited me to 1024x768 resolution. Setting modelines for higher resolutions through xrandr resulted in an unusable desktop.

Currently with 4.4.0-040400rc8 I'm able to attach my VGA display after the desktop environment is running and use the second screen to extend the desktop. Setting a different modeline still results in an unusable desktop. I haven't had the opportunity to test a displaylink display since installing this kernel.

Thanks for progressing on this issue.

Revision history for this message
In , Jani-nikula (jani-nikula) wrote :

(In reply to Joakim Koed from comment #23)
> Just wanted to let you know (if you were unaware) this bug does also make
> the system freeze randomly. I have tried to figure out what triggers it, but
> it seems just random. If anything it happens after 2-3 hours of activity and
> then 2-5 mins idle?

I don't think what you're seeing has anything to do with this bug. Please file a new bug report for the symptoms you're seeing.

> Hope its okay to write here as a non-dev.

Absolutely.

Revision history for this message
In , Jani-nikula (jani-nikula) wrote :

commit 2dfb0b816d224379efc534764388745c474abeb4
Author: Jani Nikula <email address hidden>
Date: Thu Jan 7 10:29:10 2016 +0200

    drm/i915: shut up gen8+ SDE irq dmesg noise, again

Revision history for this message
In , Niccolò Belli (darkbasic) wrote :

When did you shut up the messages for the first time? I always saw them in every RC, including latest 4.4-rc8.

Revision history for this message
In , Jani-nikula (jani-nikula) wrote :

(In reply to darkbasic from comment #26)
> When did you shut up the messages for the first time? I always saw them in
> every RC, including latest 4.4-rc8.

drm-next, not Linus' upstream.

Revision history for this message
neufeind (neufeind) wrote :

Found something here: https://bugs.freedesktop.org/show_bug.cgi?id=92084

It mentions a kernel-fix:
commit 2dfb0b816d224379efc534764388745c474abeb4
Author: Jani Nikula <email address hidden>
Date: Thu Jan 7 10:29:10 2016 +0200

    drm/i915: shut up gen8+ SDE irq dmesg noise, again

Revision history for this message
Gronor (tonut) wrote :
Download full text (4.8 KiB)

Hi, I am also plagued by this very annoying bug.

I am running Ubuntu 16.04

kernel 4.3.0-7-generic #18-Ubuntu SMP Tue Jan 19 15:46:45 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

on a Dell XPS 13 9343

This particular laptop has a mini DisplayPort output which I connected to a DisplayPort MST hub. The DisplayPort outputs from this hub are connected with DP to HDMI cables to 3 full HD monitors.

My dmesg shows lots of: [drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)!

I also see in the kernel log:

[ 92.948779] i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has bogus alignment
[ 93.451068] ACPI Error: Cannot release Mutex [PATM], not acquired (20150818/exmutex-376)
[ 93.451073] ACPI Error: Method parse/execution failed [\_SB.PCI0.LPCB.ECDV._Q66] (Node ffff8802170cae10), AE_AML_MUTEX_NOT_ACQUIRED (20150818/psparse-542)
[ 288.672984] ------------[ cut here ]------------
[ 288.673012] WARNING: CPU: 3 PID: 1278 at /build/linux-HskGKW/linux-4.3.0/drivers/gpu/drm/i915/intel_uncore.c:620 hsw_unclaimed_reg_debug+0x69/0x90 [i915]()
[ 288.673014] Unclaimed register detected before writing to register 0x44414
[ 288.673015] Modules linked in: rfcomm xt_addrtype xt_conntrack ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 iptable_filter ip_tables x_tables nf_nat nf_conntrack bridge stp llc pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) aufs vboxdrv(OE) binfmt_misc bnep btusb btrtl btbcm btintel bluetooth snd_usb_audio hid_generic snd_usbmidi_lib uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core v4l2_common videodev media hid_multitouch dell_wmi sparse_keymap dell_laptop dcdbas snd_hda_codec_hdmi intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp crct10dif_pclmul crc32_pclmul wl(POE) aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd input_leds joydev serio_raw dell_led intel_pch_thermal snd_hda_codec_realtek snd_hda_codec_generic
[ 288.673057] cfg80211 mei_me lpc_ich rtsx_pci_ms memstick mei shpchp snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep snd_soc_ssm4567 elan_i2c soc_button_array int3403_thermal dw_dmac dw_dmac_core 8250_dw snd_soc_sst_acpi spi_pxa2xx_platform i2c_designware_platform i2c_designware_core int3402_thermal mac_hid tpm_crb processor_thermal_device int340x_thermal_zone acpi_als int3400_thermal acpi_pad intel_soc_dts_iosf acpi_thermal_rel kfifo_buf industrialio kvm_intel kvm snd_soc_rt286 snd_soc_rl6347a snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device snd_timer snd soundcore parport_pc ppdev lp parport autofs4 btrfs xor hid_logitech_hidpp hid_logitech_dj raid6_pq usbhid rtsx_pci_sdmmc i915 i2c_algo_bit drm_kms_helper psmouse
[ 288.673096] syscopyarea sysfillrect sysimgblt fb_sys_fops ahci drm libahci rtsx_pci wmi video sdhci_acpi i2c_hid sdhci hid fjes
[ 288.673108] CPU: 3 PID: 1278 Comm: Xorg Tainted: P OE 4.3.0-7-generic #18-Ubuntu
[ 288.673110] Hardware name: Dell Inc. XPS 13 9343/09K8G1, BIOS A07 11/11/2015
[ 288.673112] 0000000000000000 0000000066689b11 ffff8800c2afbb70 ffffffff813d2674
[ 288.673115] ffff88...

Read more...

Revision history for this message
TJ (tj) wrote :

The fix has made its way into the v4.5 merge window and has the mainline commit ID:

ccda3a7 2016-01-13 10:48:11 +0200 N Jani Nikula drm/i915: shut up gen8+ SDE irq dmesg noise, again

Revision history for this message
Gronor (tonut) wrote :

So is it into 4.5 RC1?

Revision history for this message
Morten Clausen (morten-c) wrote :

Yes this patch is in the mainline kernel v4.5-rc1-wily. But I think regarding our problem here it does only what it says: shut up the messages. I just tested it, got a

[drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun

at boot time now (related: https://bugzilla.kernel.org/show_bug.cgi?id=95461), while the

[drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)!

are gone. With external monitor connected things getting worse, gdm isn't able to use the monitor correctly and crashes from time to time. Looks like there are now other i915 bugs (maybe regression?) more urgent. Personally I will stick to 4.4 until I've got time to investigate this further with a clean install of ubuntu to eliminate the possibility that I'm looking at completely unrelated issues here.

Revision history for this message
Londé Ngosso (londe-ngosso) wrote :

Quick test with Kernel 4.5 RC1 connected hdmi for a few seconds => the problem seems to be solved. No error anymore and everything is working fine :-).

System information: Dell Inc. Inspiron 5558 with Ubuntu 14.04.3 LTS 64 bits - Bios A07 - Intel® Core™ i5-5200U CPU @ 2.20GHz × 4 - Intel® HD Graphics 5500

Revision history for this message
Manfred Mager (frediiii) wrote :

I can confirm that for me kernel 4.5 RC1 also seems to have resolved the problem

HP EliteBook folio 1020; GMA 5300; Ubuntu 15.10 x64

Revision history for this message
Carroarmato0 (carroarmato0) wrote :

I also just tried the 4.5.0-040500rc1-generic kernel.

Minidisplay to hdmi convertor.

If I put my secondary screen on 3840x2160, I notice that after awhile I get the same black screen interval bug again.

Keeping the resolution to the same as my laptop ( 1920x1080 ) seems to be stable so far. No flicker yet.

Lenovo T450s, Ubuntu 15.10 x64

Revision history for this message
Nivus (nivus-ua) wrote :

This bug is causing dual monitor problem for me as well. It looks like it was registered a long ago, when can I track if it gets fixed? It is quite annoying that there are two options: either use laptop's display only or use laggy open drivers...

Reproduced in: DELL INSPIRON 5749
NVIDIA GeForce 840M
Kubuntu 15.10 x64

I would appreciate any advice.

Thank you.

Revision history for this message
Gronor (tonut) wrote :

Kernel 4.5 RC1 did not fix it for me. It is even worse at times

Revision history for this message
Markus (chickenmarkus) wrote :

I have that message with a HP EliteBook 850 G2 and docking station under kernel 3.19.0-49-generic on Xubuntu 14.04. I think it causes an issue with unrecognised external monitor. I have attached the syslog while reproducing via following steps:

0. directly after boot: external display is not recognised even it's connected to connected docking station (USB works fine)
1. disconnect docking station (line 1)
1. connect docking station (line 7)
2. activate external display (line 788)
3. deactivate external display (1407)
4. external display is not recognised again (USB works fine)

Maybe this is helpfull for fixing.

Revision history for this message
Raniz (raniz-1) wrote :

The error messages have gone away with 4.5-RC1 but the issues remain (i.e. display flicker, display won't turn on again after computer has gone to sleep.

I've currently only got this error message in my DMESG:

[ 21.277697] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe B FIFO underrun

Revision history for this message
Londé Ngosso (londe-ngosso) wrote :

I've got the same bug. It seems solved with kernel 4.5 RC3.

see https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1542934?comments=all

Revision history for this message
Bernhard Schussek (bschussek) wrote :

Same problem here on Lenovo T450s with kernel 4.2.0-27.

Revision history for this message
Jeffrey Walton (noloader) wrote :

From Comment #48 (https://bugs.launchpad.net/linux/+bug/1488719/comments/48):

> If you don't want to downgrade your kernel: become root ('sudo su'),
> then open '/etc/default/grub' for edition (e.g. 'gedit /etc/default/grub'),
> then add the 'nomodeset' option to "GRUB_CMDLINE_LINUX_DEFAULT="
> (e.g. GRUB_CMDLINE_LINUX_DEFAULT="nomodeset")

I've got a ChromeBook that boots with "i915.modeset=1" kernel parameter. I'm just mentioning it for completeness.

For more or the modeset option, see http://unix.stackexchange.com/questions/110573/what-is-i915-modeset-1-for .

Revision history for this message
darkhawk (info-sarazin) wrote :

I'm not sure, but sometimes you can cheat with your system.

Example:

1.) working with your dual monitor
2.) lock your desktop (windows key and l for example)
3.) you see both external monitors locked
4.) wait sometime and they go to power safe mode
5.) coming back, press a key and see that only one monitor is available...the other one is still in power safe mode
6.) press STRG+ALT and 2 (or 3 or any other number with a terminal assigned)
7.) see a lot of drm:gen8_irq_handler error messages
8.) wait a moment and the other monitor which was/is in power safe mode will power up and showing up the same errors
9.) now yo back to your graphical UI (most of times STRG+ALT + 7)
10.) you might see that both screens are working again in dual mode...

I did this now for a lot of times (because setting the display settings up again sucks)

Revision history for this message
Jeffrey Walton (noloader) wrote :

From Comment #124 (https://bugs.launchpad.net/linux/+bug/1488719/comments/124):

> ... I did this now for a lot of times (because setting the display settings up again sucks)

I had luck with the following. It removed all of the dmesg's except one:

   $ uname -a
   Linux qotom 3.19.0-49-generic ...

   $ sudo lspci | grep -is vga
   00:02.0 VGA compatible controller: Intel Corporation
   Broadwell-U Integrated Graphics (rev 09)

And then use the "00:02.0":

   $ sudo cat /etc/rc.local
   #!/bin/sh -e
   # ...
   # By default this script does nothing.

   setpci -s 00:02.0 F4.B=30

   exit 0

Also see http://askubuntu.com/q/136593 and http://askubuntu.com/a/157344 .

Revision history for this message
Carroarmato0 (carroarmato0) wrote :

A colleague of mine sent this link to Lenovo's support page: https://support.lenovo.com/be/nl/documents/HT104459?utm_source=Email&utm_medium=Email&utm_campaign=email%20trace

Says to update the VGA IC firmware.... but using a Windows tool... supposedly fixes the screen flickering on VGA

Revision history for this message
maddin (ich-martin-drees) wrote :

Hello,

same bug here on a Lenovo T450.
Kernel-Version: 4.2.0-27-generic

I have two Monitors connected over the docking station. Sometimes it happens when I'm working, but mostly after i look my system and the monitors come back from sleep mode.

Please fix it :) ...

Revision history for this message
chefarov (chefarov) wrote :

Exact same error message in brand new Dell Latitude e5550 (Intel HD 5500), BUT:
1) No external monitors
2) The laptop won't BOOT, execution hangs up.

Both in 4.2.0-27 amd64 and 4.2.0-16 amd64.
After some reboots it will hang up at
"Started Gnome Display Manager"

Booting in recovery mode I find in dmesg:
"snd_hda_intel 0000:00:03:0: failed to add i915 component master (-19)"

Installing 4.5-rc4-wily gives me:
"possible missing firmware /lib/firmware/i915/skl_guc_ver4.bin for module 915"
and booting it
"error parsing PCC subspaces from PCCT"
boot hangs up again

Revision history for this message
chefarov (chefarov) wrote :

Installing linux-firmware_1.156 from http://ubuntu-master.mirror.tudos.de/ubuntu/pool/main/l/linux-firmware/ didn't help. The problems seems to be when loading gnome. The execution hangs up after:
fsck from ...
ubuntu: X1/Y1 clean files, X2/Y2 clean blocks ...

It seems strange,
I might coincidentally experience another bug that I am not aware of...

Revision history for this message
Yuri Ribeiro Sucupira (yuri-sucupira) wrote :

This is a mysterious bug affecting a LOT of machines. As I suggested at https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1520040, as a temporary workaround I recommend downgrading to kernel "3.13.0-36-generic".

Try it out and see if it is of any help.

Revision history for this message
chefarov (chefarov) wrote :

You are right, I missed it.
I can confirm that Switching back to 3.13.0-36, and lightdm(ok that might be only me) gave me a working system.
Thank you very much

Revision history for this message
dusoft (dusoft-staznosti) wrote :

Not solved for me with kernel 4.5.0-040500rc3-generic
Still happens.

Revision history for this message
In , Yuri Ribeiro Sucupira (yuri-sucupira) wrote :

Please see this bug report:

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1520040

This bug makes my Dell Latitude laptop shutdown (power off). In that bug report I provided a lot of information about my system, logs and tests I did. Currently, only kernel "3.13.0-36-generic" running module "/lib/modules/3.13.0-36-generic/kernel/ubuntu/i915/i915_bdw.ko" doesn't have this bug.

Hence, this bug is far from "solved" and shutting up dmesg definitely won't solve it.

Revision history for this message
In , Chris Wilson (ickle) wrote :

(In reply to Yuri from comment #28)
> Please see this bug report:
>
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1520040
>
> This bug makes my Dell Latitude laptop shutdown (power off). In that bug
> report I provided a lot of information about my system, logs and tests I
> did. Currently, only kernel "3.13.0-36-generic" running module
> "/lib/modules/3.13.0-36-generic/kernel/ubuntu/i915/i915_bdw.ko" doesn't have
> this bug.
>
> Hence, this bug is far from "solved" and shutting up dmesg definitely won't
> solve it.

That has nothing to do with these error messages.

Revision history for this message
Tessa (unit3) wrote :

Seeing with the latest 16.04 desktop nightly, amd64, 2015 Macbook Pro.

Revision history for this message
dreh23 (johannes-amorosa-7) wrote :

I have spam as well and some random crashes loading steam. This started after upgrading to this kernel

Linux slim 3.19.0-51-generic #57-Ubuntu SMP Fri Feb 19 14:05:05 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

External monitor connected to mini display port. Lenovo T450s.

Revision history for this message
Raniz (raniz-1) wrote :

Downgrading to 3.19.0-28 seems to fix the issues for me but that kernel has no support for my WiFi card so I'm stuck with using a kernel with a wonky graphics driver.

Revision history for this message
Carroarmato0 (carroarmato0) wrote :

A new release candidate 4.5-rc6 has been released with the following changes:

Imre Deak (13):
      drm/i915: Add helper to get a display power ref if it was already enabled
      drm/i915: Ensure the HW is powered during display pipe HW readout
      drm/i915/ibx: Ensure the HW is powered during PLL HW readout
      drm/i915: Ensure the HW is powered when disabling VGA
      drm/i915: Ensure the HW is powered during HW access in assert_pipe
      drm/i915/crt: Ensure the HW is powered during HW state readout
      drm/i915/ddi: Ensure the HW is powered during HW state readout
      drm/i915: Ensure the HW is powered when accessing the CRC HW block
      drm/i915/dp: Ensure the HW is powered during HW state readout
      drm/i915/dsi: Ensure the HW is powered during HW state readout
      drm/i915/hdmi: Ensure the HW is powered during HW state readout
      drm/i915/lvds: Ensure the HW is powered during HW state readout
      drm/i915/skl: Ensure HW is powered during DDB HW state readout

Will give it a go as soon as I can

Revision history for this message
Carroarmato0 (carroarmato0) wrote :

I played a movie on a secondary screen for about 1hour and 40min without a glitch running the 4.5.-rc6
Will try some more tests tonight by doing some more random work.

Revision history for this message
Carroarmato0 (carroarmato0) wrote :

So I've been using the secondary screen with random activities like watching youtube clips, browsing, moving windows between the secondary screen and the primary..... different workloads etc for at least 2 hours aaaaand

it didn't blank out on me even once!

Using the 4.5.0-040500rc6-generic build from Ubuntu.

Can other people test out the RC6 of the 4.5 kernel and see if this release candidate also fixes your problems?

Changed in linux:
status: Confirmed → Fix Released
Revision history for this message
Gronor (tonut) wrote :

So did 4.5.0 RC6 fixed it for you guys?

It still reproduces for me even with this kernel

Revision history for this message
dancer7162 (dancer7162) wrote :

Yes it fixed it for me.
System is NUC5i7RYH using the HDMI port (using linux-image-4.5.0-040500rc6-generic, amd64)
thank you guys

Revision history for this message
Carroarmato0 (carroarmato0) wrote :

After some longer tests looks like this is still not 100% with RC6 :(

Revision history for this message
Raniz (raniz-1) wrote :

I haven't noticed any issues in my day-to-day work with RC6. Can't say all issues are completely resolved since I haven't done any exhaustive testing but it's a major improvement over RC5.

Revision history for this message
darkhawk (info-sarazin) wrote :

Hey folks,

there is an BIOS Update for the Lenovo T450s

[Problem fixes]
- Fixed an issue related to system unable to power on due to chipset hang in some specific situation.

Will try this....

Feedback will come

Revision history for this message
darkhawk (info-sarazin) wrote :

Ok, nothing new

[ 1510.565374] [drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)!

Revision history for this message
thomas955 (thoehlig) wrote :

Hi,

we recently got our new E7450 Notebooks from Dell and encountered the same Problems.
Main Problem - Displays flickering or turn to black at all.
We use 3 Displays 2x externeal via DP / HDMI 1920x1080 + E7450 build in with 1920x1080.

OS is Ubuntu 14.04LTS with Kernel 4.2.0-30-generic.
I also tested few hours ago the latest Kernel 4.5.0-040500rc7-generic but after a few minutes one Display started to flicker again.

The dmesg messag "[drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)!" occurs in 4.2 but not in 4.5.

There is another dmesg message in 4.5 that seems to be related to the i915 driver:

[Di Mär 8 17:51:44 2016] pci_bus 0000:02: Allocating resources
[Di Mär 8 17:51:44 2016] pci_bus 0000:03: Allocating resources
[Di Mär 8 17:51:44 2016] i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has bogus alignment
[Di Mär 8 17:51:44 2016] i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has bogus alignment
.
.
.
[Di Mär 8 17:53:14 2016] WARNING: CPU: 0 PID: 1278 at /home/kernel/COD/linux/drivers/gpu/drm/i915/intel_uncore.c:599 hsw_unclaimed_reg_debug+0x69/0x90 [i915]()
[Di Mär 8 17:53:14 2016] Unclaimed register detected after reading register 0x223a0

modinfo i915
filename: /lib/modules/4.5.0-040500rc7-generic/kernel/drivers/gpu/drm/i915/i915.ko
license: GPL and additional rights
description: Intel Graphics
author: Intel Corporation
author: Tungsten Graphics, Inc.
firmware: i915/bxt_dmc_ver1.bin
firmware: i915/skl_dmc_ver1.bin
firmware: i915/skl_guc_ver4.bin
srcversion: A8C37B25F49F03AE77E49D0

Hardware:
E7450
Graphics:
00:02.0 VGA compatible controller: Intel Corporation Broadwell-U Integrated Graphics (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell Device 062e
 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
 Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
 Latency: 0
 Interrupt: pin A routed to IRQ 51
 Region 0: Memory at f5000000 (64-bit, non-prefetchable) [size=16M]
 Region 2: Memory at d0000000 (64-bit, prefetchable) [size=256M]
 Region 4: I/O ports at f000 [size=64]
 Expansion ROM at <unassigned> [disabled]
 Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
  Address: fee00018 Data: 0000
 Capabilities: [d0] Power Management version 2
  Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
  Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
 Capabilities: [a4] PCI Advanced Features
  AFCap: TP+ FLR+
  AFCtrl: FLR-
  AFStatus: TP-
 Kernel driver in use: i915

in addition i have a:
03:00.0 3D controller: NVIDIA Corporation GM108M [GeForce 840M]
but its not in use.

If you need more Information ...
Thank you in advance
Thomas

Revision history for this message
Gronor (tonut) wrote :

@thoehlig can you check if you lower the resolution to 1280 x 1024 you still have this problem? If i switch my external monitors to that resolution, the flickering is gone.

Revision history for this message
thomas955 (thoehlig) wrote :

I will check this, but its not a solution for me and my users to lower the screen resolution to avoid flickering.

Btw. today with Kernel 4.5 i also had flickering but there were no messages in dmesg.

Revision history for this message
Dr4K4n (stefan-dr4k4n) wrote :

I'm having similar problems on my Dell XPS 13 9343 running 15.10 with 4.5.0-040500rc6-generic.
I've ran 2 FullHD displays daisy-chained to the miniDP of the notebook, both monitors switched to DP 1.2. This lead to flickering. I since then dropped that configuration and run a single display set to DP 1.1 without flickering.
Still there are some problems.
When watching a YouTube video fullscreen and changing the volume the screen freezes. The volume overlay doesn't appear, but the video seems to play along and the PC doesn't react to keypresses.
The only way out is switching to a TTY (Ctrl+Alt+F1) and restarting lightdm.

Also since I've switched from 4.2.0-30-generic to 4.5.0-040500rc6-generic the messages in dmesg disappeared.
Please let me know when you need any more infos from me.

Revision history for this message
thomas955 (thoehlig) wrote :

@Gronor Tested 1280x720 on all Displays, same problem.

Revision history for this message
Gronor (tonut) wrote :

That is strange. On that resolution I don't get the flicker. But as you said, it's not an option, though would have been a good indicator for people looking into this.

Revision history for this message
Christian George (radu-j-deactivatedaccount-deactivatedaccount) wrote :

I have a Dell XPS 13 9343 running Ubuntu 15.10 with 4.2.0-16-generic . Every few days my system freezes and I can move the mouse pointer but can't click on anything. Pressing anything on the keyboard has no effect.

I am using the laptop display + an external monitor Dell U2913WM (2560x1080 @60Hz). I see no flicker or anything else on the displays. I only experience the freeze just as Dr4K4n (stefan-dr4k4n) wrote above.

Revision history for this message
thomas955 (thoehlig) wrote :

I think the flickering problem only occurs if you use two external monitors with e-port-dock.

Revision history for this message
Yuri Ribeiro Sucupira (yuri-sucupira) wrote :

"I think the flickering problem only occurs if you use two external monitors with e-port-dock."

In my case, my laptop suddenly powers off. But another bug that happens in it is this: after a while with Xscreensaver running, the screen flickers and remains that way for some 3 extra seconds after I type my password and the screen is unlocked.

Weird thing is that after the screen is unlocked, some 3 seconds later the flickering stops.

Revision history for this message
Morten Clausen (morten-c) wrote :

I'm still not sure what we're looking at here, especially if the original message this bug deals with has anything to do with the other described buggy behaviour here, which are: random freezes, display flickering, not working external displays etc. I watched the development of the comments in this bug really closely (not at least because of my own interests being affected as well) and there hasn't been any real progress in investigating this issue(s) further. I think this is not least caused by the complexity and variatons of issues regarding graphics.

IMHO this leads to three taks which has to be done:

1. Identifiying distinct issues and filing distinct bug reports while being aware of possible duplicates.

2. If you're affected and feeling confident in providing more information, investigate those distinct issues further and provide proper amounts of logs/traces etc. possbile related to those distinct issues.

3. Pushing those issues to the proper upstream bugtrackes. (For me this is one of the hardest parts, since I'm not sure which parts play a role here, e.g. kernel, display manager etc.) When I look at my own logs (attached) my issue still looks like a kernel problem.

I've tested the 4.5RC7, the origial message is gone, but my external display (connected to DP of my advanced lenovo dock) stays black if the T450s is docked while booting. If I undock after boot and then dock it again, the system freezes totally and syslog is showing some serious kernel issues. The only way to cirumvent this behaviour is to boot undocked and then dock when the system is fully booted. I'm currently using this workaround in my daily work to see if there are other issues. I think I will file a bug report on bugs.freedesktop.org later.

Revision history for this message
David Valdivieso (valdorvaldor) wrote :

Happens to me on a NUC i7 DP port..... it happens when monitor goes idle power save mode or when i turn off the monitor.

Linux nuc 4.2.0-16-generic #19-Ubuntu SMP Thu Oct 8 15:35:06 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

Distributor ID: Ubuntu
Description: Ubuntu 15.10
Release: 15.10
Codename: wily

Revision history for this message
Manu Cogolludo (makova) wrote :

Lenovo Think Pad X1 Carbon Intel® Core™ i7-5600U CPU @ 2.60GHz × 4

Kernel solved

uname -a

Linux 4.5.0-040500-generic #201603140130 SMP Mon Mar 14 05:32:22 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

Revision history for this message
Gronor (tonut) wrote :

@Manu, what exactly is fixed? I am running this kernel now and the display flicker issue is not gone

Revision history for this message
Gronor (tonut) wrote :

We might as well close this report, nobody seems to care

Revision history for this message
Piotr (thisredoned) wrote :

uname -a
Linux 4.5.0-040500rc7-generic #201603061830 SMP Sun Mar 6 23:33:11 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

the issue (massive flickering, turning off) is still very much a problem. I'm on dell xps 13 with two dell monitors daisy chained. The second one is getting most of the flickering.

Revision history for this message
SAURABH KUMAR (saurabh-rajrappa7) wrote :

I am facing same issue after once I force shutdown My OS(laptop). And, now I cannot logon.

Revision history for this message
Sigurd Kristensen (sigurd-kristensen) wrote :
Download full text (5.7 KiB)

I have been affected by this bug for a while as well. This is my setup:

Dell E5450 with Ubuntu 14.04.04 LTS with kernel: 4.2.0-34-generic

The laptop is connected to a Dell E-Port Plus Advanced Port Replicator.

The port replicator is connected via two seperate DP -> mDP cables to two monitors of model Dell 27" QHD U2715H.

I get the same annoying error in dmesg but that is the least of my problems. I also get complete crashes where changing TTY is impossible. The entire laptop will also at times reboot, even when not being used. I also get the same problem others have reported where waking up the laptop causes the second screen to go back into power-save mode. I used to have screen flickering in Windows 10 Professional. But i have not seen this behavior in Ubuntu.

I also get this suspicious error in /var/log/syslog

Apr 12 08:53:43 SIKR-E5450 kernel: [ 5.931613] ------------[ cut here ]------------
Apr 12 08:53:43 SIKR-E5450 kernel: [ 5.931631] WARNING: CPU: 1 PID: 1367 at /build/linux-lts-wily-MVxxD8/linux-lts-wily-4.2.0/drivers/gpu/drm/i915/intel_ddi.c:756 intel_ddi_get_crtc_new_encoder+0x94/0xa0 [i915]()
Apr 12 08:53:43 SIKR-E5450 kernel: [ 5.931632] 2 encoders on crtc for pipe A
Apr 12 08:53:43 SIKR-E5450 kernel: [ 5.931633] Modules linked in: pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) cmac dm_crypt dell_wmi sparse_keymap dell_laptop dcdbas dell_smm_hwmon hid_logitech_hidpp uvcvideo intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp videobuf2_vmalloc videobuf2_memops kvm_intel snd_soc_rt5640 videobuf2_core btusb btrtl btbcm v4l2_common btintel kvm videodev snd_soc_rl6231 media crct10dif_pclmul snd_soc_core crc32_pclmul bnep rfcomm snd_compress arc4 ac97_bus snd_pcm_dmaengine bluetooth snd_seq_midi aesni_intel aes_x86_64 iwlmvm lrw gf128mul glue_helper ablk_helper cryptd mac80211 snd_seq_midi_event snd_rawmidi dell_led iwlwifi snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic joydev input_leds snd_hda_intel snd_hda_codec cfg80211 serio_raw snd_seq mei_me snd_hda_core snd_hwdep mei lpc_ich shpchp snd_pcm snd_seq_device snd_timer dw_dmac snd dw_dmac_core int3403_thermal 8250_fintek snd_soc_sst_acpi dell_smo8800 parport_pc soundcore 8250_dw ppdev i2c_hid int3400_thermal spi_pxa2xx_platform processor_thermal_device acpi_thermal_rel acpi_pad dell_rbtn i2c_designware_platform intel_soc_dts_iosf i2c_designware_core mac_hid int3402_thermal acpi_als int340x_thermal_zone lp parport kfifo_buf industrialio hid_logitech_dj hid_generic usbhid hid i915 psmouse i2c_algo_bit ahci drm_kms_helper e1000e libahci drm ptp sdhci_pci pps_core wmi sdhci_acpi video sdhci
Apr 12 08:53:43 SIKR-E5450 kernel: [ 5.931682] CPU: 1 PID: 1367 Comm: Xorg Tainted: G OE 4.2.0-34-generic #39~14.04.1-Ubuntu
Apr 12 08:53:43 SIKR-E5450 kernel: [ 5.931683] Hardware name: Dell Inc. Latitude E5450/09X6YN, BIOS A10 09/01/2015
Apr 12 08:53:43 SIKR-E5450 kernel: [ 5.931684] ffffffffc026b130 ffff8804085eb9c8 ffffffff817b5fed 0000000000000000
Apr 12 08:53:43 SIKR-E5450 kernel: [ 5.931686] ffff8804085eba18 ffff8804085eba08 ffffffff8107799a 0000000100020101
Apr 12 08:53:43 SIKR-E5450 kernel: [ 5.931687] f...

Read more...

Revision history for this message
xeno678g (e3-hvag-jl) wrote :

On NUC NUC5i3RYB
(Lubuntu 15.10 amd64)
BIOS : RYBDWi35.86A.0354.2016.0120.0912 Date: 01/20/2016

kernel 4.6.0-040600rc3-generic from http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.6-rc3-wily/

Finally fixed this for me (Yamaha RX-V475 hdmi handling was/is still buggy).

Revision history for this message
Ed Broadley (rebroad+ubuntu) wrote :

Getting this on: Linux UX303LNB 4.2.0-35-generic #40-Ubuntu SMP Tue Mar 15 22:15:45 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

Also seeing these messages in tty1: [drm:intel_pipe_config_compare [i915]] *ERROR* mismatch in base.adjusted_mode.crtc_clock (expected 138780, found 91519)

Revision history for this message
Ed Broadley (rebroad+ubuntu) wrote :

Also getting this on: Linux UX303LNB 4.2.6-040206-generic #201511091832 SMP Mon Nov 9 23:34:22 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

Revision history for this message
Ed Broadley (rebroad+ubuntu) wrote :
Revision history for this message
Gronor (tonut) wrote :

Hey Ivan,
so with kernel 4.6.0-040600rc3-generic the monitor(s) don't turn on and off anymore?

Revision history for this message
Gronor (tonut) wrote :

Unfortunately 4.6.0-040600rc3-generic still has the intermittent screen blinking issue for me.

Revision history for this message
Ed Broadley (rebroad+ubuntu) wrote :

No longer happening with the latest git build of: Linux UX303LNB 4.6.0-rc3-custom #1 SMP Fri Apr 15 00:59:30 BST 2016 x86_64 x86_64 x86_64 GNU/Linux

Revision history for this message
Gronor (tonut) wrote :

Ed, can you specify what is no longer happening?

Revision history for this message
zeine77 (mohamed-eyil) wrote :

I have written the comment 52 above; those eroor messages seem to be gone with 16.04 release. I have no longer those errors.

Revision history for this message
Gronor (tonut) wrote :

Error messages have been gone for a long time for me. Symptoms however, have not

Revision history for this message
Lauri Niskanen (lauri-niskanen-h) wrote :

[ 35.769534] Bluetooth: RFCOMM socket layer initialized
[ 35.769539] Bluetooth: RFCOMM ver 1.11
[ 367.276773] [drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)!
[ 367.277129] [drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)!
[ 367.278570] [drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)!
[ 367.278928] [drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)!
[ 367.279650] [drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)!

Ubuntu got stuck (I re-booted without dropping to shell), only mouse movement worked. It was a low memory condition and an external display was connected. The system setup was 15.10 Ubuntu 4.2.0-42-generic #49-Ubuntu SMP using NUC5i7RYH.

Revision history for this message
Tomas Van Verrewegen (tomasvanverrewegen) wrote :

"[Bug 1488719] Re: dmesg shows "[drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)!""
David Valdivieso doc

Revision history for this message
Tomas Van Verrewegen (tomasvanverrewegen) wrote : RE

Win yesterday $15044
[Bug 1488719] Re: dmesg shows "[drm:gen8_irq_handler [i915]] ERROR The master control interrupt lied (SDE)!"

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.