<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body><span class="vcard"><a class="email" href="mailto:lakshminarayana.vudum@intel.com" title="Lakshmi <lakshminarayana.vudum@intel.com>"> <span class="fn">Lakshmi</span></a>
</span> changed
<a class="bz_bug_link
bz_status_NEW "
title="NEW - Built-in display corrupted after wake-up from S3 on Dell XPS 7390 2-in-1 (Ice Lake)"
href="https://bugs.freedesktop.org/show_bug.cgi?id=112143">bug 112143</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;">CC</td>
<td>
</td>
<td>imre.deak@intel.com
</td>
</tr></table>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Built-in display corrupted after wake-up from S3 on Dell XPS 7390 2-in-1 (Ice Lake)"
href="https://bugs.freedesktop.org/show_bug.cgi?id=112143#c3">Comment # 3</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Built-in display corrupted after wake-up from S3 on Dell XPS 7390 2-in-1 (Ice Lake)"
href="https://bugs.freedesktop.org/show_bug.cgi?id=112143">bug 112143</a>
from <span class="vcard"><a class="email" href="mailto:lakshminarayana.vudum@intel.com" title="Lakshmi <lakshminarayana.vudum@intel.com>"> <span class="fn">Lakshmi</span></a>
</span></b>
<pre>(In reply to Andreas Kloeckner from <a href="show_bug.cgi?id=112143#c0">comment #0</a>)
<span class="quote">> I have a Dell XPS 7390 2-in-1, which use a "Intel(R) Core(TM) i7-1065G7 CPU
> @ 1.30GHz". While the machine defaults to s2idle, energy consumption in that
> state is high, which led me to investigate S3 sleep, enabled by
>
> echo deep|sudo tee /sys/power/mem_sleep
>
> This works well, except for one annoying showstopper wrinkle: The machine's
> built-in display remains on a corrupted version of the Dell logo after
> wake-up. All other aspects of the machine (including externally attached
> displays) resume entirely fine, but the internal display remains garbled
> until a reset or power cycle.
>
> I've recorded a video to better convey what's happening:
>
> <a href="https://ssl.tiker.net/nextcloud/s/jZQjjgjT2EwedBe">https://ssl.tiker.net/nextcloud/s/jZQjjgjT2EwedBe</a>
>
> Notably, the pixel pattern in the corrupted logo *does* change in response
> to interactions with the system, meaning that likely *some* part of the
> framebuffer is being shown, but display state is not sufficiently reset to
> enable proper display function.
>
> Linux lightning 5.4.0-rc5 #1 SMP Sun Oct 27 12:56:36 CDT 2019 x86_64
> GNU/Linux
>
> -- Linux distribution:
>
> Debian testing/unstable
>
> -- Machine or mother board model:
>
> From dmidecode:
>
> Handle 0x0100, DMI type 1, 27 bytes
> System Information
> Manufacturer: Dell Inc.
> Product Name: XPS 13 7390 2-in-1
> Version: Not Specified
> Serial Number: (redacted)
> UUID: (redacted)
> Wake-up Type: Power Switch
> SKU Number: 08B0
> Family: XPS
>
> Handle 0x0200, DMI type 2, 17 bytes
> Base Board Information
> Manufacturer: Dell Inc.
> Product Name: 06CDVY
> Version: A00
> Serial Number: (redacted)
> Asset Tag: Not Specified
> Features:
> Board is a hosting board
> Board is replaceable
> Location In Chassis: Not Specified
> Chassis Handle: 0x0000
> Type: Motherboard
> Contained Object Handles: 0
>
> -- Display connector: (such as HDMI, DP, eDP, ...)
>
> Output of xrandr --verbose:
> <a href="https://gist.github.com/inducer/169409e85ee9a8999a7834f401558146">https://gist.github.com/inducer/169409e85ee9a8999a7834f401558146</a>
>
> -- Register dumps before/after S3:
>
> <a href="https://gist.github.com/inducer/346c05cc9331c68213cda51e9bdbf7cc">https://gist.github.com/inducer/346c05cc9331c68213cda51e9bdbf7cc</a>
>
> -- Other version info
>
> <a href="https://gist.github.com/inducer/e51bb5bbfca3f307066b375b062e939d">https://gist.github.com/inducer/e51bb5bbfca3f307066b375b062e939d</a></span >
@Imre, any comments here?</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 on the CC list for the bug.</li>
<li>You are the QA Contact for the bug.</li>
</ul>
</body>
</html>