← Back to team overview

kernel-packages team mailing list archive

[Bug 1503541] Re: kern.log flooded with "[drm:gen8_irq_handler [i915_bpo]] *ERROR* The master control interrupt lied (SDE)!"


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:

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:

Please note, an error to install the kernel does not fit the criteria of

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

** Changed in: linux (Ubuntu)
       Status: Confirmed => Incomplete

You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.

  kern.log flooded with "[drm:gen8_irq_handler [i915_bpo]] *ERROR* The
  master control interrupt lied (SDE)!"

Status in linux package in Ubuntu:

Bug description:
  On an intel i5 toshiba laptop on vivid. Upgraded to the
  3.19.0-30-generic kernel and started seeing this. Additionally, bootup
  was slow.

  kern.log/dmesg is flooded with this output

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

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.19.0-30-generic 3.19.0-30.34
  ProcVersionSignature: Ubuntu 3.19.0-30.34-generic 3.19.8-ckt6
  Uname: Linux 3.19.0-30-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.5
  Architecture: amd64
   /dev/snd/controlC0:  wolsen     2493 F.... pulseaudio
   /dev/snd/controlC1:  wolsen     2493 F.... pulseaudio
  CurrentDesktop: Unity
  Date: Tue Oct  6 22:30:20 2015
  HibernationDevice: RESUME=UUID=096b9e95-621b-4cc7-a10c-250149e1b48b
  InstallationDate: Installed on 2015-07-15 (83 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: TOSHIBA Satellite E45-B
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-30-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro noprompt quiet splash
   linux-restricted-modules-3.19.0-30-generic N/A
   linux-backports-modules-3.19.0-30-generic  N/A
   linux-firmware                             1.143.3
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/12/2015
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.10
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: CA10CU
  dmi.board.vendor: TOSHIBA
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis ManuFacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: dmi:bvnINSYDECorp.:bvr1.10:bd01/12/2015:svnTOSHIBA:pnSatelliteE45-B:pvrPSPNAU-001002:rvnTOSHIBA:rnCA10CU:rvr2.0:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: Satellite E45-B
  dmi.product.version: PSPNAU-001002
  dmi.sys.vendor: TOSHIBA

To manage notifications about this bug go to: