From: Greg KH <gregkh@linuxfoundation.org>
To: Adam Edge <baronedge@protonmail.com>
Cc: "regressions@lists.linux.dev" <regressions@lists.linux.dev>,
"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: Regression after 5.7.19 causing major freezes on CPU loads
Date: Tue, 15 Jun 2021 08:17:51 +0200 [thread overview]
Message-ID: <YMhGDxrELFMrye9c@kroah.com> (raw)
In-Reply-To: <GUSUkWNwTxbgBsjYfpPEreYbwdu5JGec4XqJhWkFs8UncAWLJ9MdDIUvmZ0wYDLj8dFmEGcImo_fDBWte9QaFV2Yil6W7XLHlyXENv6vqd8=@protonmail.com>
On Tue, Jun 15, 2021 at 06:13:46AM +0000, Adam Edge wrote:
> On Tuesday, June 15th, 2021 at 6:01 AM, Greg KH <gregkh@linuxfoundation.org> wrote:
> > Can you use 'git bisect' to track down the commit that caused the
> > problem?
>
> As I have mentioned in my previous email, anytime I'm within the v5.8-rc*
> range of commits, running the kernel fails to get past a certain point
> at boot. init doesn't get executed, but SysRq keys work and I can reboot
> from there. Has this happened before? If there is an alternate method
> of getting the kernel debug logs for this (that doesn't involve a serial
> connection, as I don't have the equipment for that), I'm happy to get
> them for you.
That sounds like the offending commit is in that range, which is good,
you have narrowed it down.
Just use 'git bisect' to track down the place where this fails at,
that's all we want. No need to get a debug log yet, "failing to boot"
is a good sign something is going wrong :)
thanks,
greg k-h
next prev parent reply other threads:[~2021-06-15 6:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-14 19:21 Regression after 5.7.19 causing major freezes on CPU loads Adam Edge
2021-06-15 6:01 ` Greg KH
2021-06-15 6:13 ` Adam Edge
2021-06-15 6:17 ` Greg KH [this message]
2021-06-15 6:20 ` Adam Edge
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=YMhGDxrELFMrye9c@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=baronedge@protonmail.com \
--cc=regressions@lists.linux.dev \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).