Linux regressions report for mainline [2022-11-13]

[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.

3 of the tracked regressions were just reported in the past 3 days.

The fourth issue ("drm: amdgpu: some games hang at start") looks
stalled, will inquiry tomorrow what's up there; maybe I just missed a
patch to fix this (should have done that on Friday, sorry :-/ ).

HTH, Ciao, Thorsten

---

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

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


[ *NEW* ] usb: devices are not powered anymore and sometimes reset
------------------------------------------------------------------
https://linux-regtracking.leemhuis.info/regzbot/regression/fd0f2d56-495e-6fdd-d1e8-ff40b558101e@xxxxxxxxxx/
https://lore.kernel.org/linux-usb/fd0f2d56-495e-6fdd-d1e8-ff40b558101e@xxxxxxxxxx/

By Peter Rosin; 0 days ago; 1 activities, latest 0 days ago.
Introduced in bf7571c00dca (v6.1-rc1)

Recent activities from: Peter Rosin (1)


[ *NEW* ] drm: msm: DSI controller being switched off before the panel unprepare hook is called
-----------------------------------------------------------------------------------------------
https://linux-regtracking.leemhuis.info/regzbot/regression/1892d0af-8aa4-dc03-887a-e44bb623b836@xxxxxxxxxx/
https://lore.kernel.org/dri-devel/1892d0af-8aa4-dc03-887a-e44bb623b836@xxxxxxxxxx/

By Caleb Connolly; 2 days ago; 2 activities, latest 0 days ago.
Introduced in 007ac0262b0d (v6.1-rc1)

Recent activities from: Dmitry Baryshkov (1), Caleb Connolly (1)


[ *NEW* ] drm: amdgpu: No payload for [MST PORT:0000000006da5d29] found in mst state 00000000b0e556d6" on system resume with TBT dock connected.
------------------------------------------------------------------------------------------------------------------------------------------------
https://linux-regtracking.leemhuis.info/regzbot/regression/ghwn827862.fsf@xxxxxxxxxxx/
https://lore.kernel.org/lkml/ghwn827862.fsf@xxxxxxxxxxx/
https://gitlab.freedesktop.org/drm/amd/-/issues/2171

By Dirk Gouders and Unkown; 2 days ago; 3 activities, latest 1 days ago.
Introduced in 4d07b0bc4034 (v6.1-rc1)

Recent activities from: Dirk Gouders (2), Lyude Paul (1)


drm: amdgpu: some games (Cyberpunk 2077, Forza Horizon 4/5) hang at start
-------------------------------------------------------------------------
https://linux-regtracking.leemhuis.info/regzbot/regression/CABXGCsOeQ7VYm98jRVaYp6KaNsFVsAnSb33ZT8JvZxcTcEGW0w@xxxxxxxxxxxxxx/
https://lore.kernel.org/lkml/CABXGCsOeQ7VYm98jRVaYp6KaNsFVsAnSb33ZT8JvZxcTcEGW0w@xxxxxxxxxxxxxx/

By Mikhail Gavrilov; 23 days ago; 8 activities, latest 11 days ago.
Introduced in dd80d9c8eeca (v6.1-rc1)


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

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