Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Date:   Fri, 24 Aug 2018 16:12:54 +0200
From:   Greg KH <gregkh@linuxfoundation.org>
To:     "Matthias B." <matthias@winterdrache.de>
Cc:     stable@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: How to report kernel panic in 4.4.x
Message-ID: <20180824141254.GB31555@kroah.com>
References: <20180824142408.6340d052@ninja>
 <20180824125950.GA29673@kroah.com>
 <20180824154344.1c53a68c@ninja>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20180824154344.1c53a68c@ninja>
User-Agent: Mutt/1.10.1 (2018-07-13)
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

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@linuxfoundation.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