<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body><span class="vcard"><a class="email" href="mailto:jinxianx.guo@intel.com" title="Guo Jinxian <jinxianx.guo@intel.com>"> <span class="fn">Guo Jinxian</span></a>
</span> changed
<a class="bz_bug_link
bz_status_NEEDINFO "
title="NEEDINFO - [HSW Bisected]igt/drv_module_reload causes WARNING "Memory manager not clean during takedown." + slab not clean"
href="https://bugs.freedesktop.org/show_bug.cgi?id=86507">bug 86507</a>
<br>
<table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>What</th>
<th>Removed</th>
<th>Added</th>
</tr>
<tr>
<td style="text-align:right;">Keywords</td>
<td>bisect_pending
</td>
<td>
</td>
</tr>
<tr>
<td style="text-align:right;">Summary</td>
<td>[HSW Regression]igt/drv_module_reload causes WARNING "Memory manager not clean during takedown." + slab not clean
</td>
<td>[HSW Bisected]igt/drv_module_reload causes WARNING "Memory manager not clean during takedown." + slab not clean
</td>
</tr></table>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEEDINFO "
title="NEEDINFO - [HSW Bisected]igt/drv_module_reload causes WARNING "Memory manager not clean during takedown." + slab not clean"
href="https://bugs.freedesktop.org/show_bug.cgi?id=86507#c2">Comment # 2</a>
on <a class="bz_bug_link
bz_status_NEEDINFO "
title="NEEDINFO - [HSW Bisected]igt/drv_module_reload causes WARNING "Memory manager not clean during takedown." + slab not clean"
href="https://bugs.freedesktop.org/show_bug.cgi?id=86507">bug 86507</a>
from <span class="vcard"><a class="email" href="mailto:jinxianx.guo@intel.com" title="Guo Jinxian <jinxianx.guo@intel.com>"> <span class="fn">Guo Jinxian</span></a>
</span></b>
<pre>dcb4c12a687710ab745c2cdee8298c3e97f6f707 is the first bad commit
Author: Oscar Mateo <<a href="mailto:oscar.mateo@intel.com">oscar.mateo@intel.com</a>>
AuthorDate: Thu Nov 13 10:28:10 2014 +0000
Commit: Daniel Vetter <<a href="mailto:daniel.vetter@ffwll.ch">daniel.vetter@ffwll.ch</a>>
CommitDate: Wed Nov 19 19:32:58 2014 +0100
drm/i915/bdw: Pin the context backing objects to GGTT on-demand
Up until now, we have pinned every logical ring context backing object
during creation, and left it pinned until destruction. This made my life
easier, but it's a harmful thing to do, because we cause fragmentation
of the GGTT (and, eventually, we would run out of space).
This patch makes the pinning on-demand: the backing objects of the two
contexts that are written to the ELSP are pinned right before submission
and unpinned once the hardware is done with them. The only context that
is still pinned regardless is the global default one, so that the HWS can
still be accessed in the same way (ring->status_page).
v2: In the early version of this patch, we were pinning the context as
we put it into the ELSP: on the one hand, this is very efficient because
only a maximum two contexts are pinned at any given time, but on the other
hand, we cannot really pin in interrupt time :(
v3: Use a mutex rather than atomic_t to protect pin count to avoid races.
Do not unpin default context in free_request.
v4: Break out pin and unpin into functions. Fix style problems reported
by checkpatch
v5: Remove unpin_lock as all pinning and unpinning is done with the struct
mutex already locked. Add WARN_ONs to make sure this is the case in
future.
Issue: VIZ-4277
Signed-off-by: Oscar Mateo <<a href="mailto:oscar.mateo@intel.com">oscar.mateo@intel.com</a>>
Signed-off-by: Thomas Daniel <<a href="mailto:thomas.daniel@intel.com">thomas.daniel@intel.com</a>>
Reviewed-by: Akash Goel <<a href="mailto:akash.goels@gmail.com">akash.goels@gmail.com</a>>
Reviewed-by: Deepak S<<a href="mailto:deepak.s@linux.intel.com">deepak.s@linux.intel.com</a>>
Signed-off-by: Daniel Vetter <<a href="mailto:daniel.vetter@ffwll.ch">daniel.vetter@ffwll.ch</a>>
:040000 040000 b99fffd2ff94e9c66c4797886726deb6cdf9d502
d3501260bc640ac87a2a95d13ecfc379caaf4d41 M drivers
On it's parents commit(c86ee3a9f8cddcf2e637da19d6e7c05bdea11a96), another dmseg
warning reproduced.
[root@x-hsw24 tests]# ./drv_module_reload
unbinding /sys/class/vtconsole/vtcon0/: (M) frame buffer device
module successfully unloaded
[root@x-hsw24 tests]# dmesg -r|egrep "<[1-4]>"|grep drm
<4>[ 48.255113] WARNING: CPU: 5 PID: 3981 at
drivers/gpu/drm/i915/intel_pm.c:6207 intel_disable_gt_powersave+0x33/0x37a
[i915]()
<4>[ 48.255117] dm_mod snd_hda_codec_realtek snd_hda_codec_generic iTCO_wdt
iTCO_vendor_support snd_hda_codec_hdmi dcdbas serio_raw pcspkr i2c_i801
snd_hda_controller snd_hda_codec snd_hwdep lpc_ich shpchp mfd_core snd_pcm
snd_timer snd soundcore battery acpi_cpufreq i915(-) button video
drm_kms_helper drm [last unloaded: snd_hda_intel]
<4>[ 48.255165] [<ffffffffa0004dd3>] ? vblank_disable_and_save+0x170/0x17f
[drm]
<4>[ 48.255197] [<ffffffffa0007527>] ? drm_dev_unregister+0x1e/0x8b [drm]
<4>[ 48.255202] [<ffffffffa0007757>] ? drm_put_dev+0x3e/0x47 [drm]
<4>[ 48.255222] [<ffffffffa000917a>] ? drm_pci_exit+0x38/0x98 [drm]</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>