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

[Yuri Ribeiro Sucupira]

Device: notebook Dell Inspiron 5548

Operating system: 64-bit XUbuntu Linux 14.04 LTS

Processor: Intel Core i7-5500U

Kernel: 3.19.0-33-generic #38~14.04.1-Ubuntu SMP x86_64

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: my notebook's operating system is switching to runlevel 0 (power off) randomly, subtly and thus unexpectedly. And if I 'cat /var/log/kern.log |grep -i i915' I get a lot of "[drm:gen8_irq_handler [i915_bpo]] *ERROR* The master control interrupt lied (SDE)!" messages. I'm under the impression that either the kernel or the kernel module "i915_bpo" is buggy.

My notebook's problem can't be related to overheating, because it's a brand-new notebook (less than 1 month old) and I've already monitored its temperature parameters: nothing abnormal is happening. Also, I'm using a cooling laptop base/pad.

Other kernels I've tested, with which the same issue happens:
- 3.19.0-18-generic (kernel module: i915_bpo)
- 3.19.0-23-generic (kernel module: i915_bpo)
- 3.19.0-28-generic (kernel module: i915_bpo)
- 4.2.0-18-generic (kernel module: i915)

Temporary workaround: 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"

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.19.0-33-generic 3.19.0-33.38~14.04.1
ProcVersionSignature: Ubuntu 3.19.0-33.38~14.04.1-generic 3.19.8-ckt7
Uname: Linux 3.19.0-33-generic x86_64
NonfreeKernelModules: wl fglrx
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: amd64
CurrentDesktop: XFCE
Date: Wed Nov 25 23:44:39 2015
InstallationDate: Installed on 2015-11-03 (22 days ago)
InstallationMedia: Xubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
SourcePackage: linux-lts-vivid
UpgradeStatus: No upgrade log present (probably fresh install)
---
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: yuriyrs 2832 F.... pulseaudio
 /dev/snd/controlC1: yuriyrs 2832 F.... pulseaudio
CurrentDesktop: XFCE
DistroRelease: Ubuntu 14.04
HibernationDevice: RESUME=UUID=a08f36f9-0611-4894-9da9-8b1dcc960a86
InstallationDate: Installed on 2015-11-03 (24 days ago)
InstallationMedia: Xubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
MachineType: Dell Inc. Inspiron 5548
NonfreeKernelModules: fglrx wl
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-33-generic.efi.signed root=UUID=4f05c2b3-c971-4bf8-bcb6-a76d60b68e45 ro quiet splash video.use_native_backlight=1 intremap=no_x2apic_optout vt.handoff=7
ProcVersionSignature: Ubuntu 3.19.0-33.38~14.04.1-generic 3.19.8-ckt7
RelatedPackageVersions:
 linux-restricted-modules-3.19.0-33-generic N/A
 linux-backports-modules-3.19.0-33-generic N/A
 linux-firmware 1.127.18
Tags: trusty
Uname: Linux 3.19.0-33-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom dialout dip fax floppy fuse lpadmin netdev plugdev sambashare scanner sudo tape video
_MarkForUpload: True
dmi.bios.date: 10/12/2015
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A06
dmi.board.name: 0YDTG3
dmi.board.vendor: Dell Inc.
dmi.board.version: A02
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: A06
dmi.modalias: dmi:bvnDellInc.:bvrA06:bd10/12/2015:svnDellInc.:pnInspiron5548:pvrA06:rvnDellInc.:rn0YDTG3:rvrA02:cvnDellInc.:ct8:cvrA06:
dmi.product.name: Inspiron 5548
dmi.product.version: A06
dmi.sys.vendor: Dell Inc.

[Yuri Ribeiro Sucupira (yuri-sucupira)]

Recent 'dmesg' showing more detailed system info plus the error messages.

[Yuri Ribeiro Sucupira (yuri-sucupira)]

Other filed bugs reporting the same issue in other kernels:

1) Ubuntu 3.19.0-26.28-generic 3.19.8-ckt4 x86_64 + "i915" kernel module:

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

2) Ubuntu 3.19.0-30.34-generic 3.19.8-ckt6 x86_64 + "i915_bpo" kernel module:

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

