From: Paul Bolle <pebolle@tiscali.nl>
To: "Souza, Jose" <jose.souza@intel.com>,
"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: Mon, 15 Jul 2019 23:34:59 +0200 [thread overview]
Message-ID: <595d9bc87bf47717c8675eb5b1a1cbb2bc463752.camel@tiscali.nl> (raw)
In-Reply-To: <143142cad4a946361a0bf285b6f1701c81096c7b.camel@intel.com>
Hi Jose,
Souza, Jose schreef op ma 15-07-2019 om 21:03 [+0000]:
> So the issue did not happened again with the patch applied?
Not in the three days that I've been running 5.2 kernels with the hack applied
(so that should be about twelve hours of proper uptime).
> If you still have the kernel 5.1 installed could you share your
> /sys/kernel/debug/dri/0/i915_edp_psr_status with the older kernel?
> We want to check if training values changed between kernel versions.
Sure. On 5.1.17 I get:
Sink support: yes [0x01]
PSR mode: PSR1 enabled
Source PSR ctl: enabled [0x81f00626]
Source PSR status: IDLE [0x040b0001]
Busy frontbuffer bits: 0x00000000
And, in case you need it, on 5.2.1+hack I get:
Sink support: yes [0x01]
PSR mode: PSR1 enabled
Source PSR ctl: enabled [0x81f00626]
Source PSR status: IDLE [0x04030006]
Busy frontbuffer bits: 0x00000000
Hope this helps,
Paul
next prev parent reply other threads:[~2019-07-15 21:35 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-29 18:56 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
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 [this message]
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=595d9bc87bf47717c8675eb5b1a1cbb2bc463752.camel@tiscali.nl \
--to=pebolle@tiscali.nl \
--cc=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
all inboxes | Powered by JetHome®