From: "Souza, Jose" <jose.souza@intel.com>
To: "James.Bottomley@HansenPartnership.com"
<James.Bottomley@HansenPartnership.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 22:26:50 +0000 [thread overview]
Message-ID: <dad073fb4b06cf0abb7ab702a9474b9c443186eb.camel@intel.com> (raw)
In-Reply-To: <1562882235.13723.1.camel@HansenPartnership.com>
On Thu, 2019-07-11 at 14:57 -0700, James Bottomley wrote:
> On Thu, 2019-07-11 at 13:28 -0700, James Bottomley wrote:
> > I've also updated to the released 5.2 kernel and am running with
> > the
> > debug parameters you requested ... but so far no reproduction.
>
> OK, it's happened. I've attached the dmesg (it's 4MB uncompressed).
> Is there any other output you'd like from the machine? I've got an
> ssh
> session into it so I can try anything.
Thanks, could you also share the output of this after the screen
freeze?
/sys/kernel/debug/dri/0/i915_edp_psr_status
/sys/kernel/debug/dri/0/i915_display_info
/sys/kernel/debug/dri/0/i915_dmc_info
/sys/kernel/debug/pmc_core/package_cstate_show
It eventually comes back from screen freeze? Like moving the mouse or
typing brings it back?
>
> James
next prev parent reply other threads:[~2019-07-11 22:26 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 ` 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 [this message]
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 ` [Intel-gfx] " Paul Bolle
2019-07-15 21:03 ` Souza, Jose
2019-07-15 21:34 ` Paul Bolle
2019-07-16 16:32 ` [Intel-gfx] " 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 ` [Intel-gfx] " 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=dad073fb4b06cf0abb7ab702a9474b9c443186eb.camel@intel.com \
--to=jose.souza@intel.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=chris@chris-wilson.co.uk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox