archive mirror
 help / color / mirror / Atom feed
From: "Regzbot (on behalf of Thorsten Leemhuis)" <>
To: LKML <>,
	Linus Torvalds <>,
	Linux regressions mailing list <>
Subject: Linux regressions report  for mainline [2023-03-19]
Date: Sun, 19 Mar 2023 17:30:59 +0000	[thread overview]
Message-ID: <> (raw)

Hi Linus. The list of regressions from the 6.3 cycle I track is still
quite short. See below for details, but let me mention a few things:

A fix from Arnd for one of the build problems Guenter reported early
this cycle sadly doesn't make any progress since more than a month now;
I should have prodded here:

Another patch for one of Guenter build problems hopefully should sooner
or later go towards you with the btrfs updates:

The fix for the random warning backtraces in calls from ct_nmi_enter
Guenter reported in reply to 6.3-rc2 announcement is still in the works:

While at it let me briefly mentioned one 6.2 issue: a revert for a
change that causes a regression after a long review phase was accepted
by a maintainer and sent for merging to Mauro about two weeks ago – but
he afaics didn't pick it up yet and my prodding didn't help. #sigh Is
this a situation where you might be willing to help out?

Ciao, Thorsten


Hi, this is regzbot, the Linux kernel regression tracking bot.

Currently I'm aware of 4 regressions in linux-mainline. Find the
current status below and the latest on the web:

Bye bye, hope to see you soon for the next report.
   Regzbot (on behalf of Thorsten Leemhuis)

current cycle (v6.2.. aka v6.3-rc), culprit identified

[ *NEW* ] CPUIDLE_FLAG_RCU_IDLE, blk_mq_freeze_queue_wait() and slow-stuck reboots

By Alexey Klimov; 4 days ago; 5 activities, latest 2 days ago.
Introduced in 0c5ffc3d7b15 (v6.3-rc1)

Recent activities from: Alexey Klimov (3), Peter Zijlstra (1), Bart Van
  Assche (1)

2 patch postings are associated with this regression, the latest is this:
* Re: [REGRESSION] CPUIDLE_FLAG_RCU_IDLE, blk_mq_freeze_queue_wait() and slow-stuck reboots
  4 days ago, by Peter Zijlstra

Build failures for sparc64:allmodconfig and parisc:allmodconfig with gcc 11.x+

By Guenter Roeck; 25 days ago; 6 activities, latest 4 days ago.
Introduced in 1ec49744ba83 (v6.3-rc1)

Fix incoming:
* btrfs: fix compilation error on sparc/parisc

[ *NEW* ] arm: vfp: random Warning backtraces in calls from ct_nmi_enter()

By Guenter Roeck; 6 days ago; 15 activities, latest 5 days ago.
Introduced in 62b95a7b44d1 (v6.3-rc1)

Fix incoming:
* ARM: vfp: Fix broken softirq handling with instrumentation enabled

Build error in drivers/media/i2c/imx290.c if PM support is disabled

By Guenter Roeck; 19 days ago; 4 activities, latest 7 days ago.
Introduced in 02852c01f654 (v6.3-rc1)

Fix incoming:
* media: i2c: imx290: fix conditional function defintions

End of report

All regressions marked '[ *NEW* ]' were added since the previous report,
which can be found here:

Thanks for your attention, have a nice day!

  Regzbot, your hard working Linux kernel regression tracking robot

P.S.: Wanna know more about regzbot or how to use it to track regressions
for your subsystem? Then check out the getting started guide or the
reference documentation:

The short version: if you see a regression report you want to see
tracked, just send a reply to the report where you Cc with a line like this:

#regzbot introduced: v5.13..v5.14-rc1

If you want to fix a tracked regression, just do what is expected
anyway: add a 'Link:' tag with the url to the report, e.g.:


                 reply	other threads:[~2023-03-19 17:31 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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 \ \ \ \ \ \

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