From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Paul Bolle <pebolle@tiscali.nl>,
"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, 18 Jul 2019 06:29:26 +0900 [thread overview]
Message-ID: <1563398966.3438.5.camel@HansenPartnership.com> (raw)
In-Reply-To: <9ef8fc1ae2c3a9bad588899488a781333af4449a.camel@tiscali.nl>
On Wed, 2019-07-17 at 23:27 +0200, Paul Bolle wrote:
> Hi Jose,
>
> Souza, Jose schreef op di 16-07-2019 om 16:32 [+0000]:
> > Paul and James could you test this final solution(at least for
> > 5.2)? Please revert the hack patch and apply this one.
>
> I've just reached a day of uptime with your revert. (The proper
> uptime is just a fraction of a day, this being a laptop.) Anyhow, no
> screen freezes occurred during this day.
I'm afraid my status is that I'm in Tokyo doing conference
presentations (and kernel demos) so I'm a bit reluctant to mess with my
setup until I finish everything on Friday, but I will test it after
then, promise.
> So feel free to add my Tested-by tag to your revert. But please don't
> forget that James earned a Reported-by tag.
Thanks,
James
next prev parent reply other threads:[~2019-07-17 21:29 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
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 [this message]
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=1563398966.3438.5.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