<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 - [PNV/BYT Bisected]igt/kms_force_connector causes system crashes"
href="https://bugs.freedesktop.org/show_bug.cgi?id=84771">84771</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>[PNV/BYT Bisected]igt/kms_force_connector causes system crashes
</td>
</tr>
<tr>
<th>Product</th>
<td>DRI
</td>
</tr>
<tr>
<th>Version</th>
<td>unspecified
</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>high
</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>jinxianx.guo@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>==System Environment==
--------------------------
Regression: Yes.
Non-working platforms: PNV BYT
==kernel==
--------------------------
origin/drm-intel-nightly:eabc0c8db15f9ba4d727aee5e0612a68cafe1ab5(fails)
drm-intel-nightly: 2014y-10m-03d-21h-34m-34s UTC integration manifest
==Bug detailed description==
-----------------------------
igt/kms_force_connector causes system crashes. and
igt/kms_cursor_crc/cursor-size-change have DMESG_WARN,
igt/gem_concurrent_blit/gpuX-rcs-early-read-forked test timeout on PNV.
(PNV)igt/kms_force_connector PASS->CRASH
(BYT)igt/kms_force_connector PASS->CRASH
(PNV)igt/kms_cursor_crc/cursor-size-change PASS->DMESG_WARN
<3>[ 3198.161595] [drm:display_pipe_crc_irq_handler] *ERROR* spurious interrupt
(PNV)igt/gem_concurrent_blit/gpuX-rcs-early-read-forked PASS->TIMEOUT
==Reproduce steps==
----------------------------
1. ./kms_force_connector
==Bisect results form [PRTS][auto-bisect]==
----------------------------
commit 5782eca1e19e85a04ad402fa4094aa1b5f9c53ce
Author: Tim Gore <<a href="mailto:tim.gore@intel.com">tim.gore@intel.com</a>>
AuthorDate: Wed Oct 1 13:25:20 2014 +0100
Commit: Daniel Vetter <<a href="mailto:daniel.vetter@ffwll.ch">daniel.vetter@ffwll.ch</a>>
CommitDate: Wed Oct 1 14:44:30 2014 +0200
lib/igt_core.c: disable lowmemorykiller during tests
Several IGT tests cycle through a lot of GEM memory and
when running these tests on Android they tend to get
killed by the lowmemorykiller. The lowmemorykiller really
is not usefull in this context and is just preventing the
test from doing its job. This commit adds a function to
disable the lowmemorykiller by writing "9999" to its
oom adj parameter, which means it will never "select"
any process to kill. The normal linux oom killer is still
there to protect the kernel.
The low memory killer is disabled during the common
init function and then re-enabled by the exit handler.
To make this work for single tests the exit handler is now
installed in the common init function also so that it is
invoked for all tests.
This is just a hack to get round the fact that the i915
driver uses the concept of purgeable memory which is not
understood by the lowmemorykiller. If this ever gets
fixed then this patch can be removed.
Signed-off-by: Tim Gore <<a href="mailto:tim.gore@intel.com">tim.gore@intel.com</a>>
[danvet: A bit of polish (coding style, static and rename
check_igt_exit to common_exit_handler, drop the is_disabled check
since we only call this once now).]
Signed-off-by: Daniel Vetter <<a href="mailto:daniel.vetter@ffwll.ch">daniel.vetter@ffwll.ch</a>></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>