8086:2a02 [MSI MS-1637] Graphic driver crash playing youtube via Chrome

[QkiZ]

Sometimes, not every time when I'm playing some Youtube videos in Google Chrome Unity crashes. After checking in logs I noticed that video driver has crashed. Nothing helps only reboot.

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu4.1
Uname: Linux 3.17.1-031701-lowlatency i686
.tmp.unity.support.test.0:

ApportVersion: 2.14.7-0ubuntu8
Architecture: i386
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Tue Nov 18 19:40:19 2014
DistUpgraded: Fresh install
DistroCodename: utopic
DistroVariant: ubuntu
DkmsStatus:
 vboxhost, 4.3.18, 3.16.0-24-generic, i686: installed
 vboxhost, 4.3.18, 3.16.0-25-generic, i686: installed
 vboxhost, 4.3.18, 3.17.1-031701-lowlatency, i686: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) [8086:2a02] (rev 03) (prog-if 00 [VGA controller])
   Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:3ff3]
   Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:3ff3]
InstallationDate: Installed on 2014-10-31 (17 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release i386 (20141022.1)
MachineType: Micro-Star International MSI Notebook PR600
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.17.1-031701-lowlatency root=/dev/mapper/system-root ro rootflags=subvol=@ VERBOSE_INIT=yes splash crashkernel=384M-:128M vt.handoff=7
SourcePackage: xserver-xorg-video-intel
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/15/2008
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: A1637IMS V1.7
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: MS-1637
dmi.board.vendor: MSI
dmi.board.version: Ver 1.000
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 10
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA1637IMSV1.7:bd09/15/2008:svnMicro-StarInternational:pnMSINotebookPR600:pvrVer1.000:rvnMSI:rnMS-1637:rvrVer1.000:cvnToBeFilledByO.E.M.:ct10:cvrToBeFilledByO.E.M.:
dmi.product.name: MSI Notebook PR600
dmi.product.version: Ver 1.000
dmi.sys.vendor: Micro-Star International
version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1
version.libdrm2: libdrm2 2.4.56-1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3
version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu4.1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2
xserver.bootTime: Tue Nov 18 19:37:51 2014
xserver.configfile: default
xserver.errors:

xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id 14661
 vendor SEC
xserver.version: 2:1.16.0-1ubuntu1

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Alex Kot (alexykot)]

I'm not sure about the logs, but I have exactly same symptoms, and while googling for solution I've came across a handful of other descriptions of a very similar problem at StackOverflow. Here are the links:

http://askubuntu.com/questions/534883/laptop-screen-goes-black-but-laptop-still-running
http://askubuntu.com/questions/486257/chromium-inspect-element-causes-black-screen
http://askubuntu.com/questions/543790/youtube-causes-black-screen
http://askubuntu.com/questions/547149/since-updating-to-ubuntu-14-04-chromium-causes-black-screen
http://askubuntu.com/questions/540910/ubuntu-screen-goes-black-after-loading-youtube
http://askubuntu.com/questions/541862/black-screen-when-playing-youtube-videos
http://askubuntu.com/questions/508796/ubuntu-14-04-chromium-causes-black-screen

Noticeably most of these questions were posted within last month, and this corresponds to my own observations - my problem started around three weeks ago. So this all seems to be related to a recent update.

Btw, I have Ubuntu 14.04 at Dell D630, Chromium 38.0.2125.111 and Unity.

[QkiZ (qkiz)]

