Created attachment 93892 [details]
GPU crash dump
Judging from dmesg, I got a GPU hang and I'm expected to file a bug.
$ uname -a
Linux beevvy-n02 3.13.2-gentoo #1 SMP PREEMPT Sat Feb 8 19:19:27 CET 2014 x86_64 Intel(R) Core(TM) i3-2310M CPU @ 2.10GHz GenuineIntel GNU/Linux
Mesa version: 9.2.5
# dmesg|grep '\[drm\]'
[ 0.439376] [drm] Initialized drm 1.1.0 20060810
[ 0.440323] [drm] Memory usable by graphics device = 2048M
[ 0.476502] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[ 0.476611] [drm] Driver supports precise vblank timestamp query.
[ 0.500848] [drm] Wrong MCH_SSKPD value: 0x16040307
[ 0.500956] [drm] This can cause pipe underruns and display issues.
[ 0.501063] [drm] Please upgrade your BIOS to fix this.
[ 1.261192] [drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0
[ 1.963651] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off
[ 761.375446] [drm] stuck on render ring
[ 761.375447] [drm] stuck on blitter ring
[ 761.375449] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[ 761.375450] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[ 761.375450] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[ 761.375451] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[ 761.375452] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
Created attachment 93893 [details]
What was I doing: I just booted the machine, logged in (I'm using KDE 4.12.2, with KWin), run Firefox and browsed the web, nothing fancy, no WebGL. And then it happened.
*** This bug has been marked as a duplicate of bug 54226 ***