Bug #1503541 “kern.log flooded with “[drm:gen8_irq_handler [i915...” : Bugs : linux package : Ubuntu

Revision history for this message

Billy Olsen (billy-olsen) wrote on 2015-10-07:

#1

AlsaInfo.txt Edit (35.3 KiB, text/plain; charset="utf-8")
CRDA.txt Edit (219 bytes, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (77.8 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (2.3 KiB, text/plain; charset="utf-8")
IwConfig.txt Edit (649 bytes, text/plain; charset="utf-8")
JournalErrors.txt Edit (29.4 KiB, text/plain; charset="utf-8")
Lspci.txt Edit (10.5 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (362 bytes, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (4.1 KiB, text/plain; charset="utf-8")
ProcEnviron.txt Edit (103 bytes, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (2.7 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (6.9 KiB, text/plain; charset="utf-8")
PulseList.txt Edit (23.2 KiB, text/plain; charset="utf-8")
RfKill.txt Edit (112 bytes, text/plain; charset="utf-8")
UdevDb.txt Edit (160.0 KiB, text/plain; charset="utf-8")
WifiSyslog.txt Edit (114.3 KiB, text/plain; charset="utf-8")

Revision history for this message

Billy Olsen (billy-olsen) wrote on 2015-10-07:

#2

kern.log in case its needed Edit (832.1 KiB, text/plain)

Revision history for this message

Billy Olsen (billy-olsen) wrote on 2015-10-07:

#3

Hmm looks like this was showing up on Oct 3 in the kern.log.1 but I didn't upgrade to the 3.19.0-30 kernel until today. So it must have existed previously (though it seems much more readily apparent now).

Revision history for this message

Brad Figg (brad-figg) wrote on 2015-10-07: Status changed to Confirmed

#4

This change was made by a bot.

Changed in linux (Ubuntu):
status:	New → Confirmed

penalvch (penalvch) on 2015-10-12

tags:

added: latest-bios-1.10

Revision history for this message

penalvch (penalvch) wrote on 2015-10-13:

#5

Billy Olsen, thank you for reporting this and helping make Ubuntu better. 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, Y, and Z are numbers corresponding to the kernel version.

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.

Changed in linux (Ubuntu):
importance:	Undecided → Medium
status:	Confirmed → Incomplete

Revision history for this message

Yuri Ribeiro Sucupira (yuri-sucupira) wrote on 2015-11-24:

#6

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

Device: notebook Dell Inspiron 5548

Operating system: 64-bit XUbuntu Linux 14.04

Processor: Intel Core i7-5500U

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

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

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) cause subtle system shutdown (halt / poweroff) in my notebook.

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

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

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

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