Linux regressions report for mainline [2022-09-18]

[Regzbot (on behalf of Thorsten Leemhuis)]

Hi Linus! Below is a slightly edited report from regzbot listing all
regression from this cycle that the bot and I are currently aware of.

Many of the regressions I have been tracking that were introduced this
cycle got resolved in the last week or two. There is just one that
likely will be addressed by the network folks soon, and two that were
reported in the past few days that need to be looked at closer by
developers or reporters.

HTH, Ciao, Thorsten

---

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

Currently I'm aware of 48 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.19.. aka v6.0-rc), culprit identified
=======================================================


[ *NEW* ] Graphical issues on Lenovo Yoga 7 14ARB7 laptop since v6.0-rc1 (bisected)
-----------------------------------------------------------------------------------
https://linux-regtracking.leemhuis.info/regzbot/regression/c1f8886a-5624-8f49-31b1-e42b6d20dcf5@xxxxxxxxxxxxxxxxxx/
https://lore.kernel.org/lkml/c1f8886a-5624-8f49-31b1-e42b6d20dcf5@xxxxxxxxxxxxxxxxxx/

By August Wikerfors; 1 days ago; 1 activities, latest 1 days ago.
Introduced in 7cc191ee7621 (v6.0-rc1)

Recent activities from: August Wikerfors (1)


[ *NEW* ] introduced in 5.10.140 causes drives to drop from LSI SAS controller (Bisected to 6d17a112e9a63ff6a5edffd1676b99e0ffbcd269)
-------------------------------------------------------------------------------------------------------------------------------------
https://linux-regtracking.leemhuis.info/regzbot/regression/CADy0EvLGJmZe-x9wzWSB6+tDKNuLHd8Km3J5MiWWYQRR2ctS3A@xxxxxxxxxxxxxx/
https://lore.kernel.org/stable/CADy0EvL2XuWTjUdWHUHTpW3ZYaLWn0ftR-nUBioUqh-n-N=dXQ@xxxxxxxxxxxxxx/

By Jason Wittlin-Cohen and Jason Wittlin-Cohen; 3 days ago; 3 activities, latest 3 days ago.
Introduced in 6d17a112e9a6 (v6.0-rc3)

Recent activities from: Greg KH (1), Bart Van Assche (1), Jason Wittlin-
  Cohen (1)


[ *NEW* ] net: fec: backtrace: BUG: sleeping function called from invalid context at drivers/clk/imx/clk-pllv3.c
----------------------------------------------------------------------------------------------------------------
https://linux-regtracking.leemhuis.info/regzbot/regression/20220914145317.GA1868385@xxxxxxxxxxxx/
https://lore.kernel.org/netdev/20220914145317.GA1868385@xxxxxxxxxxxx/

By Guenter Roeck; 4 days ago; 19 activities, latest 4 days ago.
Introduced in b353b241f1eb (v6.0-rc5)

Recent activities from: Marc Kleine-Budde (6), Francesco Dolcini (5),
  Bence Csókás (3), Csókás Bence (2), Andrew Lunn (2), Guenter Roeck (1)

4 patch postings are associated with this regression, the latest is this:
* Re: [PATCH 1/2] Revert "net: fec: Use a spinlock to guard `fep->ptp_clk_on`"
  https://lore.kernel.org/netdev/20220912103818.j2u6afz66tcxvnr6@xxxxxxxxxxxxxx/
  6 days ago, by Marc Kleine-Budde

Noteworthy links:
* [PATCH net 0/2] Revert fec PTP changes
  https://lore.kernel.org/lkml/20220912070143.98153-1-francesco.dolcini@xxxxxxxxxxx/
  6 days ago, by Francesco Dolcini; thread monitored.
* [PATCH 1/2] Revert "net: fec: Use a spinlock to guard `fep->ptp_clk_on`"
  https://lore.kernel.org/netdev/20220912073106.2544207-1-bence98@xxxxxxxxxx/
  6 days ago, by Bence Csókás; thread monitored.


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

All regressions marked '[ *NEW* ]' were added since the previous report,
which can be found here:
https://lore.kernel.org/r/166231521235.1982292.2102689915618920245@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/