Linux regressions report for mainline [2022-07-17]

[Regzbot (on behalf of Thorsten Leemhuis)]

Hi Linus! Here is a quick summary of the regressions introduced this cycle
that I'm aware of. Not sure why Michael hasn't sent the virtio change to
avoid the troubles with VIRTIO_HARDEN_NOTIFICATION, will ask him tomorrow.

HTH, Ciao, Thorsten

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

Currently I'm aware of 22 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.18.. aka v5.19-rc), culprit identified
========================================================


[ *NEW* ] drm: i915: support for ADL-P GPUs requires updates GuC firmware files
-------------------------------------------------------------------------------
https://linux-regtracking.leemhuis.info/regzbot/regression/CAPM=9txdca1VnRpp-oNLXpBc2UWq3=ceeim5+Gw4N9tAriRY6A@xxxxxxxxxxxxxx/
https://lore.kernel.org/dri-devel/CAPM=9txdca1VnRpp-oNLXpBc2UWq3=ceeim5%2BGw4N9tAriRY6A@xxxxxxxxxxxxxx/

By Dave Airlie; 2 days ago; 6 activities, latest 0 days ago.
Introduced in 2584b3549f4c (v5.19-rc1)

Recent activities from: Patchwork (4), Daniele Ceraolo Spurio (1), Dave
  Airlie (1)

Noteworthy links:
* [PATCH] drm/i915/guc: support v69 in parallel to v70
  https://lore.kernel.org/dri-devel/20220715225451.1294354-1-daniele.ceraolospurio@xxxxxxxxx/
  1 days ago, by Daniele Ceraolo Spurio; thread monitored.


[ *NEW* ] [BUILD BUG] regression from certs: Move load_certificate_list() to be with the asymmetric keys code
-------------------------------------------------------------------------------------------------------------
https://linux-regtracking.leemhuis.info/regzbot/regression/20220712104554.408dbf42@xxxxxxxxxxxxxxxxxx/
https://lore.kernel.org/lkml/20220712104554.408dbf42@xxxxxxxxxxxxxxxxxx/

By Steven Rostedt; 5 days ago; 1 activities, latest 5 days ago.
Introduced in 60050ffe3d77 (v5.19-rc4)

Recent activities from: Steven Rostedt (1)


virtio_balloon regression in 5.19-rc3
-------------------------------------
https://linux-regtracking.leemhuis.info/regzbot/regression/64c567bc77c4fbe7bfe37467cc1c89d24a45c37a.camel@xxxxxxxxxxxxxxx/
https://lore.kernel.org/virtualization/64c567bc77c4fbe7bfe37467cc1c89d24a45c37a.camel@xxxxxxxxxxxxxxx/

By Ben Hutchings; 26 days ago; 22 activities, latest 7 days ago.
Introduced in 8b4ec69d7e09 (v5.19-rc1)

Fix incoming:
* virtio: VIRTIO_HARDEN_NOTIFICATION is broken
  https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=master&id=6a9720576cd00d30722c5f755bd17d4cfa9df636


====================================================
current cycle (v5.18.. aka v5.19-rc), unkown culprit
====================================================


[ *NEW* ] PM: hibernate: Sound Distortion on boot
-------------------------------------------------
https://linux-regtracking.leemhuis.info/regzbot/regression/46fd7a73-06fd-a8a0-8530-0ecf9b18c08d@xxxxxxxxxxxxxx/
https://lore.kernel.org/lkml/46fd7a73-06fd-a8a0-8530-0ecf9b18c08d@xxxxxxxxxxxxxx/

By Daniel Exner; 5 days ago; 5 activities, latest 3 days ago.
Introduced in v5.19-rc1..v5.19-rc4

Recent activities from: Thorsten Leemhuis (2), Daniel Exner (2), Dmitry
  Osipenko (1)

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

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