[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Mon, 9 Sep 2019 13:24:49 +0300
From: Alexander Kapshuk <alexander.kapshuk@...il.com>
To: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: Daniel Vetter <daniel@...ll.ch>, dri-devel@...ts.freedesktop.org,
linux-kernel <linux-kernel@...r.kernel.org>,
Linux-Next <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
On Mon, Sep 9, 2019 at 1:21 PM Stephen Rothwell <sfr@...b.auug.org.au> wrote:
>
> Hi,
>
> On Mon, 9 Sep 2019 20:11:59 +1000 Stephen Rothwell <sfr@...b.auug.org.au> wrote:
> >
> > 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).
>
> Actually (since you won't be bisecting the latest linux-next), you
> probably want to use
>
> git merge-base stable next-20190903
> (or whatever linux-next you are bisecting)
>
> as your first good commit (assuming it id good :-)).
>
> --
> Cheers,
> Stephen Rothwell
Hi Stephen,
Thanks very much for the tips.
I'll go ahead and give those a try.
Powered by blists - more mailing lists