<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 - i915 resume weirdness/OOM OOPSing, but only when built-into kernel"
href="https://bugs.freedesktop.org/show_bug.cgi?id=93815">93815</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>i915 resume weirdness/OOM OOPSing, but only when built-into kernel
</td>
</tr>
<tr>
<th>Product</th>
<td>DRI
</td>
</tr>
<tr>
<th>Version</th>
<td>XOrg git
</td>
</tr>
<tr>
<th>Hardware</th>
<td>x86-64 (AMD64)
</td>
</tr>
<tr>
<th>OS</th>
<td>Linux (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>kenny@panix.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>If I compile the i915 DRM driver into the kernel
directly, I get OOM (et al). crashes upon resuming from suspend. Made as a
module and loaded post-init (at first boot), no problems at all.
Because I'm running X at the time I suspend (and I'm using the vanilla kernel's
"swsusp"), the i915 module can't even be removed at the time of suspend, so
(wild-assed guess coming) there's "something" in the module-initialization
code (or throw-away upon init() pages?) that prevents the following from
happening (and I don't know from GPUs, but I'll bet that first line is the
smoking gun here):
----
[ 844.911705] Purging GPU memory, 130011136 bytes freed, 19116032 bytes still
pinned.
[ 844.911988] ibus-ui-gtk3 invoked oom-killer: gfp_mask=0x0, order=0,
oom_score_adj=0
[ 844.911991] CPU: 4 PID: 2814 Comm: ibus-ui-gtk3 Tainted: G O
4.4.0-Kenny-EFI+ #5
[ 844.911992] Hardware name: TOSHIBA Satellite P75-A/Type2 - Board Product
Name1, BIOS 1.60 12/04/2014
[ 844.911993] ffff880441df7e98 ffff880441df7d50 ffffffff814275b2
0000000000000000
[ 844.911995] ffff880441df7dd8 ffffffff81173ad9 0000000000000000
ffff880441df7db0
[ 844.911997] ffffffff81554d86 0000000000000000 01ff880441df7da0
00000000ffffffff
[ 844.911998] Call Trace:
[ 844.912003] [<ffffffff814275b2>] dump_stack+0x4b/0x79
[ 844.912007] [<ffffffff81173ad9>] dump_header.isra.9+0x4c/0x1c9
[ 844.912010] [<ffffffff81554d86>] ? i915_gem_shrinker_oom+0x186/0x1f0
[ 844.912012] [<ffffffff811276d1>] oom_kill_process+0x201/0x3f0
[ 844.912014] [<ffffffff81127bbb>] out_of_memory+0x29b/0x2f0
[ 844.912015] [<ffffffff81127c55>] pagefault_out_of_memory+0x45/0x90
[ 844.912018] [<ffffffff81094467>] mm_fault_error+0x59/0x101
[ 844.912020] [<ffffffff810381fd>] __do_page_fault+0x2bd/0x360
[ 844.912022] [<ffffffff810382dc>] do_page_fault+0xc/0x10
[ 844.912025] [<ffffffff81943bd2>] page_fault+0x22/0x30
(I'd E-mailed Daniel and Jani the output of "dmesg" which I no longer have;
I've asked them to add it to this bug report if they've still got it).</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
<li>You are the QA Contact for the bug.</li>
<li>You are on the CC list for the bug.</li>
</ul>
</body>
</html>