[penalvch (penalvch)]

Yuri Ribeiro Sucupira, thank you for reporting this and helping make Ubuntu better.

Please execute the following command only once, as it will automatically gather debugging information, in a terminal:
apport-collect 1520040

[Yuri Ribeiro Sucupira (yuri-sucupira)]

apport information

[Yuri Ribeiro Sucupira (yuri-sucupira)]

apport information

[Yuri Ribeiro Sucupira (yuri-sucupira)]

apport information

[Yuri Ribeiro Sucupira (yuri-sucupira)]

apport information

[Yuri Ribeiro Sucupira (yuri-sucupira)]

apport information

[Yuri Ribeiro Sucupira (yuri-sucupira)]

apport information

[Yuri Ribeiro Sucupira (yuri-sucupira)]

apport information

[Yuri Ribeiro Sucupira (yuri-sucupira)]

apport information

[Yuri Ribeiro Sucupira (yuri-sucupira)]

apport information

[Yuri Ribeiro Sucupira (yuri-sucupira)]

apport information

[Yuri Ribeiro Sucupira (yuri-sucupira)]

apport information

[Yuri Ribeiro Sucupira (yuri-sucupira)]

apport information

[Yuri Ribeiro Sucupira (yuri-sucupira)]

apport information

[Yuri Ribeiro Sucupira (yuri-sucupira)]

apport information

[Yuri Ribeiro Sucupira (yuri-sucupira)]

apport information

[Yuri Ribeiro Sucupira (yuri-sucupira)]

apport information

[Yuri Ribeiro Sucupira (yuri-sucupira)]

Thank you. I've just run the apport-collect app as instructed.

Note: until Nov 27 02:32:01 AM UTC-2 (my local time, equivalent to 04:32:01 AM UTC) I was running kernel 3.19.0-33-generic as my default O.S. kernel, but then my notebook subtly powered off once more, thus causing me to decide to boot with kernel 3.13.0-36-generic by default. However, before running 'apport-collect 1520040' I booted the machine with kernel 3.19.0-33-generic again. Please let me know if it's interesting that I keep my system running only kernel 3.19.0-33-generic for a while, in order to further generate useful logs.

[penalvch (penalvch)]

Yuri Ribeiro Sucupira, could you please test the latest upstream kernel available from the very top line at the top of the page from http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D (the release names are irrelevant for testing, and please do not test the daily folder)? Install instructions are available at https://wiki.ubuntu.com/Kernel/MainlineBuilds . This will allow additional upstream developers to examine the issue.

If the latest kernel did not allow you to test to the issue (ex. you couldn't boot into the OS) please make a comment in your report about this, and continue to test the next most recent kernel version until you can test to the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this issue is fixed in the mainline kernel, please add the following tags by clicking on the yellow circle with a black pencil icon, next to the word Tags, located at the bottom of the report description:
kernel-fixed-upstream
kernel-fixed-upstream-X.Y-rcZ

Where X, and Y are the first two numbers of the kernel version, and Z is the release candidate number if it exists.

If the mainline kernel does not fix the issue, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-X.Y-rcZ

Please note, an error to install the kernel does not fit the criteria of kernel-bug-exists-upstream.

Once testing of the latest upstream kernel is complete, please mark this report's Status as Confirmed. Please let us know your results.

Thank you for your understanding.

[Yuri Ribeiro Sucupira (yuri-sucupira)]

HI. Today I accessed http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D but the very top line at the top of the page was a link to http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4-rc2-wily/, which doesn't have kernel DEB packages (except for linux-headers-4.4.0-040400rc2_4.4.0-040400rc2.201511251301_all.deb, but this is only the kernel headers, I couldn't find any kernel image). Thus I proceeded to http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel-next/ where the most recent folder with available DEB packages currently is http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel-next/2015-11-21-wily/

From http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel-next/2015-11-21-wily/ I downloaded and installed the following packages:

 linux-image-4.3.0-997-generic_4.3.0-997.201511202100_amd64.deb
 linux-headers-4.3.0-997_4.3.0-997.201511202100_all.deb
 linux-headers-4.3.0-997-generic_4.3.0-997.201511202100_amd64.deb

