<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW --- - Frequent loss of screen content, system barely usable"
href="https://bugs.freedesktop.org/show_bug.cgi?id=76608#c2">Comment # 2</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW --- - Frequent loss of screen content, system barely usable"
href="https://bugs.freedesktop.org/show_bug.cgi?id=76608">bug 76608</a>
from <span class="vcard"><a class="email" href="mailto:whistler_mb@gmx.net" title="whistler_mb@gmx.net">whistler_mb@gmx.net</a>
</span></b>
<pre>Same problem here
kern.log:
Mar 25 22:56:18 Tuxedo kernel: [ 77.405050] [drm] stuck on render ring
Mar 25 22:56:18 Tuxedo kernel: [ 77.405058] [drm] GPU crash dump saved to
/sys/class/drm/card0/error
Mar 25 22:56:18 Tuxedo kernel: [ 77.405060] [drm] GPU hangs can indicate a
bug anywhere in the entire gfx stack, including userspace.
Mar 25 22:56:18 Tuxedo kernel: [ 77.405061] [drm] Please file a _new_ bug
report on bugs.freedesktop.org against DRI -> DRM/Intel
Mar 25 22:56:18 Tuxedo kernel: [ 77.405062] [drm] drm/i915 developers can
then reassign to the right component if it's not a kernel issue.
Mar 25 22:56:18 Tuxedo kernel: [ 77.405064] [drm] The gpu crash dump is
required to analyze gpu hangs, so please always attach it.
Mar 25 22:56:23 Tuxedo kernel: [ 83.431319] [drm] stuck on render ring
Mar 25 22:56:29 Tuxedo kernel: [ 89.444223] [drm] stuck on render ring
Mar 25 22:56:35 Tuxedo kernel: [ 95.390385] [drm] stuck on render ring
Mar 25 22:56:41 Tuxedo kernel: [ 101.450022] [drm] stuck on render ring
~$ inxi -v3
System: Host: Tuxedo Kernel: 3.13-6.towo-siduction-amd64 x86_64 (64 bit gcc:
4.8.2)
Desktop: KDE 4.12.3 (Qt 4.8.6) Distro: siduction 13.1.0 Firestarter
- kde - (201305211844)
Machine: Mobo: Notebook model: W230ST Bios: American Megatrends v: 4.6.5
date: 07/16/2013
CPU: Quad core Intel Core i7-4702MQ CPU (-HT-MCP-) cache: 6144 KB
flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 17565
Clock Speeds: 1: 2200 MHz 2: 2211 MHz 3: 2200 MHz 4: 2443 MHz 5:
2200 MHz 6: 2200 MHz 7: 2200 MHz 8: 2201 MHz
Graphics: Card: Intel 4th Gen Core Processor Integrated Graphics Controller
bus-ID: 00:02.0
Display Server: X.Org 1.15.0 drivers: intel (unloaded: fbdev,vesa)
Resolution: <a href="mailto:1920x1080@60.0hz">1920x1080@60.0hz</a>
GLX Renderer: Mesa DRI Intel Haswell Mobile GLX Version: 3.0 Mesa
10.1.0 Direct Rendering: Yes
Network: Card-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
Controller
driver: r8169 v: 2.3LK-NAPI port: e000 bus-ID: 04:00.1
IF: eth0 state: down mac: xx:xx:xx:xx:xx:xx
Card-2: Intel Wireless 7260 driver: iwlwifi v: in-tree: bus-ID:
03:00.0
IF: wlan0 state: down mac: xx:xx:xx:xx:xx:xx
Drives: HDD Total Size: 1120.2GB (38.9% used) 1: model: HGST_HTS721010A9
2: model: Crucial_CT120M50
Info: Processes: 218 Uptime: 27 min Memory: 1138.2/15975.4MB Init:
SysVinit runlevel: 5 Gcc sys: 4.8.2
Client: Shell (bash 4.3.01) inxi: 2.1.7</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
<li>You are on the CC list for the bug.</li>
</ul>
</body>
</html>