Linux regressions report for mainline [2022-03-06]

From: Regzbot (on behalf of Thorsten Leemhuis)
Date: Sun Mar 06 2022 - 14:59:02 EST

Hi Linus, Thorsten here, with a quick preface before the latest report
from regzbot.

>From my side things seem to look normal right now; quite a few
regressions got fixed in the past few days. I (and thus regzbot) are
only aware of two regressions remaining that got introduced this cycle
(at least one of them pretty special); I didn't add those build problems
from Guenter to the tracking: he seems to look after those quite well
already (I need to talk to him if he want's me to track them, but I
didn't get around to do that).

Sadly I'm guess there are some regressions out there which I and regzbot
are not aware of. Hopefully more people will at least CC the regressions
mailing list (regressions@xxxxxxxxxxxxxxx) on regressions reports in the
future (and/or get regzbot involved themselves), as that ensures I'll
get aware of them.

Ciao, Thorsten

---

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

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

https://linux-regtracking.leemhuis.info/regzbot/mainline/

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


========================================================
current cycle (v5.16.. aka v5.17-rc), culprit identified
========================================================


Follow-up error for the commit fixing "PCIe regression on APM Merlin (aarch64 dev platform) preventing NVME initialization"
---------------------------------------------------------------------------------------------------------------------------
https://linux-regtracking.leemhuis.info/regzbot/regression/Yf2wTLjmcRj+AbDv@xps13.dannf/
https://lore.kernel.org/stable/Yf2wTLjmcRj%2BAbDv@xps13.dannf/

By dann frazier, 29 days ago; 7 activities, latest 23 days ago; poked 13 days ago.
Introduced in c7a75d07827a (v5.17-rc1)


====================================================
current cycle (v5.16.. aka v5.17-rc), unkown culprit
====================================================


net: bluetooth: qualcom and intel adapters, unable to reliably connect to bluetooth devices
-------------------------------------------------------------------------------------------
https://linux-regtracking.leemhuis.info/regzbot/regression/CAJCQCtSeUtHCgsHXLGrSTWKmyjaQDbDNpP4rb0i+RE+L2FTXSA@xxxxxxxxxxxxxx/
https://lore.kernel.org/linux-bluetooth/CAJCQCtSeUtHCgsHXLGrSTWKmyjaQDbDNpP4rb0i%2BRE%2BL2FTXSA@xxxxxxxxxxxxxx/

By Chris Murphy, 23 days ago; 47 activities, latest 3 days ago.
Introduced in v5.16..f1baf68e1383 (v5.16..v5.17-rc4)

Fix incoming:
* https://lore.kernel.org/regressions/1686eb5f-7484-8ec2-8564-84fe04bf6a70@xxxxxxxxxxxxx/


=========================================================================================
previous cycle (v5.15..v5.16), culprit identified, with activity in the past three months
=========================================================================================


drm: fb_helper: Build failure of mainline kernel with qcom_defconfig
---------------------------------------------------------------------
https://linux-regtracking.leemhuis.info/regzbot/regression/YhofdlzadzRmy7tj@debian/
https://lore.kernel.org/lkml/YhofdlzadzRmy7tj@debian/

By Sudip Mukherjee, 8 days ago; 10 activities, latest 2 days ago.
Introduced in 9d6366e743f3 (v5.16-rc1)

Fix incoming:
* drm/panel: Select DRM_DP_HELPER for DRM_PANEL_EDP
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=master&id=eea89dff4c39a106f98d1cb5e4d626f8c63908b9


net: wireless: rtl8723bs (SDIO) - Access point mode causes a kernel panic
-------------------------------------------------------------------------
https://linux-regtracking.leemhuis.info/regzbot/regression/d58625ad-6f3e-a7d7-b5b4-d18eb16f4082@xxxxxxxxxxxxx/
https://lore.kernel.org/regressions/d58625ad-6f3e-a7d7-b5b4-d18eb16f4082@xxxxxxxxxxxxx/

By José Ángel Pastrana, 35 days ago; 3 activities, latest 2 days ago.
Introduced in 54659ca026e5 (v5.16-rc1)

Fix incoming:
* staging: rtl8723bs: Fix access-point mode deadlock
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=master&id=8f4347081be32e67b0873827e0138ab0fdaaf450


bluetooth: HSP/HFP mSBC profile broken with QCA6174
---------------------------------------------------
https://linux-regtracking.leemhuis.info/regzbot/regression/bug-215576-62941@xxxxxxxxxxxxxxxxxxxxxxxxx//
https://lore.kernel.org/linux-bluetooth/bug-215576-62941@xxxxxxxxxxxxxxxxxxxxxxxxx%2F/

By bugzilla-daemon@xxxxxxxxxx, 27 days ago; 11 activities, latest 7 days ago.
Introduced in b2af264ad3af (v5.16-rc1)

2 patch postings are associated with this regression, the latest is this:
* [Bug 215576] HSP/HFP mSBC profile broken with QCA6174
https://lore.kernel.org/linux-bluetooth/bug-215576-62941-2nprEl3omz@xxxxxxxxxxxxxxxxxxxxxxxxx%2F/
15 days ago, by bugzilla-daemon@xxxxxxxxxx

Noteworthy links:
* https://bugzilla.kernel.org/show_bug.cgi?id=215576


==================================================================================
older cycles (..v5.15), culprit identified, with activity in the past three months
==================================================================================


mtd: cfi_cmdset_0002: flash write accesses on the hardware fail on a PowerPC MPC8313 to a 8-bit-parallel S29GL064N flash
------------------------------------------------------------------------------------------------------------------------
https://linux-regtracking.leemhuis.info/regzbot/regression/b687c259-6413-26c9-d4c9-b3afa69ea124@xxxxxxxxxxxxxx/
https://lore.kernel.org/lkml/b687c259-6413-26c9-d4c9-b3afa69ea124@xxxxxxxxxxxxxx/

By Ahmad Fatoum, 83 days ago; 16 activities, latest 0 days ago.
Introduced in dfeae1073583 (v4.18-rc1)

Recent activities from: Tokunori Ikegami (3), Ahmad Fatoum (1), Vignesh
Raghavendra (1)

2 patch postings are associated with this regression, the latest is this:
* [PATCH v2] mtd: cfi_cmdset_0002: Use chip_ready() for write on S29GL064N
https://lore.kernel.org/stable/20220306153213.411425-1-ikegami.t@xxxxxxxxx/
0 days ago, by Tokunori Ikegami; thread monitored.

Noteworthy links:
* [PATCH] mtd: cfi_cmdset_0002: Use chip_ready() for write on S29GL064N
https://lore.kernel.org/stable/20220214182011.8493-1-ikegami.t@xxxxxxxxx/
20 days ago, by Tokunori Ikegami; thread monitored.


[ *NEW* ] memory corruption on Atmel SAMA5D31
---------------------------------------------
https://linux-regtracking.leemhuis.info/regzbot/regression/13c6c9a2-6db5-c3bf-349b-4c127ad3496a@xxxxxxxxxx/
https://lore.kernel.org/lkml/13c6c9a2-6db5-c3bf-349b-4c127ad3496a@xxxxxxxxxx/

By Peter Rosin, 3 days ago; 10 activities, latest 1 days ago.
Introduced in f9aa460672c9 (v5.11-rc1)

Recent activities from: Peter Rosin (5), Saravana Kannan (3),
Tudor.Ambarus@xxxxxxxxxxxxx (2)


btrfs: deadlocks in dedupe
--------------------------
https://linux-regtracking.leemhuis.info/regzbot/regression/20211210183456.GP17148@xxxxxxxxxxxxxx/
https://lore.kernel.org/linux-btrfs/20211210183456.GP17148@xxxxxxxxxxxxxx/

By Zygo Blaxell, 86 days ago; 15 activities, latest 16 days ago; poked 0 days ago.
Introduced in 3078d85c9a10 (v5.11-rc1)


gpio: some GPIO lines have stopped working
------------------------------------------
https://linux-regtracking.leemhuis.info/regzbot/regression/20211217153555.9413-1-marcelo.jimenez@xxxxxxxxx/
https://lore.kernel.org/stable/20211217153555.9413-1-marcelo.jimenez@xxxxxxxxx/

By Marcelo Roberto Jimenez, 79 days ago; 19 activities, latest 17 days ago; poked 2 days ago.
Introduced in 2ab73c6d8323 (v5.7-rc1)

One patch associated with this regression:
* Patch "ARM: dts: gpio-ranges property is now required" has been added to the 5.4-stable tree
https://lore.kernel.org/linux-arm-kernel/16432993096685@xxxxxxxxx/
38 days ago, by gregkh@xxxxxxxxxxxxxxxxxxx


drm: amdgpu: Too-low frequency limit for AMD GPU PCI-passed-through to Windows VM
---------------------------------------------------------------------------------
https://linux-regtracking.leemhuis.info/regzbot/regression/87ee57c8fu.fsf@xxxxxxxxxxx/
https://lore.kernel.org/lkml/87ee57c8fu.fsf@xxxxxxxxxxx/

By James D. Turner, 48 days ago; 19 activities, latest 18 days ago; poked 0 days ago.
Introduced in f9b7f3703ff9 (v5.14-rc1)


Intel TGL notebook no longer enters power states deeper than PC2
----------------------------------------------------------------
https://linux-regtracking.leemhuis.info/regzbot/regression/34eb9d46-d937-fc29-02b1-7cfb9162f9b8@xxxxxxxxxxxxx/
https://lore.kernel.org/regressions/34eb9d46-d937-fc29-02b1-7cfb9162f9b8@xxxxxxxxxxxxx/

By MarcelHB, 45 days ago; 19 activities, latest 24 days ago.
Introduced in e5ad96f388b7 (v5.15-rc1)

One patch associated with this regression:
* Re: [PATCH] nvme/pci: default to simple suspend
https://lore.kernel.org/linux-nvme/20220207160655.GB635727@xxxxxxxxxxxxxxxxxxxxxxxxxxx/
27 days ago, by Keith Busch

Noteworthy links:
* https://bugzilla.kernel.org/show_bug.cgi?id=215467
* [Bug] nvme blocks PC10 since v5.15 - bisected
https://lore.kernel.org/lkml/CAJZ5v0hvvYedSn5u-i7sjpoEHU4P65t7i1b2pVn=S1q0nHWgqQ@xxxxxxxxxxxxxx/
44 days ago, by Rafael J. Wysocki; thread monitored.
* [PATCH] nvme/pci: default to simple suspend
https://lore.kernel.org/linux-nvme/20220201165006.3074615-1-kbusch@xxxxxxxxxx/
33 days ago, by Keith Busch; thread monitored.


=============================================================================
older cycles (..v5.15), unkown culprit, with activity in the past three weeks
=============================================================================


Regression in workingset_refault latency on 5.15
------------------------------------------------
https://linux-regtracking.leemhuis.info/regzbot/regression/CA+wXwBSyO87ZX5PVwdHm-=dBjZYECGmfnydUicUyrQqndgX2MQ@xxxxxxxxxxxxxx/
https://lore.kernel.org/linux-mm/CA%2BwXwBSyO87ZX5PVwdHm-=dBjZYECGmfnydUicUyrQqndgX2MQ@xxxxxxxxxxxxxx/

By Daniel Dao, 11 days ago; 49 activities, latest 1 days ago.
Introduced in v3.0..v5.15.19

Recent activities from: Shakeel Butt (11), Ivan Babrou (8), Michal
Koutný (3), Andrew Morton (1), Frank Hofmann (1), Michal Hocko (1)

8 patch postings are associated with this regression, the latest is this:
* + memcg-sync-flush-only-if-periodic-flush-is-delayed.patch added to -mm tree
https://lore.kernel.org/stable/20220304235350.5043FC340E9@xxxxxxxxxxxxxxx/
1 days ago, by Andrew Morton; thread monitored.

Noteworthy links:
* [PATCH] memcg: async flush memcg stats from perf sensitive codepaths
https://lore.kernel.org/stable/20220226002412.113819-1-shakeelb@xxxxxxxxxx/
8 days ago, by Shakeel Butt; thread monitored.
* [PATCH] memcg: sync flush only if periodic flush is delayed
https://lore.kernel.org/stable/20220304184040.1304781-1-shakeelb@xxxxxxxxxx/
2 days ago, by Shakeel Butt; thread monitored.


cifs: Failure to access cifs mount of samba share after resume from sleep
-------------------------------------------------------------------------
https://linux-regtracking.leemhuis.info/regzbot/regression/CAFrh3J9soC36+BVuwHB=g9z_KB5Og2+p2_W+BBoBOZveErz14w@xxxxxxxxxxxxxx/
https://lore.kernel.org/linux-cifs/CAFrh3J9soC36%2BBVuwHB=g9z_KB5Og2%2Bp2_W%2BBBoBOZveErz14w@xxxxxxxxxxxxxx/

By Satadru Pramanik, 7 days ago; 10 activities, latest 2 days ago.
Introduced in v5.16.11..v5.17-rc5

Recent activities from: Satadru Pramanik (6), Shyam Prasad N (2), Steve
French (1)


md: unable to handle page fault while running badblocks (fsck.ext4 -c) on a raid5 md array
------------------------------------------------------------------------------------------
https://linux-regtracking.leemhuis.info/regzbot/regression/53e7de78-4d27-5089-f159-0d443b354666@xxxxxxxxxxxxx/
https://lore.kernel.org/lkml/53e7de78-4d27-5089-f159-0d443b354666@xxxxxxxxxxxxx/

By Dominik Mierzejewski, 12 days ago; 4 activities, latest 2 days ago.
Introduced in v5.13..v5.14.10

Recent activities from: Song Liu (2), Dominik Mierzejewski (1)

Noteworthy links:
* https://bugzilla.kernel.org/show_bug.cgi?id=215605


====================================================================
all others with unkown culprit and activity in the past three months
====================================================================


backlight: Intel_backlight does not work after updating from 5.10.89 to latest 5.15.17
--------------------------------------------------------------------------------------
https://linux-regtracking.leemhuis.info/regzbot/regression/74ee2216-a295-c2b6-328b-3e6d0cc1847e@xxxxxxxxxxxxx/
https://lore.kernel.org/regressions/74ee2216-a295-c2b6-328b-3e6d0cc1847e@xxxxxxxxxxxxx/

By Filippo Falezza, 34 days ago; 1 activities, latest 34 days ago.
Introduced in v5.10.89..v5.15.17

Noteworthy links:
* https://bugzilla.kernel.org/show_bug.cgi?id=215553


=============
End of report
=============

All regressions marked '[ *NEW* ]' were added since the previous report,
which can be found here:
https://lore.kernel.org/r/164598944963.346832.10219407090470852309@xxxxxxxxxxxxx

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:

https://gitlab.com/knurd42/regzbot/-/blob/main/docs/getting_started.md
https://gitlab.com/knurd42/regzbot/-/blob/main/docs/reference.md

The short version: if you see a regression report you want to see
tracked, just send a reply to the report where you Cc
regressions@xxxxxxxxxxxxxxx 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.:

Link: https://lore.kernel.org/all/30th.anniversary.repost@xxxxxxxxxxxxxxxxxx/