I was able to boot this kernel. Here's the result of some commands:

'uname -a':

 Linux yurix 4.3.0-997-generic #201511202100 SMP Sat Nov 21 02:02:46 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

'dmesg |grep -i i915':

 [ 1.175639] [drm] Initialized i915 1.6.0 20151120 for 0000:00:02.0 on minor 0
 [ 2.343450] i915 0000:00:02.0: fb0: inteldrmfb frame buffer device
 [ 13.974419] snd_hda_intel 0000:00:03.0: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915])
 (most recent event in dmesg was rcreated @ [ 1282.427420])

'dmesg |grep -i amd':

 [ 0.000000] AMD AuthenticAMD
 [ 0.000000] RAMDISK: [mem 0x34978000-0x364b3fff]
 [ 1.143551] [drm] amdgpu kernel modesetting enabled.
 [ 1.146516] AMD IOMMUv2 driver by Joerg Roedel <email address hidden>
 [ 1.146519] AMD IOMMUv2 functionality not available on this system
 [ 1.151854] amdgpu 0000:04:00.0: enabling device (0100 -> 0103)
 [ 1.224583] amdgpu 0000:04:00.0: Direct firmware load for amdgpu/topaz_mc.bin failed with error -2
 [ 1.224584] mc: Failed to load firmware "amdgpu/topaz_mc.bin"
 [ 1.224604] [drm:gmc_v8_0_sw_init [amdgpu]] *ERROR* Failed to load mc firmware!
 [ 1.224606] amdgpu 0000:04:00.0: Fatal error during GPU init
 [ 1.224607] [drm] amdgpu: finishing device.
 [ 1.224944] amdgpu: probe of 0000:04:00.0 failed with error -2

I noticed that 'fglrx_updates.ko' (which seems to be the AMD GPU driver) probably is a proprietary driver and thus wasn't loaded by the kernel (I noticed some dkms error messages related to it, during kernel installation, probably because of restrictions at the driver's dkms.conf file), which caused kernel '4.3.0-997-generic' to try to load /lib/modules/4.3.0-997-generic/kernel/drivers/gpu/drm/amd/amdgpu/amdgpu.ko. Because 'amdgpu.ko' wasn't loaded either, I was unable to run the 'AMD Catalyst Control Center' (shell command: amdcccle). But the kernel did detect the AMD GPU:

'aticonfig --list-adapters':
 * 0. 04:00.0 AMD Radeon R7 M260

 * - Default adapter (managed by /lib/modules/4.3.0-997-generic/kernel/drivers/gpu/drm/i915/i915.ko)

'lspci |grep -i amd':

04:00.0 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Topaz XT [Radeon R7 M260]

'i915.ko' was loaded and 'amdgpu.ko' depends on i...

[Yuri Ribeiro Sucupira (yuri-sucupira)]

I'm not 100% sure if "Confirmed" refers to the latest / upstream kernel I'm testing (4.3.0-997-generic) or to the one in which I detected the bug in (kernel 3.19.0-33-generic). But I'm assuming that it refers to '4.3.0-997-generic', thus I marked this bug as "Confirmed" (although it seems to be fixed in the last upstream kernel).

I just would like to test this upstream kernel it with both 'fglrx_updates' and 'i915'/'i915_bpo' simultaneously loaded. I'm under the impression that maybe there's an IRQ conflict between the default GPU (handled by Broadwell module i915*) and the AMD GPU (handled by AMD module fglrx_updates).

[penalvch (penalvch)]

Yuri Ribeiro Sucupira, the latest kernel available is 4.4-rc2+cod1 (not 4.3.x).

[Yuri Ribeiro Sucupira (yuri-sucupira)]

Okay, I've just (~21:13 UTC) installed kernel "4.4-rc2+cod1".

Packages installed:

 linux-image-4.4.0-040400rc2-generic_4.4.0-040400rc2.201511231054_amd64.deb
 linux-headers-4.4.0-040400rc2_4.4.0-040400rc2.201511231054_all.deb
 linux-headers-4.4.0-040400rc2-generic_4.4.0-040400rc2.201511231054_amd64.deb

