From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: "Souza, Jose" <jose.souza@intel.com>,
"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 13:28:00 -0700 [thread overview]
Message-ID: <1562876880.2840.12.camel@HansenPartnership.com> (raw)
In-Reply-To: <27a5b2ca8cfc79bf617387a363ea7192acc4e1f0.camel@intel.com>
On Thu, 2019-07-11 at 20:25 +0000, Souza, Jose wrote:
> On Thu, 2019-07-11 at 13:11 -0700, James Bottomley wrote:
> > On Thu, 2019-07-11 at 10:29 +0100, Chris Wilson wrote:
> > > Quoting James Bottomley (2019-06-29 19:56:52)
> > > > 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 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.
> > >
> > > It's likely this is panel self-refresh going haywire.
> > >
> > > commit 8f6e87d6d561f10cfa48a687345512419839b6d8
> > > Author: José Roberto de Souza <jose.souza@intel.com>
> > > Date: Thu Mar 7 16:00:50 2019 -0800
> > >
> > > drm/i915: Enable PSR2 by default
> > >
> > > The support for PSR2 was polished, IGT tests for PSR2 was
> > > added and
> > > it was tested performing regular user workloads like
> > > browsing,
> > > editing documents and compiling Linux, so it is time to
> > > enable it by
> > > default and enjoy even more power-savings.
> > >
> > > Temporary workaround would be to set i915.enable_psr=0
> >
> > It looks plausible. I have to say I was just about to mark a
> > bisect containing this as good, but that probably reflects my
> > difficulty
> > reproducing the issue.
>
> Take at look of what PSR version is supported by your panel, it
> likely that a notebook shipped with Skylake will have panel that
> supports only PSR1 so that patch has no effect on your machine.
>
> sudo more /sys/kernel/debug/dri/0/i915_edp_psr_status
> Sink support: yes [0x01]
It says
Sink support: yes [0x01]
PSR mode: PSR1 enabled
Source PSR ctl: enabled [0x81f00726]
Source PSR status: IDLE [0x04010212]
Busy frontbuffer bits: 0x00000000
I've also updated to the released 5.2 kernel and am running with the
debug parameters you requested ... but so far no reproduction.
James
next prev parent reply other threads:[~2019-07-11 20:28 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 [this message]
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
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=1562876880.2840.12.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 \
/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;
as well as URLs for NNTP newsgroup(s).