All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: intel-gfx@lists.freedesktop.org
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: screen freeze with 5.2-rc6 Dell XPS-13 skylake  i915
Date: Wed, 10 Jul 2019 08:01:14 -0700	[thread overview]
Message-ID: <1562770874.3213.14.camel@HansenPartnership.com> (raw)
In-Reply-To: <1561834612.3071.6.camel@HansenPartnership.com>

On Sat, 2019-06-29 at 11:56 -0700, James Bottomley wrote:
> The symptoms are really weird: the screen image is locked in place. 
> The machine is still functional and if I log in over the network I
> can do anything I like, including killing the X server and the
> display will never alter.  It also seems that the system is accepting
> keyboard input because when it freezes I can cat information to a
> file (if the mouse was over an xterm) and verify over the network the
> file contents. Nothing unusual appears in dmesg when the lockup
> happens.
> 
> The last kernel I booted successfully on the system was 5.0, so I'll
> try compiling 5.1 to narrow down the changes.

I've confirmed that 5.1 doesn't have the regression and I'm now trying
to bisect the 5.2 merge window, but since the problem takes quite a
while to manifest this will take some time.  Any hints about specific
patches that might be the problem would be welcome.

James


  parent reply	other threads:[~2019-07-10 15:01 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-29 18:56 screen freeze with 5.2-rc6 Dell XPS-13 skylake i915 James Bottomley
2019-07-09 13:52 ` Paul Bolle
2019-07-10 15:01 ` James Bottomley [this message]
2019-07-10 16:16   ` Paul Bolle
2019-07-10 16:32     ` James Bottomley
2019-07-10 16:32       ` James Bottomley
2019-07-10 16:45       ` Paul Bolle
2019-07-10 16:45         ` Paul Bolle
2019-07-10 17:35         ` James Bottomley
2019-07-10 21:59           ` Paul Bolle
2019-07-10 22:18             ` James Bottomley
2019-07-11 19:32               ` [Intel-gfx] " Souza, Jose
2019-07-11 19:32                 ` Souza, Jose
2019-07-11  9:29 ` Chris Wilson
2019-07-11 11:20   ` Paul Bolle
2019-07-11 11:20     ` Paul Bolle
2019-07-12 10:32     ` Paul Bolle
2019-07-11 20:11   ` James Bottomley
2019-07-11 20:25     ` [Intel-gfx] " Souza, Jose
2019-07-11 20:25       ` Souza, Jose
2019-07-11 20:28       ` [Intel-gfx] " James Bottomley
2019-07-11 21:57         ` James Bottomley
2019-07-11 22:26           ` Souza, Jose
2019-07-11 22:26             ` Souza, Jose
2019-07-11 22:38             ` James Bottomley
2019-07-11 23:03               ` Paul Bolle
2019-07-11 23:28                 ` Souza, Jose
2019-07-11 23:28                   ` Souza, Jose
2019-07-11 23:40                   ` James Bottomley
2019-07-11 23:40                     ` James Bottomley
2019-07-12 14:19                     ` [Intel-gfx] " James Bottomley
2019-07-12 14:19                       ` James Bottomley
2019-07-12 14:28                       ` [Intel-gfx] " Paul Bolle
2019-07-15 21:03                         ` Souza, Jose
2019-07-15 21:03                           ` Souza, Jose
2019-07-15 21:34                           ` [Intel-gfx] " Paul Bolle
2019-07-15 21:34                             ` Paul Bolle
2019-07-16 16:32                             ` [Intel-gfx] " Souza, Jose
2019-07-16 16:32                               ` Souza, Jose
2019-07-17 21:27                               ` Paul Bolle
2019-07-17 21:27                                 ` Paul Bolle
2019-07-17 21:29                                 ` James Bottomley
2019-07-24 19:23                                   ` Paul Bolle
2019-07-24 20:27                                     ` Souza, Jose
2019-07-24 20:27                                       ` Souza, Jose
2019-07-24 20:39                                       ` [Intel-gfx] " Paul Bolle
2019-07-24 20:39                                         ` Paul Bolle
2019-07-24 20:42                                         ` Souza, Jose
2019-07-24 20:42                                           ` Souza, Jose
2019-08-09 17:16                                         ` Souza, Jose
2019-08-09 17:16                                           ` Souza, Jose
2019-08-10 19:40                                           ` Paul Bolle

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1562770874.3213.14.camel@HansenPartnership.com \
    --to=james.bottomley@hansenpartnership.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.