Hi Linus, here is the weekly regressions report. Everything normal at
this point and nothing worth highlighting. Except maybe one thing:
* A fix for bogus lockdep warning in network driver stmmac that started
to happen in 6.8 is not making no progress, despite a Reviewed-by: from
Eric and some prodding from my side more than 10 days ago:
https://lore.kernel.org/lkml/[email protected]/
But well, it's "just" a lockdep warning, so it's not really urgent.
Ciao, Thorsten
---
Hi, this is regzbot, the Linux kernel regression tracking bot.
Currently I'm aware of 7 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 (v6.8.. aka v6.9-rc), culprit identified
======================================================
[ *NEW* ] PWM vibrator does not probe with v6.9-rc1
---------------------------------------------------
https://linux-regtracking.leemhuis.info/regzbot/regression/lore/[email protected]/
https://lore.kernel.org/lkml/[email protected]/
By Karel Balej; 2 days ago; 5 activities, latest 2 days ago.
Introduced in 40ade0c2e794 (v6.9-rc1)
Recent activities from: Uwe Kleine-König (2), Karel Balej (2), Linux
regression tracking (Thorsten Leemhuis) (1)
One patch associated with this regression:
* [PATCH] pwm: Fix setting period with #pwm-cells = <1> and of_pwm_single_xlate()
https://lore.kernel.org/lkml/[email protected]/
2 days ago, by Uwe Kleine-König
mm: vmalloc: persistent "spinlock bad magic" message when booting s390 images with spinlock debugging enabled
-------------------------------------------------------------------------------------------------------------
https://linux-regtracking.leemhuis.info/regzbot/regression/lore/[email protected]/
https://lore.kernel.org/lkml/[email protected]/
By Guenter Roeck; 8 days ago; 4 activities, latest 2 days ago.
Introduced in 72210662c5a2 (v6.9-rc1)
Fix incoming:
* mm: vmalloc: bail out early in find_vmap_area() if vmap is not init
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=master&id=eefa71fa900336d7c9173a8ec3ce75af68f484ec
mainline boot regression on AMD Stoney Ridge Chromebooks
--------------------------------------------------------
https://linux-regtracking.leemhuis.info/regzbot/regression/lore/[email protected]/
https://lore.kernel.org/lkml/[email protected]/
By Laura Nao; 8 days ago; 3 activities, latest 3 days ago.
Introduced in c749ce393b (v6.9-rc1)
Recent activities from: Laura Nao (2)
[ *NEW* ] Framework Laptop 13 AMD suspend/wakeup regression with 6.9rc1
-----------------------------------------------------------------------
https://linux-regtracking.leemhuis.info/regzbot/regression/bugzilla.kernel.org/218641/
https://bugzilla.kernel.org/show_bug.cgi?id=218641
https://lore.kernel.org/lkml/[email protected]/
By David Markey and David Markey; 5 days ago; 6 activities, latest 4 days ago.
Introduced in 7ee988770326 (v6.9-rc1)
Recent activities from: David Markey (3), Mario Limonciello (AMD) (2),
anna-maria (1)
One patch associated with this regression:
* bugzilla.kernel.org, issue 218641: new comment (#4) with patch
https://bugzilla.kernel.org/show_bug.cgi?id=218641#c4
5 days ago, by Mario Limonciello (AMD)
[ *NEW* ] Re: [PATCH v4 2/8] clk: qcom: gdsc: Enable supply reglator in GPU GX handler
--------------------------------------------------------------------------------------
https://linux-regtracking.leemhuis.info/regzbot/regression/lore/[email protected]/
https://lore.kernel.org/lkml/[email protected]/
By Johan Hovold; 8 days ago; 12 activities, latest 5 days ago.
Introduced in 9187ebb954ab (v6.9-rc1)
Recent activities from: Johan Hovold (6), Mark Brown (2), Konrad
Dybcio (1), Dmitry Baryshkov (1), Bjorn Andersson (1)
3 patch postings are associated with this regression, the latest is this:
* [PATCH 4/5] clk: qcom: gpucc-sc8280xp: fix GX external supply lookup [implicit due to Link/Closes tag]
https://lore.kernel.org/lkml/20240326140108.21307-5-johan%[email protected]/
5 days ago, by Johan Hovold; thread monitored.
Noteworthy links:
* [PATCH] clk: qcom: gdsc: treat optional supplies as optional [implicit due to Link/Closes tag]
https://lore.kernel.org/lkml/20240325081957.10946-1-johan%[email protected]/
6 days ago, by Johan Hovold; thread monitored.
* [PATCH] clk: qcom: gdsc: treat optional supplies as optional [implicit due to Link/Closes tag]
https://lore.kernel.org/lkml/20240325085835.26158-1-johan%[email protected]/
6 days ago, by Johan Hovold; thread monitored.
Re: [PATCH] fs: Remove NTFS classic
-----------------------------------
https://linux-regtracking.leemhuis.info/regzbot/regression/lore/[email protected]/
https://lore.kernel.org/linux-fsdevel/[email protected]/
By Johan Hovold; 8 days ago; 8 activities, latest 6 days ago.
Introduced in 7ffa8f3d3023 (v6.9-rc1)
Recent activities from: Christian Brauner (5), Johan Hovold (2)
2 patch postings are associated with this regression, the latest is this:
* [PATCH 2/2] ntfs3: remove warning
https://lore.kernel.org/linux-fsdevel/20240325-faucht-kiesel-82c6c35504b3@brauner/
6 days ago, by Christian Brauner
===================================================
current cycle (v6.8.. aka v6.9-rc), unknown culprit
===================================================
[ *NEW* ] bluetooth: oops during init in btintel_read_debug_features
--------------------------------------------------------------------
https://linux-regtracking.leemhuis.info/regzbot/regression/lore/[email protected]/
https://lore.kernel.org/lkml/[email protected]/
By Thorsten Leemhuis; 5 days ago; 2 activities, latest 3 days ago.
Introduced in v6.8..v6.9-rc1
Fix incoming:
* Bluetooth: hci_sync: Fix not checking error on hci_cmd_sync_cancel_sync
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=master&id=1c3366abdbe884be62e5a7502b4db758aa3974c6
=============
End of report
=============
All regressions marked '[ *NEW* ]' were added since the previous report,
which can be found here:
https://lore.kernel.org/r/[email protected]
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
[email protected] 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/[email protected]/