Description of problem:

The following was registered in logs on ASUS K52Jc laptop:

 [46339.646330] kernel BUG at drivers/gpu/drm/i915/i915_gem.c:1159!
 [46339.641049] Restarting tasks ... 
 [46339.648538] invalid opcode: 0000 [#1] SMP 
 [46339.650904] done.
 [46339.654998] Modules linked in: rpcsec_gss_krb5 nfsv4 dns_resolver nfs fscache fuse ip6t_REJECT nf_conntrack_ipv6 nf_defrag_ipv6 nf_conntrack_ipv4 nf_defrag_ipv4 ip6table_filter ip6_tables xt_conntrack nf_conntrack snd_hda_codec_hdmi snd_hda_codec_conexant uvcvideo videobuf2_vmalloc videobuf2_memops coretemp videobuf2_core iTCO_wdt iTCO_vendor_support videodev snd_hda_intel media snd_hda_codec arc4 snd_hwdep snd_seq snd_seq_device ath9k ath9k_common ath9k_hw snd_pcm ath microcode serio_raw mac80211 intel_ips snd_page_alloc snd_timer sdhci_pci snd sdhci lpc_ich mfd_core mmc_core soundcore cfg80211 jmb38x_ms jme mii memstick shpchp mei_me mei asus_laptop sparse_keymap rfkill input_polldev acpi_cpufreq nfsd auth_rpcgss nfs_acl lockd sunrpc i915 i2c_algo_bit drm_kms_helper drm i2c_core video
 [46339.661818] CPU: 0 PID: 17423 Comm: gnome-shell Not tainted 3.12.7-300.fc20.x86_64 #1
 [46339.663232] Hardware name: ASUSTeK Computer Inc.         K52Jc/K52Jc, BIOS K52Jc.206 03/29/2010
 [46339.665248] task: ffff8800a5066300 ti: ffff88009904e000 task.ti: ffff88009904e000
 [46339.667956] RIP: 0010:[<ffffffffa009de82>]  [<ffffffffa009de82>] i915_gem_set_domain_ioctl+0x232/0x240 [i915]
 [46339.670790] RSP: 0018:ffff88009904fd70  EFLAGS: 00010246
 [46339.673086] RAX: 0000000000000001 RBX: 0000000000000040 RCX: ffff88009904ffd8
 [46339.674780] RDX: ffff8800b6468000 RSI: ffff88012fed6400 RDI: ffff88012fed6440
 [46339.675034] video LNXVIDEO:02: Restoring backlight state
 [46339.678037] RBP: ffff88009904fdb8 R08: 000000000000440f R09: 000000000000e200
 [46339.679583] R10: ffffffffa00f6b00 R11: ffff8800370b2800 R12: ffff8800370b2800
 [46339.681346] R13: ffff8800990b5c00 R14: 0000000000000000 R15: 0000000000000040
 [46339.683231] FS:  00007f77f3e4da40(0000) GS:ffff880137c00000(0000) knlGS:0000000000000000
 [46339.685072] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
 [46339.686704] CR2: 000000000344a4bc CR3: 00000000ab44c000 CR4: 00000000000007f0
 [46339.688368] Stack:
 [46339.690032] PM: Syncing filesystems ... 
 [46339.690033]  ffff88009904fda8 ffffffff81078102 ffff88009904ff58 01ff88009904fe78
 [46339.694740]  ffff8800370b2800 ffff88012fed6400 fffffffffffffff2 ffff88009904fe18
 [46339.696503]  000000000000005f ffff88009904fec8 ffffffffa0020c32 ffff880000000001
 [46339.698380] Call Trace:
 [46339.700798]  [<ffffffff81078102>] ? dequeue_signal+0x82/0x160
 [46339.703051]  [<ffffffffa0020c32>] drm_ioctl+0x502/0x630 [drm]
 [46339.705534]  [<ffffffff81012428>] ? do_signal+0x48/0x5e0
 [46339.708034]  [<ffffffff81553517>] ? SYSC_recvfrom+0x127/0x160
 [46339.710445]  [<ffffffff811c11dd>] do_vfs_ioctl+0x2dd/0x4b0
 [46339.712568]  [<ffffffff811c1431>] SyS_ioctl+0x81/0xa0
 [46339.714483]  [<ffffffff81676969>] system_call_fastpath+0x16/0x1b
 [46339.716155] Code: 00 41 bf fe ff ff ff e9 fb fe ff ff 8b 82 a8 2c 00 00 41 bf fb ff ff ff 83 c0 01 b8 f5 ff ff ff 44 0f 45 f8 e9 c9 fe ff ff 0f 0b <0f> 0b 66 66 66 2e 0f 1f 84 00 00 00 00 00 66 66 66 66 90 55 48 
 [46339.720383] RIP  [<ffffffffa009de82>] i915_gem_set_domain_ioctl+0x232/0x240 [i915]
 [46339.723519]  RSP <ffff88009904fd70>
 [46339.733579] ---[ end trace 970778f70cafc4e7 ]---
 [46340.172800] done.
 [46340.172987] Freezing user space processes ... (elapsed 0.040 seconds) done.
 [46340.213501] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
 [46340.214841] Suspending console(s) (use no_console_suspend to debug)
 [46340.215200] sd 0:0:0:0: [sda] Synchronizing SCSI cache
 [46340.215690] sd 0:0:0:0: [sda] Stopping disk
 [46340.229263] mei_me 0000:00:16.0: suspend
 [46340.634393] PM: suspend of devices complete after 419.593 msecs
 [46340.634584] PM: late suspend of devices complete after 0.186 msecs


As it follows from this log this crash happened when suspending a laptop.  That action was apparently succesfull; only after a restore a machine woke up, to some extent, but with a totally useless display (entirely frozen or a black field with a mouse pointer and nothing less).

Subsequent logs examination found 2741 "[drm] stuck on render ring" entries and also interspersed with
[drm:i915_set_reset_status] *ERROR* render ring hung inside bo (0x4371000 ctx 0) at 0x4371ff4
from time to time.  I do not know if this is related but see bug 1027328 too.  (I am afraid that I nothing in /sys/class/drm/card0/error; a machine was rather useless, with "kernel BUG" on a console, and I rebooted it before looking at logs).


Version-Release number of selected component (if applicable):
kernel-3.12.7-300.fc20.x86_64
libdrm-2.4.50-1.fc20
gnome-shell-3.10.2.1-3.fc20

How reproducible:
No idea at this moment

Additional info:
It is possible that "stuck on render ring" messages started to show up when I tried experiments with xscreensaver.  I did that because despite of gnome-shell settings which should turn off a screen after some minutes of idle time this never happens (should a bug reported be filed too?).

That laptop was running before Fedora 18 and with that distro it newer had problems with powering down a screen, suspending and hibernating.  All that looks like a sharp regress.