[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180824141254.GB31555@kroah.com>
Date: Fri, 24 Aug 2018 16:12:54 +0200
From: Greg KH <gregkh@...uxfoundation.org>
To: "Matthias B." <matthias@...terdrache.de>
Cc: stable@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: How to report kernel panic in 4.4.x
On Fri, Aug 24, 2018 at 03:43:44PM +0200, Matthias B. wrote:
>
> On Fri, 24 Aug 2018 14:59:50 +0200
> Greg KH <gregkh@...uxfoundation.org> wrote:
>
> > It depends on what the panic looks like :)
> >
> > Any hints? You can post it here if you want.
>
> The attached image is everything I see on screen. Scrolling up does not
> work.
>
> >
> > Also, if you can run 'git bisect' to track it down to the commit that
> > causes the problem, that is even better, as we can cc: all of the
> > people on that patch to get help from.
>
> I can try.
> Which git repository and branch stores the 4.4.x kernel and which
> changeset/tag is the 4.4.147 kernel (which is the last one that works
> for me)?
All of the stable trees are here:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/
you want the linux-4.4.y branch to work off of.
All of the kernels releases are tagged, so you can start with v4.4.147
as the good entry for 'git bisect'.
thanks,
greg k-h
Powered by blists - more mailing lists