[Bug 89727] [SKL bisected] system hang when changing resolution in games or killing gnome-session twice
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Wed Apr 1 15:48:26 PDT 2015
https://bugs.freedesktop.org/show_bug.cgi?id=89727
Matt Roper <matthew.d.roper at intel.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |NEEDINFO
--- Comment #8 from Matt Roper <matthew.d.roper at intel.com> ---
(In reply to Gordon Jin from comment #4)
> (In reply to Damien Lespiau from comment #3)
> > 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?
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?
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20150401/bf5208da/attachment.html>
More information about the intel-gfx-bugs
mailing list