All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Souza, Jose" <jose.souza@intel.com>
To: "pebolle@tiscali.nl" <pebolle@tiscali.nl>,
	"James.Bottomley@HansenPartnership.com" 
	<James.Bottomley@HansenPartnership.com>,
	"intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>
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 19:32:31 +0000	[thread overview]
Message-ID: <a522eb05e65fe5068c519f0c2ce44d894a9526db.camel@intel.com> (raw)
In-Reply-To: <1562797129.3213.111.camel@HansenPartnership.com>

Hi James and Paul

Could you share a dmesg output of your system after the bug occur with
this kernel parameters "drm.debug=0x1e log_buf_len=4M"? Also the output
of /sys/kernel/debug/dri/0/i915_edp_psr_status

Thanks


On Wed, 2019-07-10 at 15:18 -0700, James Bottomley wrote:
> On Wed, 2019-07-10 at 23:59 +0200, Paul Bolle wrote:
> > James Bottomley schreef op wo 10-07-2019 om 10:35 [-0700]:
> > > I can get back to it this afternoon, when I'm done with the
> > > meeting
> > > requirements and doing other dev stuff.
> > 
> > I've started bisecting using your suggestion of that drm merge:
> >     $ git bisect log
> >     git bisect start
> >     # good: [89c3b37af87ec183b666d83428cb28cc421671a6] Merge
> > git://git.kernel.org/pub/scm/linux/kernel/git/davem/ide
> >     git bisect good 89c3b37af87ec183b666d83428cb28cc421671a6
> >     # bad: [a2d635decbfa9c1e4ae15cb05b68b2559f7f827c] Merge tag
> > 'drm-
> > next-2019-05-09' of git://anongit.freedesktop.org/drm/drm
> >     git bisect bad a2d635decbfa9c1e4ae15cb05b68b2559f7f827c
> >     # bad: [ad2c467aa92e283e9e8009bb9eb29a5c6a2d1217] drm/i915:
> > Update DRIVER_DATE to 20190417
> >     git bisect bad ad2c467aa92e283e9e8009bb9eb29a5c6a2d1217
> > 
> > Git told me I have nine steps after this. So at two hours per step
> > I
> > might
> > pinpoint the offending commit by Friday the 12th. If I'm lucky.
> > (There are
> > other things to do than bisecting this issue.)
> > 
> > If you find that commit before I do, I'll be all ears.
> 
> Sure ... I'm doing the holistic thing and looking at the tree in that
> branch.  It seems to consist of 7 i915 updates
> 
> c09d39166d8a3f3788680b32dbb0a40a70de32e2 DRIVER_DATE to 20190207
> 47ed55a9bb9e284d46d6f2489e32a53b59152809 DRIVER_DATE to 20190220
> f4ecb8ae70de86710e85138ce49af5c689951953 DRIVER_DATE to 20190311
> 1284ec985572232ace4817476baeb2d82b60be7a DRIVER_DATE to 20190320
> a01b2c6f47d86c7d1a9fa822b3b91ec233b61784 DRIVER_DATE to 20190328
> 28d618e9ab86f26a31af0b235ced55beb3e343c8 DRIVER_DATE to 20190404
> ad2c467aa92e283e9e8009bb9eb29a5c6a2d1217 DRIVER_DATE to 20190417
> 
> So I figured I'd see if I can locate the problem by bisection of
> those
> plus inspection.
> 
> James
> 
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2019-07-11 19:32 UTC|newest]

Thread overview: 52+ 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:32       ` James Bottomley
2019-07-10 16:45       ` Paul Bolle
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               ` Souza, Jose [this message]
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-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: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
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:28                   ` Souza, Jose
2019-07-11 23:40                   ` James Bottomley
2019-07-11 23:40                     ` James Bottomley
2019-07-12 14:19                     ` [Intel-gfx] " 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:03                           ` Souza, Jose
2019-07-15 21:34                           ` [Intel-gfx] " Paul Bolle
2019-07-15 21:34                             ` Paul Bolle
2019-07-16 16:32                             ` [Intel-gfx] " Souza, Jose
2019-07-16 16:32                               ` Souza, Jose
2019-07-17 21:27                               ` Paul Bolle
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:27                                       ` Souza, Jose
2019-07-24 20:39                                       ` [Intel-gfx] " Paul Bolle
2019-07-24 20:39                                         ` Paul Bolle
2019-07-24 20:42                                         ` Souza, Jose
2019-07-24 20:42                                           ` Souza, Jose
2019-08-09 17:16                                         ` 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=a522eb05e65fe5068c519f0c2ce44d894a9526db.camel@intel.com \
    --to=jose.souza@intel.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.