"uname -a":

 Linux yurix 4.4.0-040400rc2-generic #201511231054 SMP Mon Nov 23 10:56:43 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

"dmesg |grep -i i915":
 [ 1.240521] [drm] Initialized i915 1.6.0 20151010 for 0000:00:02.0 on minor 0
 [ 2.461518] i915 0000:00:02.0: fb0: inteldrmfb frame buffer device
 [ 13.662232] snd_hda_intel 0000:00:03.0: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915])

"dmesg |grep -i amd":
 [ 0.000000] AMD AuthenticAMD
 [ 0.000000] RAMDISK: [mem 0x3448c000-0x3623dfff]
 [ 1.211790] [drm] amdgpu kernel modesetting enabled.
 [ 1.214823] AMD IOMMUv2 driver by Joerg Roedel <email address hidden>
 [ 1.214825] AMD IOMMUv2 functionality not available on this system

Last lines of "cat /var/log/kern.log |grep -i lied":
 Nov 29 11:30:15 yurix kernel: [ 23.887712] [drm:gen8_irq_handler [i915_bpo]] *ERROR* The master control interrupt lied (SDE)!
 Nov 29 11:30:15 yurix kernel: [ 23.887880] [drm:gen8_irq_handler [i915_bpo]] *ERROR* The master control interrupt lied (SDE)!
 Nov 29 11:30:15 yurix kernel: [ 23.888368] [drm:gen8_irq_handler [i915_bpo]] *ERROR* The master control interrupt lied (SDE)!
 Nov 29 11:30:15 yurix kernel: [ 23.888536] [drm:gen8_irq_handler [i915_bpo]] *ERROR* The master control interrupt lied (SDE)!
(so far no IRQ-related issues after I booted the system with an upstream kernel)

"lsmod |grep -i i915":
 i915 --- 1204224 --- 5
 i2c_algo_bit --- 16384 --- 2 --- i915,amdgpu
 drm_kms_helper --- 135168 --- 2 --- i915,amdgpu
 drm --- 360448 --- 8 --- ttm,i915,drm_kms_helper,amdgpu
 video --- 40960 --- 3 --- i915,dell_wmi,dell_laptop

"aticonfig --list-adapters":

 * 0. 04:00.0 AMD Radeon R7 M260

 * - Default adapter

"amdcccle" (AMD Catalyst Control Center): opens a window with an error message in brazilian portuguese. In english, the message translates to "There was a problem while attempting to start Catalyst Control Center Linux Edition. It may have been caused by the following:

 No AMD graphics driver installed, or AMD graphics driver not working properly.

 Install the proper AMD driver to your AMD hardware, or configure it with 'aticonfig'."

Well, this pretty much confirms to me that "fglrx_updates" is definitely a proprietary AMD GPU driver and thus doesn't work with these kernels, as explained in https://wiki.ubuntu.com/Kernel/MainlineBuilds

I will keep this kernel running for the next hours and report back if any message like "[drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)!" comes up in "dmesg".

[Yuri Ribeiro Sucupira (yuri-sucupira)]

Well, it's been ~24 hours since I started using kernel"4.4-rc2+cod1".

My notebook was kept "on" for over 16 of these 24 hours: 8h yesterday + 8h today. So far, no subtle poweroff happened. I restarted the system a couple of times, today and yesterday, and I also powered off the notebook. No issues detected.

Here's the current output for 'dmesg |grep -i i915' (the notebook's been on for the last 8 hours):
 [ 1.246344] [drm] Initialized i915 1.6.0 20151010 for 0000:00:02.0 on minor 0
 [ 2.431514] i915 0000:00:02.0: fb0: inteldrmfb frame buffer device
 [ 9.782202] snd_hda_intel 0000:00:03.0: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915])

[penalvch (penalvch)]

Yuri Ribeiro Sucupira, the next step is to fully reverse commit bisect from kernel 3.19 to 4.4-rc2 in order to identify the last bad commit, followed immediately by the first good one. Once this commit has been identified, then it may be reviewed as a candidate for backporting into your release. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection#How_do_I_reverse_bisect_the_upstream_kernel.3F ?

Please note, finding adjacent kernel versions is not fully commit bisecting.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

[Yuri Ribeiro Sucupira (yuri-sucupira)]

Wow, that seems a lot of work. I've never did it before in my life, but ok, let's see if I can do it.

I'll need some help here, though, 'coz I'm not 100% sure if the kernel list I created is correct. Could you please confirm this to me?

If I understood the instructions correctly, according with "ProcVersionSignature: Ubuntu 3.19.0-33.38~14.04.1-generic 3.19.8-ckt7" and "http://people.canonical.com/~kernel/info/kernel-version-map.html" the mainline kernel version for "3.19.0-33-generic" (which shipped with my notebook) is kernel "3.19.8-ckt7", hence the botton of the kernel list must be "v3.19.8-ckt7-vivid".

Also, because the bug was fixed in upstream kernel "v4.4-rc2+cod1-wily", it has to be on the top of the list, thus I am assuming that the kernel list for reverse commit bisect has to be this one:

v4.4-rc2+cod1-wily
v4.4-rc1-wily
v4.4-rc1+cod1-wily
v4.3-wily
v4.3-unstable
v4.3-rc7-unstable
v4.3-rc6-unstable
v4.3-rc5-unstable
v4.3-rc4-unstable
v4.3-rc3-unstable
v4.3-rc2-unstable
v4.3-rc1-unstable
v4.2.6-wily
v4.2.5-wily
v4.2.4-wily
v4.2.4-unstable
v4.2.3-unstable
v4.2.2-unstable
v4.2.1-unstable
v4.2-wily
v4.2-unstable
v4.2-rc8-unstable
v4.2-rc7-unstable
v4.2-rc6-unstable
v4.2-rc5-unstable
v4.2-rc4-unstable
v4.2-rc3-unstable
v4.2-rc2-unstable
v4.2-rc1-unstable
v4.1.13-wily
v4.1.12-wily
v4.1.11-wily
v4.1.11-unstable
v4.1.10-unstable
v4.1.9-unstable
v4.1.8-unstable
v4.1.7-unstable
v4.1.6-unstable
v4.1.5-unstable
v4.1.4-unstable
v4.1.3-unstable
v4.1.2-unstable
v4.1.1-unstable
v4.1-wily
v4.1-unstable
v4.1-rc8-unstable
v4.1-rc7-unstable
v4.1-rc6-unstable
v4.1-rc5-unstable
v4.1-rc4-unstable
v4.1-rc3-unstable
v4.1-rc2-vivid
v4.1-rc1-vivid
v4.0.9-wily
v4.0.8-wily
v4.0.7-wily
v4.0.6-wily
v4.0.5-wily
v4.0.4-wily
v4.0.3-wily
v4.0.2-wily
v4.0.1-wily
v4.0-vivid
v4.0-rc7-vivid
v4.0-rc6-vivid
v4.0-rc5-vivid
v4.0-rc4-vivid
v4.0-rc3-vivid
v4.0-rc2-vivid
v4.0-rc1-vivid
v3.19.8-vivid
v3.19.8-ckt10-vivid
v3.19.8-ckt9-vivid
v3.19.8-ckt8-vivid
v3.19.8-ckt7-vivid

Is my line of thought correct? Hence, is the above list correct?

As soon as I have a confirmation, I'll begin tracking down the commit that fixed the bug.

[Dara Adib (daradib)]

Marking as a duplicate of bug 1488719. If you believe this is a separate bug please change it back.

[penalvch (penalvch)]

Yuri Ribeiro Sucupira, the list is correct.

[Yuri Ribeiro Sucupira (yuri-sucupira)]

Hello.

Happy New Year everyone. :)

I have a doubt: I started testing these kernels and one of'em has the following message in dmesg (shell command was 'dmesg | grep -i i915'):

[ 11.547334] snd_hda_intel 0000:00:03.0: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915])

I understand that this isn't a bug (it seems that snd_hda_intel was bound to the audio component of i915 and that's it), but since I'm not 100% sure about what this message actually means it doesn't hurt to ask. Any consideration to be taken into account here?

