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 14:59:50 +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: <20180824125950.GA29673@kroah.com>
References: <20180824142408.6340d052@ninja>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20180824142408.6340d052@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 02:24:08PM +0200, Matthias B. wrote:
> Hallo,
> 
> 4.4.147 is the last kernel of the 4.4.x series that boots for me. All
> subsequent versions panic on boot. How do I report this bug? 
> If I'm supposed to use https://bugzilla.kernel.org/ I don't know what
> to fill into the fields. I don't even know if the longterm kernel falls
> under "Mainline" or some other tree.

It depends on what the panic looks like :)

Any hints?  You can post it here if you want.

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.

thanks,

greg k-h