dmesg shows "[drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)!"
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_
There are two monitors connected to this box, one with mini-HDMI->HDMI, one with mini-DP->HDMI cable.
Maybe related:
https:/
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: linux-image-generic 3.19.0.26.25
ProcVersionSign
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=
SourcePackage: linux
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)
In freedesktop.org Bugzilla #80896, Jinxianx-guo (jinxianx-guo) wrote : | #8 |
In freedesktop.org Bugzilla #80896, Paulo Zanoni (pzanoni) wrote : | #9 |
Can you please bisect this? Which one is the bad commit?
In freedesktop.org Bugzilla #80896, Damien Lespiau (damien-lespiau) wrote : | #10 |
No need to bisect, the error message was introduced by Oscar in
commit 38cc46d73ed99dd
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.
In freedesktop.org Bugzilla #80896, Jinxianx-guo (jinxianx-guo) wrote : | #11 |
Created attachment 102730
dmesg
(In reply to comment #2)
> No need to bisect, the error message was introduced by Oscar in
>
> commit 38cc46d73ed99dd
> 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_
Output:
[root@x-bdw01 ~]# dmesg -r | egrep "<[1-3]>" |grep drm
<3>[ 2.753243] [drm:intel_
<3>[ 2.768133] [drm:intel_
<3>[ 2.780219] [drm:intel_
<3>[ 2.792092] [drm:intel_
<3>[ 2.804271] [drm:intel_
<3>[ 2.813306] [drm:intel_
<3>[ 2.831054] [drm:intel_
<3>[ 2.832254] [drm:intel_
In freedesktop.org Bugzilla #80896, Paulo Zanoni (pzanoni) wrote : | #12 |
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
In freedesktop.org Bugzilla #80896, Paulo Zanoni (pzanoni) wrote : | #13 |
(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
In freedesktop.org Bugzilla #80896, Huax-lu (huax-lu) wrote : | #14 |
Created attachment 104474
dmesg(14bf99)
It doesn't happen on latest -queued and -nightly kernel.I guess someone fixed it.
In freedesktop.org Bugzilla #80896, Paulo Zanoni (pzanoni) wrote : | #15 |
(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.
In freedesktop.org Bugzilla #80896, Jinxianx-guo (jinxianx-guo) wrote : | #16 |
Verified on latest -nightly(
[root@x-bdw01 ~]# dmesg -r | egrep "<[1-3]>" |grep drm
[root@x-bdw01 ~]#
In freedesktop.org Bugzilla #80896, Dima Ryazanov (dima-gmail) wrote : | #17 |
Created attachment 115902
dmesg
I just saw this error while running the 4.0.3 kernel (4.0.3-
In freedesktop.org Bugzilla #80896, Tobias Gerschner (tobig77) wrote : | #18 |
Created attachment 116126
dmesg output, post event
In freedesktop.org Bugzilla #80896, Tobias Gerschner (tobig77) wrote : | #19 |
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.
In freedesktop.org Bugzilla #80896, Jani-nikula (jani-nikula) wrote : | #20 |
*** Bug 90058 has been marked as a duplicate of this bug. ***
In freedesktop.org Bugzilla #80896, M. B. (tomboy64) wrote : | #21 |
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.
Alexander List (alexlist) wrote : | #1 |
- output of dmidecode Edit (23.3 KiB, text/plain)
- CurrentDmesg.txt Edit (62.6 KiB, text/plain; charset="utf-8")
- Dependencies.txt Edit (3.6 KiB, text/plain; charset="utf-8")
- HookError_source_linux_meta.txt Edit (727 bytes, text/plain; charset="utf-8")
- JournalErrors.txt Edit (58.4 KiB, text/plain; charset="utf-8")
- Lspci.txt Edit (9.1 KiB, text/plain; charset="utf-8")
- Lsusb.txt Edit (470 bytes, text/plain; charset="utf-8")
- ProcCpuinfo.txt Edit (4.1 KiB, text/plain; charset="utf-8")
- ProcEnviron.txt Edit (106 bytes, text/plain; charset="utf-8")
- ProcInterrupts.txt Edit (2.4 KiB, text/plain; charset="utf-8")
- ProcModules.txt Edit (5.4 KiB, text/plain; charset="utf-8")
- UdevDb.txt Edit (174.6 KiB, text/plain; charset="utf-8")
Alexander List (alexlist) wrote : | #2 |
Alexander List (alexlist) wrote : | #3 |
Brad Figg (brad-figg) wrote : Status changed to Confirmed | #4 |
This change was made by a bot.
Changed in linux (Ubuntu): | |
status: | New → Confirmed |
Changed in linux (Ubuntu): | |
importance: | Undecided → High |
Timo Aaltonen (tjaalton) wrote : | #5 |
Try mainline v4.2-rc8:
http://
Changed in linux (Ubuntu): | |
status: | Confirmed → Incomplete |
Alexander List (alexlist) wrote : | #6 |
Changed in linux (Ubuntu): | |
status: | Incomplete → Confirmed |
Alexander List (alexlist) wrote : | #7 |
Tried 4.2.0 from http://
Changed in linux: | |
importance: | Unknown → High |
status: | Unknown → Confirmed |
Peter Matulis (petermatulis) wrote : | #22 |
Tried 4.3-rc1 [1] on an Asus Zenbook trying to escape bug 1492632 and I am now getting this message.
[1]: http://
In freedesktop.org Bugzilla #92084, Wendy-wang (wendy-wang) wrote : | #57 |
Test Environment:
BDW-U
4.3.0-rc2_
Reproduce steps:
1.boot up system and grep error message in dmesg
2. Will see below ERROR message.
[ 1.260036] [drm:gen8_
Dmesg log attached.
In freedesktop.org Bugzilla #92084, Jani-nikula (jani-nikula) wrote : | #58 |
(In reply to wendy.wang from comment #0)
> Dmesg log attached.
There's no attachment.
In freedesktop.org Bugzilla #92084, Yex-tian (yex-tian) wrote : | #59 |
Created attachment 118408
dmesg info with drm.debug=0xe
In freedesktop.org Bugzilla #92084, Yex-tian (yex-tian) wrote : | #60 |
This bug also exists on the latest drm-intel-fixes and drm-intel-
In freedesktop.org Bugzilla #92084, Jani-nikula (jani-nikula) wrote : | #61 |
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."
In freedesktop.org Bugzilla #92084, Wendy-wang (wendy-wang) wrote : | #62 |
Good commit:
commit b42fa27abff5970
Author: Daniel Vetter <email address hidden>
Date: Wed Jul 8 21:48:11 2015 +0200
drm-
Bad commit:
commit 5b4a647fe39cf42
Author: Daniel Vetter <email address hidden>
Date: Thu Jul 9 21:57:35 2015 +0200
drm-
In freedesktop.org Bugzilla #92084, Mika-kuoppala (mika-kuoppala) wrote : | #63 |
On my bdw after this commit the messages started to appear:
commit aaf5ec2e51ab1d9
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.
In freedesktop.org Bugzilla #92084, Niccolò Belli (darkbasic) wrote : | #64 |
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.
cboettig (cboettig) wrote : | #23 |
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.
Stefan Langeland (morphuspam) wrote : | #24 |
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_
...
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://
In freedesktop.org Bugzilla #92084, Jani-nikula (jani-nikula) wrote : | #65 |
(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.
In freedesktop.org Bugzilla #92084, Jani-nikula (jani-nikula) wrote : | #66 |
Created attachment 118559
dmesg reproducing the problem on bdw
Curiously the errors are next to DP aux traffic.
In freedesktop.org Bugzilla #92084, Ville-syrjala-e (ville-syrjala-e) wrote : | #67 |
Random idea:
--- a/drivers/
+++ b/drivers/
@@ -2345,6 +2345,7 @@ static irqreturn_t gen8_irq_
u32 pch_iir = I915_READ(SDEIIR);
if (pch_iir) {
+ POSTING_
In freedesktop.org Bugzilla #92084, Jani-nikula (jani-nikula) wrote : | #68 |
(In reply to Ville Syrjala from comment #10)
> + POSTING_
Does not help.
In freedesktop.org Bugzilla #92084, Jani-nikula (jani-nikula) wrote : | #69 |
However this helps. We're missing something.
diff --git a/drivers/
index 76bd40e13391.
--- a/drivers/
+++ b/drivers/
@@ -1827,6 +1827,9 @@ static void ibx_hpd_
+ if (!hotplug_trigger)
+ return;
+
@@ -1934,8 +1937,7 @@ static void cpt_irq_
int pipe;
u32 hotplug_trigger = pch_iir & SDE_HOTPLUG_
- if (hotplug_trigger)
- ibx_hpd_
+ ibx_hpd_
if (pch_iir & SDE_AUDIO_
int port = ffs((pch_iir & SDE_AUDIO_
In freedesktop.org Bugzilla #92084, Ville-syrjala-e (ville-syrjala-e) wrote : | #70 |
(In reply to Jani Nikula from comment #12)
> However this helps. We're missing something.
>
> diff --git a/drivers/
> b/drivers/
> index 76bd40e13391.
> --- a/drivers/
> +++ b/drivers/
> @@ -1827,6 +1827,9 @@ static void ibx_hpd_
> *dev, u32 hotplug_trigger,
> dig_hotplug_reg = I915_READ(
> I915_WRITE(
Is the read alone enough, or do you need the write too?
>
> + if (!hotplug_trigger)
> + return;
> +
> intel_get_
> dig_hotplug_reg, hpd,
> pch_port_
> @@ -1934,8 +1937,7 @@ static void cpt_irq_
> u32 pch_iir)
> int pipe;
> u32 hotplug_trigger = pch_iir & SDE_HOTPLUG_
>
> - if (hotplug_trigger)
> - ibx_hpd_
> + ibx_hpd_
>
> if (pch_iir & SDE_AUDIO_
> int port = ffs((pch_iir & SDE_AUDIO_
In freedesktop.org Bugzilla #92084, Sonika-jindal (sonika-jindal) wrote : | #71 |
(In reply to Jani Nikula from comment #12)
> However this helps. We're missing something.
>
> diff --git a/drivers/
> b/drivers/
> index 76bd40e13391.
> --- a/drivers/
> +++ b/drivers/
> @@ -1827,6 +1827,9 @@ static void ibx_hpd_
> *dev, u32 hotplug_trigger,
> dig_hotplug_reg = I915_READ(
> I915_WRITE(
>
> + 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_
> intel_get_
> dig_hotplug_reg, hpd,
> pch_port_
> @@ -1934,8 +1937,7 @@ static void cpt_irq_
> u32 pch_iir)
> int pipe;
> u32 hotplug_trigger = pch_iir & SDE_HOTPLUG_
>
> - if (hotplug_trigger)
> - ibx_hpd_
> + ibx_hpd_
>
> if (pch_iir & SDE_AUDIO_
> int port = ffs((pch_iir & SDE_AUDIO_
In freedesktop.org Bugzilla #92084, Jani-nikula (jani-nikula) wrote : | #72 |
(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/
> > b/drivers/
> > index 76bd40e13391.
> > --- a/drivers/
> > +++ b/drivers/
> > @@ -1827,6 +1827,9 @@ static void ibx_hpd_
> > *dev, u32 hotplug_trigger,
> > dig_hotplug_reg = I915_READ(
> > I915_WRITE(
>
> 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_
> > dig_hotplug_reg, hpd,
> > pch_port_
> > @@ -1934,8 +1937,7 @@ static void cpt_irq_
> > u32 pch_iir)
> > int pipe;
> > u32 hotplug_trigger = pch_iir & SDE_HOTPLUG_
> >
> > - if (hotplug_trigger)
> > - ibx_hpd_
> > + ibx_hpd_
> >
> > if (pch_iir & SDE_AUDIO_
> > int port = ffs((pch_iir & SDE_AUDIO_
In freedesktop.org Bugzilla #92084, Ville-syrjala-e (ville-syrjala-e) wrote : | #73 |
(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/
> > > b/drivers/
> > > index 76bd40e13391.
> > > --- a/drivers/
> > > +++ b/drivers/
> > > @@ -1827,6 +1827,9 @@ static void ibx_hpd_
> > > *dev, u32 hotplug_trigger,
> > > dig_hotplug_reg = I915_READ(
> > > I915_WRITE(
> >
> > 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(
if (!hotplug_trigger)
dig_hotplug_reg &= ~(*_HOTPLUG_
I915_WRITE(
if (!hotplug_trigger)
return;
Stephen Thirlwall (l-sdt) wrote : | #25 |
I've just started getting this after updating to linux-image-
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_
[ 29.275763] [drm:gen8_
[ 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_
[ 29.363813] [drm:gen8_
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.
Billy Olsen (billy-olsen) wrote : | #26 |
Just saw this new after updating to the 3.19.0-30-generic kernel in vivid.
Alex (leo-tv) wrote : | #27 |
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)
In freedesktop.org Bugzilla #92084, Jani-nikula (jani-nikula) wrote : | #74 |
Also http://<email address hidden>
In freedesktop.org Bugzilla #80896, Kimc (kimc) wrote : | #29 |
Created attachment 118836
The master control interrupt lied
kernel output on a
Lenovo X1 Carbon (3rd gen) connected to a lenovo onelink pro dock
In freedesktop.org Bugzilla #80896, Kimc (kimc) wrote : | #30 |
(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'
In freedesktop.org Bugzilla #80896, Kimc (kimc) wrote : | #31 |
When 4k resolution is working, these error message is still present in kernel.log. Maybe resolution issue is unrelated to IRQ issue
In freedesktop.org Bugzilla #80896, Jani-nikula (jani-nikula) wrote : | #32 |
(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.
In freedesktop.org Bugzilla #92084, Jani-nikula (jani-nikula) wrote : | #75 |
*** Bug 92454 has been marked as a duplicate of this bug. ***
Brian Neltner (neltnerb) wrote : | #28 |
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.
stan383 (stan383) wrote : | #33 |
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.
rolfinator (seb2) wrote : | #34 |
Affects me too on HP 820 G2 with Xubuntu 15.04 on Kernel 3.19.0-31-generic.
In freedesktop.org Bugzilla #80896, Daniel-ffwll (daniel-ffwll) wrote : | #35 |
commit 97e5ed1111dcc53
Author: Daniel Vetter <email address hidden>
Date: Fri Oct 23 10:56:12 2015 +0200
drm/i915: shut up gen8+ SDE irq dmesg noise
In freedesktop.org Bugzilla #92084, Daniel-ffwll (daniel-ffwll) wrote : | #76 |
commit 97e5ed1111dcc53
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 |
Morten Clausen (morten-c) wrote : | #36 |
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.
In freedesktop.org Bugzilla #92084, Jani-nikula (jani-nikula) wrote : | #77 |
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/
index 6e0a5683bbdc.
--- a/drivers/
+++ b/drivers/
@@ -1825,7 +1825,21 @@ static void ibx_hpd_
u32 dig_hotplug_reg, pin_mask = 0, long_mask = 0;
dig_hotplug_reg = I915_READ(
+ if (!hotplug_trigger) {
+ u32 mask = PORTA_HOTPLUG_
+ PORTD_HOTPLUG_
+ PORTC_HOTPLUG_
+ PORTB_HOTPLUG_
+
+ if (dig_hotplug_reg & mask)
+ DRM_DEBUG_KMS("### %08x\n", dig_hotplug_reg & mask);
+
+ dig_hotplug_reg &= ~mask;
+ }
+
I915_
+ if (!hotplug_trigger)
+ return;
intel_
@@ -1840,8 +1854,7 @@ static void ibx_irq_
int pipe;
u32 hotplug_trigger = pch_iir & SDE_HOTPLUG_MASK;
- if (hotplug_trigger)
- ibx_hpd_
+ ibx_hpd_
if (pch_iir & SDE_AUDIO_
int port = ffs((pch_iir & SDE_AUDIO_
@@ -1934,8 +1947,7 @@ static void cpt_irq_
int pipe;
u32 hotplug_trigger = pch_iir & SDE_HOTPLUG_
- if (hotplug_trigger)
- ibx_hpd_
+ ibx_hpd_
if (pch_iir & SDE_AUDIO_
int port = ffs((pch_iir & SDE_AUDIO_
Puggan (from-ubuntu-b) wrote : | #37 |
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
Jeroko (jeroko) wrote : | #38 |
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_
[ 6.254993] [drm:drm_
[ 6.254995] [drm:drm_
[ 6.254996] [drm:drm_
[ 6.254997] [drm:drm_
[ 6.254999] [drm:drm_
[ 6.255000] [drm:drm_
[ 6.255002] [drm:drm_
[ 6.255003] [drm:drm_
[ 6.255008] [drm:drm_
[ 6.255010] [drm:drm_
[ 6.255011] [drm:intel_
[ 6.255018] [drm:edp_
[ 6.255024] [drm:edp_
[ 6.255476] [drm:drm_
[ 6.255480] [drm:drm_
[ 6.255483] [drm:drm_
[ 6.255487] [drm:drm_
[ 6.255497] [drm:drm_
[ 6.255498] [drm:drm_
[ 6.255500] [drm:intel_
[ 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_
[ 6.255817] [drm:gmbus_xfer] GMBUS [i915 gmbus dpb] NAK for addr: 0050 w(1)
[ 6.255819] [drm:drm_
[ 6.255821] [drm:drm_
[ 6.255824] [drm:drm_
[ 6.255826] [drm:drm_
[ 6.255828] [drm:intel_
[ 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_
[ 6.256149] [drm:gmbus_xfer] GMBUS [i915 gmbus dpb] NAK for addr: 0050 w(1)
[ 6.256150] [drm:drm_
[ 6.256152] [drm:drm_
[ 6.302099] init: alsa-restore main process (976) terminated with status 99
...
Tim Holy (holy-wustl) wrote : | #39 |
I'm still getting this on 4.2.0-17-generic with a Lenovo W550s. Moreover, [if you read the patch](http://
fcourchesne@gmail.com (fcourchesne) wrote : | #40 |
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_
Daniel Herrmann (daniel-herrmann1) wrote : | #41 |
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.
Tomer Cohen (tomerc) wrote : | #42 |
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.
darkhawk (info-sarazin) wrote : | #43 |
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_
[19707.594307] [drm:gen8_
[19707.595068] [drm:gen8_
Ronan Mooney (roomey) wrote : | #44 |
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)
Manu Cogolludo (makova) wrote : | #45 |
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_
ajoffre (alexandre-joffre) wrote : | #46 |
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-
Nov 19 09:12:12 ajoffre-
Nov 19 09:12:13 ajoffre-
Nov 19 09:12:13 ajoffre-
Nov 19 09:12:13 ajoffre-
Nov 19 09:12:13 ajoffre-
Nov 19 09:12:13 ajoffre-
Nov 19 09:12:13 ajoffre-
Nov 19 09:12:13 ajoffre-
Nov 19 09:12:13 ajoffre-
Nov 19 09:12:13 ajoffre-
Nov 19 09:12:13 ajoffre-
Nov 19 09:12:13 ajoffre-
Nov 19 09:12:13 ajoffre-PORT...
Paul (oldcoderexception) wrote : | #47 |
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_
(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)
Yuri Ribeiro Sucupira (yuri-sucupira) wrote : | #48 |
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_
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/
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/
In freedesktop.org Bugzilla #92084, Jani-nikula (jani-nikula) wrote : | #78 |
commit 6a39d7c986be4fd
Author: Jani Nikula <email address hidden>
Date: Wed Nov 25 16:47:22 2015 +0200
drm/i915: fix the SDE irq dmesg warnings properly
Tom Lime (0x6d3468) wrote : | #49 |
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_
|dock.
- device: lenovo t450s
- proc: i7-5600U
- OS: ubuntu 14.04.03
- kernel: 3.19.0-33-generic x86_64
- video:
*-display
bus info: pci@0000:00:02.0
width: 64 bits
clock: 33MHz
darkhawk (info-sarazin) wrote : | #50 |
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_
sometimes after a fresh boot inside dmesg.
Andreas Scherbaum (ads-launchpad) wrote : | #51 |
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.
zeine77 (mohamed-eyil) wrote : | #52 |
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_
[26255.194650] [drm:gen8_
[26255.202474] [drm:gen8_
[26255.203480] [drm:gen8_
[26255.210467] [drm:gen8_
[26255.211472] [drm:gen8_
Michel Weimerskirch (michel-weimerskirch) wrote : | #53 |
When connecting my Lenovo T450s to the dock, the screen gets black after logging in and I have the same error message:
[drm:gen8_
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.
Joakim Koed (vooze) wrote : | #54 |
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_
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?
In freedesktop.org Bugzilla #92084, Chris Wilson (ickle) wrote : | #79 |
Still present as of
commit 0035ecf934fae04
Author: Daniel Vetter <email address hidden>
Date: Mon Dec 14 10:41:10 2015 +0100
drm-
will look into the debug printk next time I have the box connected to a display.
Morten Clausen (morten-c) wrote : | #55 |
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 |
Morten Clausen (morten-c) wrote : | #56 |
@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-
Changed in linux: | |
importance: | Unknown → Medium |
status: | Unknown → Confirmed |
Joakim Koed (vooze) wrote : | #80 |
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.?
Joakim Koed (vooze) wrote : | #81 |
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 :)
In freedesktop.org Bugzilla #92084, Joakim Koed (vooze) wrote : | #82 |
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.
hitchhiker54 (hitchhiker54) wrote : | #83 |
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.
Matt (reg-launchpad-net) wrote : | #84 |
Also experiencing this with 14.04 dell XPS 9350 Intel(R) Core(TM) i7-5500U
Londé Ngosso (londe-ngosso) wrote : | #85 |
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
Carroarmato0 (carroarmato0) wrote : | #86 |
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.
ming (mctiew) wrote : | #87 |
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.
Manu Cogolludo (makova) wrote : | #88 |
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
uname -a
Linux Lucy 4.4.0-040400rc6
Joakim Koed (vooze) wrote : | #89 |
#88
Great!! Good to hear. Now we just have to wait to 4.4 stable and this and go away for good =)
Manu Cogolludo (makova) wrote : Re: [Bug 1488719] Re: dmesg shows "[drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)!" | #90 |
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:/
>
> Title:
> dmesg shows "[drm:gen8_
> 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_
> lied (SDE)!
>
> There are two monitors connected to this box, one with mini-
> HDMI->HDMI, one with mini-DP->HDMI cable.
>
> Maybe related:
>
> https:/
>
> ProblemType: Bug
> DistroRelease: Ubuntu 15.04
> Package: linux-image-generic 3.19.0.26.25
> ProcVersionSign
> 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=
> root=/dev/
> 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:/
>
--
Manu
Londé Ngosso (londe-ngosso) wrote : | #91 |
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
Joakim Koed (vooze) wrote : | #92 |
Just testet RC7 from mainline, and it seems to be gone here as well. No messages in /var/log/syslog.
Peter Bodrovics (bodrovics) wrote : | #93 |
Also tested 4.4.0 RC7 and error is gone.
Dell Latitude E5250 with Linux Mint 17.3, BIOS A10, Intel Core i5
Londé Ngosso (londe-ngosso) wrote : | #94 |
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
Arnau (arnaubcn) wrote : | #95 |
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_
<3>[ 5.006249] [drm:gen8_
<3>[ 22.784920] [drm:gen8_
<3>[ 22.785111] [drm:gen8_
<3>[ 22.785409] [drm:gen8_
<3>[ 22.785594] [drm:gen8_
<3>[ 22.785878] [drm:gen8_
<3>[ 22.786051] [drm:gen8_
<3>[ 22.786340] [drm:gen8_
<3>[ 22.786497] [drm:gen8_
<3>[ 22.786667] [drm:gen8_
<3>[ 22.786819] [drm:gen8_
<3>[ 22.786986] [drm:gen8_
<3>[ 22.787137] [drm:gen8_
<3>[ 22.787290] [drm:gen8_
<3>[ 22.787459] [drm:gen8_
<3>[ 22.787610] [drm:gen8_
<3>[ 22.787778] [drm:gen8_
<3>[ 22.787929] [drm:gen8_
<3>[ 22.788081] [drm:gen8_
<3>[ 22.788250] [drm:gen8_
<3>[ 22.788401] [drm:gen8_
<3>[ 22.788688] [drm:gen8_
<3>[ 22.788979] [drm:gen8_
<3>[ 22.789269] [drm:gen8_
<3>[ 22.789559] [drm:gen8_
<3>[ 22.789851] [drm:gen8_
<3>[ 22.790141] [drm:gen8_
<3>[ 22.790432] [drm:gen8_
<3>[ 22.790722] [drm:gen8_
<3>[ 22.790877] [drm:ge...
Jan Pfeifer (pfjan) wrote : | #96 |
Also on Dell XPS-13, Ubuntu 15.10, kernel 4.2.0-22.
X doesn't start here :(
Joakim Koed (vooze) wrote : | #97 |
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.
Falx (thomasdupont100) wrote : | #99 |
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.
Morten Clausen (morten-c) wrote : | #100 |
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.
Raniz (raniz-1) wrote : | #101 |
Happening here as well with 4.4.0 RC7
$ uname -r v
4.4.0-040400rc7
$ dmesg | egrep '(intel|i915)'
[ 0.149154] pci 0000:00:14.0: reg 0x10: [mem 0xe1220000-
[ 0.649005] [<ffffffff81f66
[ 0.649435] audit: type=2000 audit(145191513
[ 0.985552] intel_idle: MWAIT substates: 0x11142120
[ 0.985553] intel_idle: v0.4 model 0x3D
[ 0.985554] intel_idle: lapic_timer_
[ 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_
-- Repeated 44 times --
[ 2.752695] [drm] GMBUS [i915 gmbus dpb] timed out, falling back to bit banging on pin 5
[ 2.817096] [drm:gen8_
-- Repeated 56 times --
[ 2.851265] i915 0000:00:02.0: fb0: inteldrmfb frame buffer device
[ 2.902734] [drm:gen8_
-- Repeated 91 times --
[ 3.467690] snd_hda_intel 0000:00:03.0: bound 0000:00:02.0 (ops i915_audio_
[ 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_
-- Repeated 44 times --
[ 47.125136] [drm:intel_
[ 47.128273] [drm:intel_
[ 70.590927] [drm:gen8_
-- Repeated 98 times --
Joakim Koed (vooze) wrote : | #102 |
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 :)
ddalex (ddalex) wrote : | #103 |
Can confirm this bug on Macbook12,1 running 4,4rc7 and a single display on a miniDP connector.
Morten Clausen (morten-c) wrote : | #104 |
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.
Londé Ngosso (londe-ngosso) wrote : | #105 |
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
Falx (thomasdupont100) wrote : | #107 |
- dmesg log after boot Edit (58.3 KiB, text/plain)
Just tested 4.4.0-040400rc8
Still get the [drm:gen8_
See attached file for my dmesg output after login.
Sera (seraphim6x7) wrote : | #108 |
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.
In freedesktop.org Bugzilla #92084, Jani-nikula (jani-nikula) wrote : | #139 |
(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.
In freedesktop.org Bugzilla #92084, Jani-nikula (jani-nikula) wrote : | #140 |
commit 2dfb0b816d22437
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
In freedesktop.org Bugzilla #92084, Niccolò Belli (darkbasic) wrote : | #141 |
When did you shut up the messages for the first time? I always saw them in every RC, including latest 4.4-rc8.
In freedesktop.org Bugzilla #92084, Jani-nikula (jani-nikula) wrote : | #142 |
(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.
neufeind (neufeind) wrote : | #109 |
Found something here: https:/
It mentions a kernel-fix:
commit 2dfb0b816d22437
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
Gronor (tonut) wrote : | #110 |
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_
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/
[ 93.451073] ACPI Error: Method parse/execution failed [\_SB.PCI0.
[ 288.672984] ------------[ cut here ]------------
[ 288.673012] WARNING: CPU: 3 PID: 1278 at /build/
[ 288.673014] Unclaimed register detected before writing to register 0x44414
[ 288.673015] Modules linked in: rfcomm xt_addrtype xt_conntrack ipt_MASQUERADE nf_nat_
[ 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_
[ 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...
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
Gronor (tonut) wrote : | #112 |
So is it into 4.5 RC1?
Morten Clausen (morten-c) wrote : | #113 |
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_
at boot time now (related: https:/
[drm:gen8_
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.
Londé Ngosso (londe-ngosso) wrote : | #114 |
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
Manfred Mager (frediiii) wrote : | #115 |
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
Carroarmato0 (carroarmato0) wrote : | #116 |
I also just tried the 4.5.0-040500rc1
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
Nivus (nivus-ua) wrote : | #117 |
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.
Gronor (tonut) wrote : | #118 |
Kernel 4.5 RC1 did not fix it for me. It is even worse at times
Markus (chickenmarkus) wrote : | #119 |
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.
Raniz (raniz-1) wrote : | #120 |
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_
Londé Ngosso (londe-ngosso) wrote : | #121 |
I've got the same bug. It seems solved with kernel 4.5 RC3.
see https:/
Bernhard Schussek (bschussek) wrote : | #122 |
Same problem here on Lenovo T450s with kernel 4.2.0-27.
Jeffrey Walton (noloader) wrote : | #123 |
From Comment #48 (https:/
> 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/
> then add the 'nomodeset' option to "GRUB_CMDLINE_
> (e.g. GRUB_CMDLINE_
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://
darkhawk (info-sarazin) wrote : | #124 |
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_
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)
Jeffrey Walton (noloader) wrote : | #125 |
From Comment #124 (https:/
> ... 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://
Carroarmato0 (carroarmato0) wrote : | #126 |
A colleague of mine sent this link to Lenovo's support page: https:/
Says to update the VGA IC firmware.... but using a Windows tool... supposedly fixes the screen flickering on VGA
maddin (ich-martin-drees) wrote : | #127 |
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 :) ...
chefarov (chefarov) wrote : | #128 |
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/
and booting it
"error parsing PCC subspaces from PCCT"
boot hangs up again
chefarov (chefarov) wrote : | #129 |
Installing linux-firmware_
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...
Yuri Ribeiro Sucupira (yuri-sucupira) wrote : | #130 |
This is a mysterious bug affecting a LOT of machines. As I suggested at https:/
Try it out and see if it is of any help.
chefarov (chefarov) wrote : | #131 |
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
dusoft (dusoft-staznosti) wrote : | #132 |
Not solved for me with kernel 4.5.0-040500rc3
Still happens.
In freedesktop.org Bugzilla #92084, Yuri Ribeiro Sucupira (yuri-sucupira) wrote : | #143 |
Please see this bug report:
https:/
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/
Hence, this bug is far from "solved" and shutting up dmesg definitely won't solve it.
In freedesktop.org Bugzilla #92084, Chris Wilson (ickle) wrote : | #144 |
(In reply to Yuri from comment #28)
> Please see this bug report:
>
> https:/
>
> 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/
> 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.
Tessa (unit3) wrote : | #133 |
Seeing with the latest 16.04 desktop nightly, amd64, 2015 Macbook Pro.
dreh23 (johannes-amorosa-7) wrote : | #134 |
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.
Raniz (raniz-1) wrote : | #135 |
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.
Carroarmato0 (carroarmato0) wrote : | #136 |
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/
drm/
drm/i915/skl: Ensure HW is powered during DDB HW state readout
Will give it a go as soon as I can
Carroarmato0 (carroarmato0) wrote : | #137 |
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.
Carroarmato0 (carroarmato0) wrote : | #138 |
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
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 |
Gronor (tonut) wrote : | #145 |
So did 4.5.0 RC6 fixed it for you guys?
It still reproduces for me even with this kernel
dancer7162 (dancer7162) wrote : | #146 |
Yes it fixed it for me.
System is NUC5i7RYH using the HDMI port (using linux-image-
thank you guys
Carroarmato0 (carroarmato0) wrote : | #147 |
After some longer tests looks like this is still not 100% with RC6 :(
Raniz (raniz-1) wrote : | #148 |
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.
darkhawk (info-sarazin) wrote : | #149 |
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
darkhawk (info-sarazin) wrote : | #150 |
Ok, nothing new
[ 1510.565374] [drm:gen8_
thomas955 (thoehlig) wrote : | #151 |
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
The dmesg messag "[drm:gen8_
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/
[Di Mär 8 17:53:14 2016] Unclaimed register detected after reading register 0x223a0
modinfo i915
filename: /lib/modules/
license: GPL and additional rights
description: Intel Graphics
author: Intel Corporation
author: Tungsten Graphics, Inc.
firmware: i915/bxt_
firmware: i915/skl_
firmware: i915/skl_
srcversion: A8C37B25F49F03A
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-
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
Gronor (tonut) wrote : | #152 |
@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.
thomas955 (thoehlig) wrote : | #153 |
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.
Dr4K4n (stefan-dr4k4n) wrote : | #154 |
I'm having similar problems on my Dell XPS 13 9343 running 15.10 with 4.5.0-040500rc6
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
Please let me know when you need any more infos from me.
thomas955 (thoehlig) wrote : | #155 |
@Gronor Tested 1280x720 on all Displays, same problem.
Gronor (tonut) wrote : | #156 |
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.
Christian George (radu-j-deactivatedaccount-deactivatedaccount) wrote : | #157 |
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.
thomas955 (thoehlig) wrote : | #158 |
I think the flickering problem only occurs if you use two external monitors with e-port-dock.
Yuri Ribeiro Sucupira (yuri-sucupira) wrote : | #159 |
"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.
Morten Clausen (morten-c) wrote : | #160 |
- Syslog portion from plugging to dock until crash Edit (43.0 KiB, text/plain)
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.freedeskto
David Valdivieso (valdorvaldor) wrote : | #161 |
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
Manu Cogolludo (makova) wrote : | #162 |
Lenovo Think Pad X1 Carbon Intel® Core™ i7-5600U CPU @ 2.60GHz × 4
Kernel solved
uname -a
Linux 4.5.0-040500-
Gronor (tonut) wrote : | #163 |
@Manu, what exactly is fixed? I am running this kernel now and the display flicker issue is not gone
Gronor (tonut) wrote : | #164 |
We might as well close this report, nobody seems to care
Piotr (thisredoned) wrote : | #165 |
uname -a
Linux 4.5.0-040500rc7
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.
SAURABH KUMAR (saurabh-rajrappa7) wrote : | #166 |
I am facing same issue after once I force shutdown My OS(laptop). And, now I cannot logon.
Sigurd Kristensen (sigurd-kristensen) wrote : | #167 |
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/
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_
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...
xeno678g (e3-hvag-jl) wrote : | #168 |
On NUC NUC5i3RYB
(Lubuntu 15.10 amd64)
BIOS : RYBDWi35.
kernel 4.6.0-040600rc3
Finally fixed this for me (Yamaha RX-V475 hdmi handling was/is still buggy).
Ed Broadley (rebroad+ubuntu) wrote : | #169 |
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_
Ed Broadley (rebroad+ubuntu) wrote : | #170 |
Also getting this on: Linux UX303LNB 4.2.6-040206-
Ed Broadley (rebroad+ubuntu) wrote : | #171 |
According to http://
Gronor (tonut) wrote : | #172 |
Hey Ivan,
so with kernel 4.6.0-040600rc3
Gronor (tonut) wrote : | #173 |
Unfortunately 4.6.0-040600rc3
Ed Broadley (rebroad+ubuntu) wrote : | #174 |
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
Gronor (tonut) wrote : | #175 |
Ed, can you specify what is no longer happening?
zeine77 (mohamed-eyil) wrote : | #176 |
I have written the comment 52 above; those eroor messages seem to be gone with 16.04 release. I have no longer those errors.
Gronor (tonut) wrote : | #177 |
Error messages have been gone for a long time for me. Symptoms however, have not
Lauri Niskanen (lauri-niskanen-h) wrote : | #178 |
[ 35.769534] Bluetooth: RFCOMM socket layer initialized
[ 35.769539] Bluetooth: RFCOMM ver 1.11
[ 367.276773] [drm:gen8_
[ 367.277129] [drm:gen8_
[ 367.278570] [drm:gen8_
[ 367.278928] [drm:gen8_
[ 367.279650] [drm:gen8_
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.
Tomas Van Verrewegen (tomasvanverrewegen) wrote : | #179 |
"[Bug 1488719] Re: dmesg shows "[drm:gen8_
David Valdivieso doc
Tomas Van Verrewegen (tomasvanverrewegen) wrote : RE | #181 |
Win yesterday $15044
[Bug 1488719] Re: dmesg shows "[drm:gen8_
Created attachment 102239
dmesg
==System Environment== ------- ------- ----- daba19eec676b63 2faa523fc8
-------
Regression: Yes.
Good commit on -next-queued: b6fdd0f2b990006
Non-working platforms: BDW
==kernel== ------- ------- ----- drm-intel- nightly: eb638c7fabe97a9 df752aeb2f59a94 63ce4aed8e( fails) intel-nightly: 2014y-07m- 03d-14h- 50m-16s integration manifest drm-intel- next-queued: 5e59f7175f96550 ede91f58d267d2b 551cb6fbba( fails) drm-intel- fixes: 5549d25f642a7e6 cfb8744d0031a9d a404f696d6( works)
-------
origin/
drm-
origin/
drm/i915: Try harder to get FBC
origin/
drm/i915: Drop early VLV WA to fix Voltage not getting dropped to Vmin
==Bug detailed description== irq_handler] *ERROR* The master control interrupt lied (SDE)!" after boot.
dmesg error "<3>[ 1.954836] [drm:gen8_
Output: irq_handler] *ERROR* The master control interrupt lied (SDE)! irq_handler] *ERROR* The master control interrupt lied (SDE)! irq_handler] *ERROR* The master control interrupt lied (SDE)! irq_handler] *ERROR* The master control interrupt lied (SDE)!
[root@x-bdw01 ~]# dmesg -r | egrep "<[1-3]>" |grep drm
<3>[ 1.955683] [drm:gen8_
<3>[ 1.955848] [drm:gen8_
<3>[ 3.683649] [drm:gen8_
<3>[ 3.686870] [drm:gen8_
==Reproduce steps== ------- ------- -------
-------
1. boot
2. dmesg -r | egrep "<[1-3]>" |grep drm