On 14.04 after driver crash screen becomes black (its turning off). On 14.10 driver crash causes Unity restarting over and over (screen isn't turning off).

[QkiZ (qkiz)]

This is happening only on Google Chrome. On Firefox its ok.

[penalvch (penalvch)]

QkiZ, 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 (the release names are irrelevant for testing, and please do not test the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue.

If the test 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 bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested exactly shown as:
kernel-fixed-upstream-3.18-rc6

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description.

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

[QkiZ (qkiz)]

3.18.0-031800rc6-lowlatency problem still exists

[penalvch (penalvch)]

QkiZ, did this problem not occur in a release prior to Utopic?

[QkiZ (qkiz)]

Its occur in Trusty also but with different symptoms. In trusty after graphic driver crash screen was turning off.

[penalvch (penalvch)]

QkiZ, does this issue only occur after a resume from suspend/hibernate, or does it occur if you just came up from a reboot/shutdown?

[QkiZ (qkiz)]

It's occurs every time I power on computer.

[penalvch (penalvch)]

QkiZ, could you please test the latest mainline kernel 3.18-rc7 and advise to the results?

[QkiZ (qkiz)]

No change. After login to system this appears in logs:
Dec 1 19:10:13 digital-n0123 kernel: [ 249.446748] ------------[ cut here ]------------
Dec 1 19:10:13 digital-n0123 kernel: [ 249.446822] WARNING: CPU: 1 PID: 0 at /home/apw/COD/linux/drivers/gpu/drm/i915/intel_display.c:9918 intel_check_page_flip+0xac/0xc0 [i915]()
Dec 1 19:10:13 digital-n0123 kernel: [ 249.446826] Kicking stuck page flip: queued at 14708, now 14710
Dec 1 19:10:13 digital-n0123 kernel: [ 249.446829] Modules linked in: pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) ctr ccm uvcvideo videobuf2_vmalloc gpio_ich videobuf2_memops videobuf2_core v4l2_common arc4 videodev snd_hda_codec_hdmi rfcomm bnep media coretemp snd_hda_codec_realtek iwl3945 pcmcia joydev bluetooth iwlegacy snd_hda_codec_generic serio_raw mac80211 snd_hda_intel yenta_socket snd_hda_controller pcmcia_rsrc snd_hda_codec cfg80211 lpc_ich pcmcia_core snd_hwdep snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device snd_timer snd soundcore shpchp mac_hid parport_pc binfmt_misc ppdev lp parport btrfs xor raid6_pq xts gf128mul dm_crypt i915 i2c_algo_bit hid_a4tech drm_kms_helper ahci firewire_ohci sdhci_pci drm psmouse firewire_core libahci sdhci pata_acpi crc_itu_t r8169 mii usbhid hid video
Dec 1 19:10:13 digital-n0123 kernel: [ 249.446929] CPU: 1 PID: 0 Comm: swapper/1 Tainted: G OE 3.18.0-031800rc7-lowlatency #201411302035
Dec 1 19:10:13 digital-n0123 kernel: [ 249.446932] Hardware name: Micro-Star International MSI Notebook PR600/MS-1637, BIOS A1637IMS V1.7 09/15/2008
Dec 1 19:10:13 digital-n0123 kernel: [ 249.446936] 00000000 00000000 f2933e8c c16c7b31 f8ac7b1c f2933ebc c1061514 f8aca508
Dec 1 19:10:13 digital-n0123 kernel: [ 249.446947] f2933ee8 00000000 f8ac7b1c 000026be f8a803dc f8a803dc f5ceb000 f5cf2c00
Dec 1 19:10:13 digital-n0123 kernel: [ 249.446957] 00000001 f2933ed4 c10615d3 00000009 f2933ecc f8aca508 f2933ee8 f2933f04
Dec 1 19:10:13 digital-n0123 kernel: [ 249.446967] Call Trace:
Dec 1 19:10:13 digital-n0123 kernel: [ 249.446979] [<c16c7b31>] dump_stack+0x48/0x69
Dec 1 19:10:13 digital-n0123 kernel: [ 249.446988] [<c1061514>] warn_slowpath_common+0x84/0xa0
Dec 1 19:10:13 digital-n0123 kernel: [ 249.447036] [<f8a803dc>] ? intel_check_page_flip+0xac/0xc0 [i915]
Dec 1 19:10:13 digital-n0123 kernel: [ 249.447080] [<f8a803dc>] ? intel_check_page_flip+0xac/0xc0 [i915]
Dec 1 19:10:13 digital-n0123 kernel: [ 249.447086] [<c10615d3>] warn_slowpath_fmt+0x33/0x40
Dec 1 19:10:13 digital-n0123 kernel: [ 249.447132] [<f8a803dc>] intel_check_page_flip+0xac/0xc0 [i915]
Dec 1 19:10:13 digital-n0123 kernel: [ 249.447174] [<f8a4d90d>] i915_handle_vblank+0x4d/0x90 [i915]
Dec 1 19:10:13 digital-n0123 kernel: [ 249.447216] [<f8a53512>] i965_irq_handler+0x242/0x300 [i915]
Dec 1 19:10:13 digital-n0123 kernel: [ 249.447223] [<c10b0205>] handle_irq_event_percpu+0x35/0x200
Dec 1 19:10:13 digital-n0123 kernel: [ 249.447229] [<c10b040a>] handle_irq_event+0x3a/0x60
Dec 1 19:10:13 digital-n0123 kernel: [ 249.447235] [<c10b2b50>] ? handle_level_irq+0xd0/0xd0
Dec 1 19:10:13 digital-n0123 kernel: [ 249.447240] [<c10b2bbe>] han...

[penalvch (penalvch)]

QkiZ, the issue you are reporting is an upstream one. Could you please report this problem following the instructions at https://01.org/linuxgraphics/documentation/how-report-bugs ?

Please provide a direct URL to your bug report once you have made it so that it may be tracked.

Thank you for your understanding.