<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body><span class="vcard"><a class="email" href="mailto:s.zharkoff@gmail.com" title="s.zharkoff@gmail.com">s.zharkoff@gmail.com</a>
</span> changed
<a class="bz_bug_link
bz_status_NEW "
title="NEW - No package C-states on Dell XPS 15 9570 after resume from deep sleep"
href="https://bugs.freedesktop.org/show_bug.cgi?id=111623">bug 111623</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;">OS</td>
<td>All
</td>
<td>Linux (All)
</td>
</tr>
<tr>
<td style="text-align:right;">Version</td>
<td>XOrg git
</td>
<td>DRI git
</td>
</tr>
<tr>
<td style="text-align:right;">Hardware</td>
<td>Other
</td>
<td>x86-64 (AMD64)
</td>
</tr></table>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - No package C-states on Dell XPS 15 9570 after resume from deep sleep"
href="https://bugs.freedesktop.org/show_bug.cgi?id=111623#c1">Comment # 1</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - No package C-states on Dell XPS 15 9570 after resume from deep sleep"
href="https://bugs.freedesktop.org/show_bug.cgi?id=111623">bug 111623</a>
from <span class="vcard"><a class="email" href="mailto:s.zharkoff@gmail.com" title="s.zharkoff@gmail.com">s.zharkoff@gmail.com</a>
</span></b>
<pre>Movig the bug from kernel bugzilla
<a href="https://bugzilla.kernel.org/show_bug.cgi?id=204751">https://bugzilla.kernel.org/show_bug.cgi?id=204751</a>
Kernel 5.2 series - suspend, resume - package enter c-states up to C10.
Kernel 5.3 starting from 5.3-rc1 till latest drm-tip builds - states up to C10
before suspend, no package C-states after resume.
Zhang Rui:
before suspend
CPU%c7 CoreTmp PkgTmp GFX%rc6 GFXMHz Totl%C0 Any%C0 GFX%C0
99.40 38 38 99.85 350 1.29 0.79 0.14
after resume
CPU%c7 CoreTmp PkgTmp GFX%rc6 GFXMHz Totl%C0 Any%C0 GFX%C0
99.49 39 39 1.32 350 1.21 1.00 95.04
It is graphics that blocks cpu from entering package c-state.
Please file a bug at freedesktop.org and attach the full dmesg output with
kernel parameter drm.debug=0xe, after the problem reproduced.</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>