archive mirror
 help / color / mirror / Atom feed
From: Thorsten Leemhuis <>
To: Linus Torvalds <>,
	"" <>
Cc: "Song Liu" <>,
	"Jens Axboe" <>,, "Mario Limonciello" <>,
	"Alex Deucher" <>,
	"Christian König" <>,
	"Pan, Xinhui" <>,
	"Linux Kernel Mailing List" <>
Subject: Special regressions report for the pending 5.16 release
Date: Fri, 7 Jan 2022 11:59:05 +0100	[thread overview]
Message-ID: <> (raw)

Hi Linus,

a quick brief manual regressions report, as I assume you'll likely
release 5.16 soon and thus might find this helpful. Below is a list of
remaining regressions in 5.16-rc I'm currently aware of.

regressions where a fix exists


* This fix afaics is not yet mainlined:

[PATCH] md/raid1: fix missing bitmap update w/o WriteMostly devices

But I'm pretty sure Jens (CCed) will send it onwards soon:

* There is an open regression "Applications that need amdgpu doesn't run
after waking up from suspend":

Wolfram (CCed) plans to revert a i2c commit to fix it, but I'm not sure
if he plans to send in onwards for 5.16 (or if that would be a good idea
at all):

* There are suspend and resume problems related to amdgpu:

Mario (CCed) recently found the root cause and came up with a fix, but
it likely needs a little more time to bake:

no fix in sight


 * screen contents do get restored after some input events (so it
doesn't stay blank).

(related: )

Alex (CCed) is trying hard to find a fix for, but afaics needs more time.

Need more time to analyse


I'm aware of two more reports that afaics need (a lot?) more time to

 * suspend issues for a user that faces another regression that might

 * 5-10% increase in IO latencies with nohz balance patch

Closing words


HTH, ciao, Thorsten

             reply	other threads:[~2022-01-07 10:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-07 10:59 Thorsten Leemhuis [this message]
2022-01-07 16:24 ` Deucher, Alexander
2022-01-07 16:30 ` Jens Axboe
2022-01-07 20:31 ` Wolfram Sang
2022-01-07 21:33 ` Linus Torvalds

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \ \ \ \ \
    --subject='Re: Special regressions report for the pending 5.16 release' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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).