kernel-packages team mailing list archive

Thread
Date
[Bug 1488719] Re: dmesg shows "[drm:gen8_irq_handler [i915]] ERROR The master control interrupt lied (SDE)!"

To: kernel-packages@xxxxxxxxxxxxxxxxxxx
From: Bug Watch Updater <1488719@xxxxxxxxxxxxxxxxxx>
Date: Mon, 31 Aug 2015 04:43:09 -0000
Reply-to: Bug 1488719 <1488719@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx
Launchpad has imported 14 comments from the remote bug at
https://bugs.freedesktop.org/show_bug.cgi?id=80896.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.

------------------------------------------------------------------------
On 2014-07-04T06:45:35+00:00 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

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1488719/comments/0

------------------------------------------------------------------------
On 2014-07-04T12:09:10+00:00 Paulo Zanoni wrote:

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

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1488719/comments/1

------------------------------------------------------------------------
On 2014-07-04T15:43:29+00:00 Damien Lespiau wrote:

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

commit 38cc46d73ed99dd7002f1406002e52d7975d16cc
Author: Oscar Mateo <oscar.mateo@xxxxxxxxx>
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.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1488719/comments/2

------------------------------------------------------------------------
On 2014-07-14T01:40:02+00:00 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 <oscar.mateo@xxxxxxxxx>
> 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

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1488719/comments/3

------------------------------------------------------------------------
On 2014-08-11T18:32:37+00:00 Paulo Zanoni 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

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1488719/comments/4

------------------------------------------------------------------------
On 2014-08-11T18:37:42+00:00 Paulo Zanoni 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

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1488719/comments/5

------------------------------------------------------------------------
On 2014-08-12T08:30:06+00:00 Huax-lu wrote:

Created attachment 104474
dmesg(14bf99)

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

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1488719/comments/6

------------------------------------------------------------------------
On 2014-08-12T12:37:49+00:00 Paulo Zanoni 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.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1488719/comments/7

------------------------------------------------------------------------
On 2014-08-13T06:11:22+00:00 Jinxianx-guo wrote:

Verified on latest -nightly(723dbbfb6ce02b5662c0c4cac9be3bcdfbb11d35)

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

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1488719/comments/8

------------------------------------------------------------------------
On 2015-05-19T20:33:49+00:00 Dima Ryazanov wrote:

Created attachment 115902
dmesg

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

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1488719/comments/9

------------------------------------------------------------------------
On 2015-05-28T19:26:45+00:00 Tobias Gerschner wrote:

Created attachment 116126
dmesg output, post event

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1488719/comments/10

------------------------------------------------------------------------
On 2015-05-28T19:30:33+00:00 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.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1488719/comments/11

------------------------------------------------------------------------
On 2015-08-18T14:18:51+00:00 Jani-nikula wrote:

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

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1488719/comments/12

------------------------------------------------------------------------
On 2015-08-22T10:09:42+00:00 M. B. 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.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1488719/comments/13


** Changed in: linux
       Status: Unknown => Confirmed

** Changed in: linux
   Importance: Unknown => High

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
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
References

[Bug 1488719] [NEW] dmesg shows "[drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)!"
From: Alexander List, 2015-08-26
kernel-packages team mailing list archive

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

References

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