<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW "
title="NEW - [BSW]igt/gem_evict_everything/minor-hang not enough mem, dmesg warning"
href="https://bugs.freedesktop.org/show_bug.cgi?id=88482">88482</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>[BSW]igt/gem_evict_everything/minor-hang not enough mem, dmesg warning
</td>
</tr>
<tr>
<th>Product</th>
<td>DRI
</td>
</tr>
<tr>
<th>Version</th>
<td>DRI git
</td>
</tr>
<tr>
<th>Hardware</th>
<td>Other
</td>
</tr>
<tr>
<th>OS</th>
<td>All
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Severity</th>
<td>normal
</td>
</tr>
<tr>
<th>Priority</th>
<td>medium
</td>
</tr>
<tr>
<th>Component</th>
<td>DRM/Intel
</td>
</tr>
<tr>
<th>Assignee</th>
<td>intel-gfx-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>hengx.ding@intel.com
</td>
</tr>
<tr>
<th>QA Contact</th>
<td>intel-gfx-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>CC</th>
<td>intel-gfx-bugs@lists.freedesktop.org
</td>
</tr></table>
<p>
<div>
<pre>Created <span class=""><a href="attachment.cgi?id=112328" name="attach_112328" title="dmesg for this case">attachment 112328</a> <a href="attachment.cgi?id=112328&action=edit" title="dmesg for this case">[details]</a></span>
dmesg for this case
==System Environment==
--------------------------
Regression: No, this is a new case.
Non-working platforms: BSW
==kernel==
--------------------------
origin/drm-intel-nightly:95cce4b4c5f3ecaf9c1c01d42f670da2748fcffb(fails)
==Bug detailed description==
-----------------------------
dmesg -r | egrep "<[1-6]>" |grep drm
<6>[ 160.817604] [drm] stuck on render ring
<6>[ 160.847315] [drm] GPU HANG: ecode 8:0:0xe757fffe, reason: Ring hung,
action: reset
<6>[ 160.847329] [drm] GPU hangs can indicate a bug anywhere in the entire gfx
stack, including userspace.
<6>[ 160.847332] [drm] Please file a _new_ bug report on bugs.freedesktop.org
against DRI -> DRM/Intel
<6>[ 160.847348] [drm] drm/i915 developers can then reassign to the right
component if it's not a kernel issue.
<6>[ 160.847353] [drm] The gpu crash dump is required to analyze gpu hangs, so
please always attach it.
<6>[ 160.847356] [drm] GPU crash dump saved to /sys/class/drm/card0/error
<5>[ 160.849206] drm/i915: Resetting chip after gpu hang
<4>[ 162.820074] WARNING: CPU: 0 PID: 891 at
drivers/gpu/drm/i915/intel_pm.c:3874 valleyview_set_rps+0x58/0x153 [i915]()
<4>[ 162.820080] Modules linked in: ipv6 dm_mod snd_hda_codec_hdmi iTCO_wdt
iTCO_vendor_support pcspkr serio_raw snd_hda_codec_realtek
snd_hda_codec_generic i2c_i801 lpc_ich mfd_core snd_hda_intel
snd_hda_controller snd_hda_codec snd_hwdep snd_pcm snd_timer snd soundcore
battery ac acpi_cpufreq joydev i915 button video drm_kms_helper drm cfbfillrect
cfbimgblt cfbcopyarea
<4>[ 162.820132] CPU: 0 PID: 891 Comm: kworker/0:1 Tainted: G W
3.19.0-rc4_drm-intel-nightly_95cce4_20150116+ #498
==Reproduce steps==
----------------------------
1. ./gem_evict_alignment --run-subtest minor-hang</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>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>