Anyway, so far I've tested the following kernels and got the following outputs from 'dmesg |grep -i i915':

1) v4.1.6-unstable:

[ 1.195451] [drm] Initialized i915 1.6.0 20150327 for 0000:00:02.0 on minor 0
[ 2.311613] i915 0000:00:02.0: fb0: inteldrmfb frame buffer device
[ 2.311614] i915 0000:00:02.0: registered panic notifier
[ 8.605191] snd_hda_intel 0000:00:03.0: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915])

Because I am assuming that "snd_hda_intel 0000:00:03.0: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915])" isn't a bug, I considered that the bug reported in this ticket is fixed in kernel version "v4.1.6-unstable", hence I decided to test a previous (older) kernel version: v4.0.6-wily.

2) v4.0.6-wily:

[ 1.243539] [drm] Initialized i915 1.6.0 20150130 for 0000:00:02.0 on minor 0
[ 2.316114] i915 0000:00:02.0: fb0: inteldrmfb frame buffer device
[ 2.316115] i915 0000:00:02.0: registered panic notifier
[ 7.558016] snd_hda_intel 0000:00:03.0: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915])
[ 34.302400] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun

I considered that FIFO underrun a bug, hence I then decided to test a newer kernel version: v4.1-rc7-unstable.

3) v4.1-rc7-unstable:

[ 1.194191] [drm] Initialized i915 1.6.0 20150327 for 0000:00:02.0 on minor 0
[ 2.324857] i915 0000:00:02.0: fb0: inteldrmfb frame buffer device
[ 2.324858] i915 0000:00:02.0: registered panic notifier
[ 5.989937] snd_hda_intel 0000:00:03.0: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915])
[ 26.618897] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun

Same FIFO underrun issue, thus I then tested a newer kernel version: v4.1.2-unstable.

4) v4.1.2-unstable:

[ 1.188288] [drm] Initialized i915 1.6.0 20150327 for 0000:00:02.0 on minor 0
[ 2.296468] i915 0000:00:02.0: fb0: inteldrmfb frame buffer device
[ 2.296469] i915 0000:00:02.0: registered panic notifier
[ 7.502745] snd_hda_intel 0000:00:03.0: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915])

Assuming that "snd_hda_intel 0000:00:03.0: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915])" isn't a bug, I considered the bug fixed in kernel version v4.1.2-unstable, and thus decided to test a previous (older) kernel version: v4.1-wily.

5) v4.1-wily:

[ 1.176185] [drm] Initialized i915 1.6.0 20150327 for 0000:00:02.0 on minor 0
[ 2.292596] i915 0000:00:02.0: fb0: inteldrmfb frame buffer device
[ 2.292597] i915 0000:00:02.0: registered panic notifier
[ 11.547334] snd_h...

[Yuri Ribeiro Sucupira (yuri-sucupira)]

By the way: "dmesg |grep -i error" and "dmesg |grep -i lied" are two other shell commands I run, too. Where I mentioned above that I didn't find the bug I mean that besides running "dmesg |grep -i i915" I also ran the two previously mentioned commands and got no results (meaning that no "error" string neither "lied" string was found).

[Johan De Meersman (vegivamp+launchpad)]

Having similar problem with kernel 3.19.0-32.37 and i915_bpo module - when docked and external (displayport) screen attached, X finds no screens with a usable configuration.

When the external screen is off or disconnected, startup works normally into single (laptop) screen config; when undocked and using on-board displayport connector dualscreen also works normally.

I have the same errors in dmesg, which did not occur on kernel 3.16.0-38.52. I've currently reverted back to that kernel as workaround.

[penalvch (penalvch)]

Johan De Meersman, it will help immensely if you filed a new report with the Ubuntu repository kernel (not mainline/upstream) via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.

For more on why this is helpful, please see https://wiki.ubuntu.com/ReportingBugs.

[P (p92)]

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

[blabber (blabber-m)]

Just wanted to add that this message no longer appears on machines running the 4.4.0 kernel from Xenial, whereas it still appeared in the latest 4.2.0 kernel on wiley machines.