linux-kernel - Re: screen freeze with 5.2-rc6 Dell XPS-13 skylake i915

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1562797129.3213.111.camel@HansenPartnership.com>
Date:   Wed, 10 Jul 2019 15:18:49 -0700
From:   James Bottomley <James.Bottomley@...senPartnership.com>
To:     Paul Bolle <pebolle@...cali.nl>, intel-gfx@...ts.freedesktop.org
Cc:     linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: screen freeze with 5.2-rc6 Dell XPS-13 skylake  i915

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