Kernel panic during drm/nouveau init 5.3.0-rc7-next-20190903
sfr at canb.auug.org.au
Mon Sep 9 10:11:59 UTC 2019
On Sun, 8 Sep 2019 17:13:07 +0300 Alexander Kapshuk <alexander.kapshuk at gmail.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).
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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 488 bytes
Desc: OpenPGP digital signature
More information about the dri-devel