From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: "Souza, Jose" <jose.souza@intel.com>,
"pebolle@tiscali.nl" <pebolle@tiscali.nl>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"chris@chris-wilson.co.uk" <chris@chris-wilson.co.uk>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [Intel-gfx] screen freeze with 5.2-rc6 Dell XPS-13 skylake i915
Date: Thu, 11 Jul 2019 16:40:33 -0700 [thread overview]
Message-ID: <1562888433.2915.0.camel@HansenPartnership.com> (raw)
In-Reply-To: <55f4d1c242d684ca2742e8c14613d810a9ee9504.camel@intel.com>
On Thu, 2019-07-11 at 23:28 +0000, Souza, Jose wrote:
> On Fri, 2019-07-12 at 01:03 +0200, Paul Bolle wrote:
> > James Bottomley schreef op do 11-07-2019 om 15:38 [-0700]:
> > > On Thu, 2019-07-11 at 22:26 +0000, Souza, Jose wrote:
> > > > It eventually comes back from screen freeze? Like moving the
> > > > mouse or typing brings it back?
> > >
> > > No, it seems to be frozen for all time (at least until I got
> > > bored waiting, which was probably 20 minutes). Even if I reboot
> > > the machine, the current screen state stays until the system
> > > powers off.
> >
> > As I mentioned earlier, a suspend/resume cycle unfreezes the
> > screen.
> >
> > And I seem to remember that, if the gnome screen-locking eventually
> > kicks in, unlocking the screen still works, as the screen then
> > isn't frozen anymore.
> >
> > Thanks,
>
> Thanks for all the information Paul.
>
> Could test with the patch attached?
Applied and running with it now.
> If the issue happens again could send the output of:
>
> /sys/kernel/debug/dri/0/eDP-1/i915_psr_sink_status
> /sys/kernel/debug/dri/0/i915_edp_psr_status
>
> Thanks so much for all the help
Sure,
James
next prev parent reply other threads:[~2019-07-11 23:41 UTC|newest]
Thread overview: 35+ 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
2019-07-10 16:16 ` Paul Bolle
2019-07-10 16:32 ` James Bottomley
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 9:29 ` Chris Wilson
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:28 ` James Bottomley
2019-07-11 21:57 ` James Bottomley
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:40 ` James Bottomley [this message]
2019-07-12 14:19 ` James Bottomley
2019-07-12 14:28 ` Paul Bolle
2019-07-15 21:03 ` Souza, Jose
2019-07-15 21:34 ` Paul Bolle
2019-07-16 16:32 ` Souza, Jose
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:39 ` Paul Bolle
2019-07-24 20:42 ` 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=1562888433.2915.0.camel@HansenPartnership.com \
--to=james.bottomley@hansenpartnership.com \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jose.souza@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pebolle@tiscali.nl \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox