From: "Matthias B." <matthias@winterdrache.de>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: stable@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: How to report kernel panic in 4.4.x
Date: Fri, 24 Aug 2018 15:43:44 +0200 [thread overview]
Message-ID: <20180824154344.1c53a68c@ninja> (raw)
In-Reply-To: <20180824125950.GA29673@kroah.com>
[-- Attachment #1: Type: text/plain, Size: 653 bytes --]
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)?
MSB
--
A man without light need not fear darkness.
[-- Attachment #2: panic.jpg --]
[-- Type: image/jpeg, Size: 255079 bytes --]
next prev parent reply other threads:[~2018-08-24 17:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-24 12:24 How to report kernel panic in 4.4.x Matthias B.
2018-08-24 12:59 ` Greg KH
2018-08-24 13:43 ` Matthias B. [this message]
2018-08-24 14:12 ` Greg KH
2018-08-24 14:33 ` Matthias B.
2018-08-24 15:55 ` Greg KH
2018-08-24 16:19 ` Matthias B.
2018-08-24 16:19 ` Matthias B.
2018-08-24 19:18 ` Greg KH
2018-08-24 14:09 ` Matthias B.
2018-08-24 14:11 ` Greg KH
2018-08-24 14:24 ` Matthias B.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180824154344.1c53a68c@ninja \
--to=matthias@winterdrache.de \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.