regressions.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: "Regzbot (on behalf of Thorsten Leemhuis)" <regressions@leemhuis.info>
Cc: LKML <linux-kernel@vger.kernel.org>,
	 Linux regressions mailing list <regressions@lists.linux.dev>
Subject: Re: Linux regressions report for mainline [2022-01-09]
Date: Sun, 9 Jan 2022 11:20:36 -0800	[thread overview]
Message-ID: <CAHk-=wi8gSsM7-+fx-iSoKGHtgrgN==NcQtRikYfiFmv8gjbnQ@mail.gmail.com> (raw)
In-Reply-To: <164175418046.1037107.9730034714816887497@leemhuis.info>

On Sun, Jan 9, 2022 at 10:51 AM Regzbot (on behalf of Thorsten
Leemhuis) <regressions@leemhuis.info> wrote:
>
> 5-10% increase in IO latencies with nohz balance patch

This one is clearly not rootcaused, but even the reporter isn't sure
what triggered it.  It was bisected to that mentioned patch, but even
that bisection result isn't really entirely certain.

So this one will remain pending, I'm afraid.

> pm: laptop totally freezes when going to hibernation
> drm: amdgpu: s0ix suspend stopped working

Something clearly not great in amdgpu suspend/resume land. The reports
are not fully clear, with even the bisection being questionable.

But from the previous cycle reports:

> =========================================================================================
> previous cycle (v5.14..v5.15), culprit identified, with activity in the past three months
> =========================================================================================
>
> drm: amdgpu: NUC8i7HVKVA crashes during system suspend

This one isn't questionable, and Len sent me the revert he's been
using on his system for a long time. So I applied it.

Maybe it's related, maybe it's not.

             Linus

  reply	other threads:[~2022-01-09 19:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-09 18:50 Linux regressions report for mainline [2022-01-09] Regzbot (on behalf of Thorsten Leemhuis)
2022-01-09 19:20 ` Linus Torvalds [this message]
2022-01-09 19:46   ` Thorsten Leemhuis

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='CAHk-=wi8gSsM7-+fx-iSoKGHtgrgN==NcQtRikYfiFmv8gjbnQ@mail.gmail.com' \
    --to=torvalds@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=regressions@leemhuis.info \
    --cc=regressions@lists.linux.dev \
    /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).