Linux regressions report for mainline [2024-01-21]

[Regzbot (on behalf of Thorsten Leemhuis)]

Hi Linus. I kept a loose eye on a handful of regressions introduced
during the merge window, but all except a build problem Guenter reported
already got resolved (and Guenter's will likely soon be addressed as
well). I wish we'd be as fast when it comes to regressions that are only
noticed once a proper mainline release is out. Speaking of which:

* Quite a few people reported problems due to a mm change that made it
into 6.7 three days before its release: efa7df3e3bb5 ("mm: align larger
anonymous mappings on THP boundaries"). It among others "breaks 32bit
processes on x86_64 (at least). In particular, 32bit kernel or firefox
builds in our build system." as Jiri noted. For details and other
problems reported see:

  https://lore.kernel.org/linux-mm/d0a136a0-4a31-46bc-adf4-2db109a61672@xxxxxxxxxx/
  https://lore.kernel.org/linux-mm/CAJuCfpHXLdQy1a2B6xN2d7quTYwg2OoZseYPZTRpU0eHHKD-sQ@xxxxxxxxxxxxxx/
  https://lore.kernel.org/all/1e8f5ac7-54ce-433a-ae53-81522b2320e1@xxxxxxx/
  https://lore.kernel.org/all/a914c7f2-cf9f-44a8-99d4-c25a66d39f1c@xxxxxxx/

  A patch that fixes at least Jiri's problem is up for review:
https://lore.kernel.org/all/20240118180505.2914778-1-shy828301@xxxxxxxxx/

  Hope that fix reaches you soon.

* BTW a quick TWIMC: ath11k is crashing during suspend on v6.7; a fix
exists and hopefully will reach mainline next week:

  https://git.kernel.org/pub/scm/linux/kernel/git/wireless/wireless.git/commit/?id=556857aa1d0855aba02b1c63bc52b91ec63fc2cc

  Sadly lacks a stable tag. I sometimes wish they were mandatory in
cases like this to ensure this the fix makes it to the latest latest
stable series. But whatever, under the current circumstances this it's
not that bad as 6.6.y is a longterm branch.

Ciao, Thorsten

---

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

Currently I'm aware of 1 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.7.. aka v6.7-post), culprit identified
========================================================


[ *NEW* ] spi: qemu emulations quanta-q71l-bmc and almetto-bmc fail to boot
---------------------------------------------------------------------------
https://linux-regtracking.leemhuis.info/regzbot/regression/lore/3d3a11b1-8396-4d8e-9bb3-61ecb67e7efa@xxxxxxxxxxxx/
https://lore.kernel.org/lkml/3d3a11b1-8396-4d8e-9bb3-61ecb67e7efa@xxxxxxxxxxxx/

By Guenter Roeck; 8 days ago; 5 activities, latest 0 days ago.
Introduced in 4d8ff6b0991d

Recent activities from: Guenter Roeck (3), Mark Brown (2)


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

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