<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 - Intel GemniLake laptops goes power off directly after performing suspend"
href="https://bugs.freedesktop.org/show_bug.cgi?id=104235">104235</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>Intel GemniLake laptops goes power off directly after performing suspend
</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>critical
</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>chiu@endlessm.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=136128" name="attach_136128" title="dmesg log of performing S3 on GemniLake">attachment 136128</a> <a href="attachment.cgi?id=136128&action=edit" title="dmesg log of performing S3 on GemniLake">[details]</a></span>
dmesg log of performing S3 on GemniLake
Multiple new Acer and Asus consumer products based on Intel GeminiLake
N4100/N5000 fail to go into S3 suspend-to-RAM. At the point when you
would normally expect the system to go into sleep, the computer
completely powers off.
The same happens under Windows 10 RS3 too, until the following Intel
graphics driver is installed:
Package: 530967
Intel(R) Graphics Driver: 23.20.16.4849
Intel(R) Display Audio Driver: 10.00.00.1
After installing this driver, Windows can now go into S3 suspend and
also be resumed. I'm wondering if someone can check with the Windows
gfx driver developers what this driver does to affect S3 suspend so
that we can fix up Linux behavior.
Also tried to boot Linux with "nomodeset" parameter, it can go into sleep
w/o problem, but exit suspend with blank screen. The attached dmesg log shows
it comes back from suspend.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are on the CC list for the bug.</li>
<li>You are the QA Contact for the bug.</li>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>