<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body><span class="vcard"><a class="email" href="mailto:matthew.d.roper@intel.com" title="Matt Roper <matthew.d.roper@intel.com>"> <span class="fn">Matt Roper</span></a>
</span> changed
<a class="bz_bug_link
bz_status_NEEDINFO "
title="NEEDINFO - [SKL bisected] system hang when changing resolution in games or killing gnome-session twice"
href="https://bugs.freedesktop.org/show_bug.cgi?id=89727">bug 89727</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;">Status</td>
<td>NEW
</td>
<td>NEEDINFO
</td>
</tr></table>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEEDINFO "
title="NEEDINFO - [SKL bisected] system hang when changing resolution in games or killing gnome-session twice"
href="https://bugs.freedesktop.org/show_bug.cgi?id=89727#c8">Comment # 8</a>
on <a class="bz_bug_link
bz_status_NEEDINFO "
title="NEEDINFO - [SKL bisected] system hang when changing resolution in games or killing gnome-session twice"
href="https://bugs.freedesktop.org/show_bug.cgi?id=89727">bug 89727</a>
from <span class="vcard"><a class="email" href="mailto:matthew.d.roper@intel.com" title="Matt Roper <matthew.d.roper@intel.com>"> <span class="fn">Matt Roper</span></a>
</span></b>
<pre>(In reply to Gordon Jin from <a href="show_bug.cgi?id=89727#c4">comment #4</a>)
<span class="quote">> (In reply to Damien Lespiau from <a href="show_bug.cgi?id=89727#c3">comment #3</a>)
> > I can't reproduce this one by starting X and killing it, nor by doing init
> > 3/init 5 cycles.
>
> xinit is not sufficient. Could you try gnome-session as well?</span >
To confirm, you can xinit and kill X as many times as you like without problem,
but if you start a full Gnome session, kill it, start a second Gnome session,
and then kill it again, you see a hang?
I don't have access to a SKL platform, so I'm a bit blind here, but can you try
a few things (assuming my understanding above is correct and also that you
still see this issue on the latest -nightly)?
- Test with xinit, but make sure you move your mouse into and out of the xterm
that usually gets started by default to ensure the mouse cursor has to
appear/change before you kill X. I want to rule out the framebuffer reference
counting issues we had with universal cursors recently.
- Start with xinit, but run xrandr to set varying display modes. I.e., can we
easily trigger this crash by just switching modes with nothing else going on?</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>
</ul>
</body>
</html>