linux-kernel - Re: Kernel panic during drm/nouveau init 5.3.0-rc7-next-20190903

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 for Android: free password hash cracker in your pocket

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

Date:   Mon, 9 Sep 2019 20:11:59 +1000
From:   Stephen Rothwell <sfr@...b.auug.org.au>
To:     Alexander Kapshuk <alexander.kapshuk@...il.com>
Cc:     Daniel Vetter <daniel@...ll.ch>, dri-devel@...ts.freedesktop.org,
        linux-kernel@...r.kernel.org, linux-next@...r.kernel.org,
        maarten.lankhorst@...ux.intel.com, mripard@...nel.org,
        sean@...rly.run, airlied@...ux.ie
Subject: Re: Kernel panic during drm/nouveau init 5.3.0-rc7-next-20190903

Hi Alexander,

On Sun, 8 Sep 2019 17:13:07 +0300 Alexander Kapshuk <alexander.kapshuk@...il.com> wrote:
>
> This is my first bisect. Here's what I've tried so far and based on the
> output I got, I seem to be taken in the opposit direction.
> 
> git bisect start
> git bisect bad				# 7dc4585e0378:next-20190903
> git bisect good next-20190730	#70f4b4ac1655

If you are bisecting linux-next, I will suggest bisecting between the stable branch on linux-next (which is just Linus' tree when I started that day) and the top of the first linux-next that fails.  (Assuming that the stable branch is good).

so

git bisect start
git bisect good stable
git bisect bad next-20190903

and go from there.  It will (unfortunately) be quite a few commits to test
:-(

-- 
Cheers,
Stephen Rothwell

Content of type "application/pgp-signature" skipped