mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Paul Bolle <pebolle@tiscali.nl>
To: James Bottomley <James.Bottomley@HansenPartnership.com>,
	intel-gfx@lists.freedesktop.org
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: screen freeze with 5.2-rc6 Dell XPS-13 skylake  i915
Date: Wed, 10 Jul 2019 23:59:11 +0200	[thread overview]
Message-ID: <a23e93d918f8be5aea4af0b87efbf9c3d143d2fb.camel@tiscali.nl> (raw)
In-Reply-To: <1562780135.3213.58.camel@HansenPartnership.com>

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.

Thanks,


Paul Bolle


  reply	other threads:[~2019-07-10 21:59 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 [this message]
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
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=a23e93d918f8be5aea4af0b87efbf9c3d143d2fb.camel@tiscali.nl \
    --to=pebolle@tiscali.nl \
    --cc=James.Bottomley@HansenPartnership.com \
    --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
all inboxes | Powered by JetHome®