All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Adam Edge <baronedge@protonmail.com>
Cc: "stable@vger.kernel.org" <stable@vger.kernel.org>,
	"regressions@lists.linux.dev" <regressions@lists.linux.dev>
Subject: Re: Regression after 5.7.19 causing major freezes on CPU loads
Date: Tue, 15 Jun 2021 08:01:15 +0200	[thread overview]
Message-ID: <YMhCK8x7R4TbnLAF@kroah.com> (raw)
In-Reply-To: <HnYKcqmY_z0ERb5qOOUauOLY1vt6nxuKHXzuKVrZ297elyqtzpsWTrjUUnlIDG7mQUYnJMfS8HkFceFMf0Fd_GLzOMghgf4btNt9YhwwZK0=@protonmail.com>

On Mon, Jun 14, 2021 at 07:21:55PM +0000, Adam Edge wrote:
> Hello,
> 
> After I've upgraded from 5.7.11 (didn't have access to this machine for
> about 10 months) to 5.12.10, I've noticed that anytime I used all my
> cores to, for example, compile a project, the system would degrade
> significantly in performance and applications would start to stutter.
> Compiles are also about 3-4x slower on kernels with the regression vs.
> without. After debugging this for the past 24 hours or so, I've narrowed
> it down to a change between 5.7.19 and 5.8.1. Sadly, bisect does not
> help, because trying to run any of the 5.8 RC kernels causes the kernel
> to be stuck before init, without any apparent errors on the screen (and
> I don't have a serial cable to dump the kernel output to). I'm listing
> all the information I know and my system information below.
> 
> Reproduction steps (dunno if this helps, but):
> 1. Boot with kernel with the regression
> 2. Do something that uses all cores, like compiling the Linux kernel
> 3. Observe long compile times and stuttering applications (which doesn't
> happen even on full load with a working kernel)
> 
> Regression between kernel versions:
> 5.7 - working
> 5.7.11 - working
> 5.7.19 - working
> 5.8.1 - broken
> 5.8.18 - broken
> 5.12.10 - broken
> 8ecfa36cd4db3275bf3b6c6f32c7e3c6bb537de2 (master on 2021-06-13) - broken

Can you use 'git bisect' to track down the commit that caused the
problem?

thanks,

greg k-h

  reply	other threads:[~2021-06-15  6:01 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 [this message]
2021-06-15  6:13   ` Adam Edge
2021-06-15  6:17     ` Greg KH
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=YMhCK8x7R4TbnLAF@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 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.