Linux regressions report for mainline [2022-03-06]

Linux regressions report for mainline [2022-03-06]

[Regzbot (on behalf of Thorsten Leemhuis)]

Hi Linus, Thorsten here, with a quick preface before the latest report
from regzbot.

From my side things seem to look normal right now; quite a few
regressions got fixed in the past few days. I (and thus regzbot) are
only aware of two regressions remaining that got introduced this cycle
(at least one of them pretty special); I didn't add those build problems
from Guenter to the tracking: he seems to look after those quite well
already (I need to talk to him if he want's me to track them, but I
didn't get around to do that).

Sadly I'm guess there are some regressions out there which I and regzbot
are not aware of. Hopefully more people will at least CC the regressions
mailing list (regressions@lists.linux.dev) on regressions reports in the
future (and/or get regzbot involved themselves), as that ensures I'll
get aware of them.

Ciao, Thorsten

---

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

Currently I'm aware of 15 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.16.. aka v5.17-rc), culprit identified
========================================================


Follow-up error for the commit fixing "PCIe regression on APM Merlin (aarch64 dev platform) preventing NVME initialization"
---------------------------------------------------------------------------------------------------------------------------
https://linux-regtracking.leemhuis.info/regzbot/regression/Yf2wTLjmcRj+AbDv@xps13.dannf/
https://lore.kernel.org/stable/Yf2wTLjmcRj%2BAbDv@xps13.dannf/

By dann frazier, 29 days ago; 7 activities, latest 23 days ago; poked 13 days ago.
Introduced in c7a75d07827a (v5.17-rc1)


====================================================
current cycle (v5.16.. aka v5.17-rc), unkown culprit
====================================================


net: bluetooth: qualcom and intel adapters, unable to reliably connect to bluetooth devices
-------------------------------------------------------------------------------------------
https://linux-regtracking.leemhuis.info/regzbot/regression/CAJCQCtSeUtHCgsHXLGrSTWKmyjaQDbDNpP4rb0i+RE+L2FTXSA@mail.gmail.com/
https://lore.kernel.org/linux-bluetooth/CAJCQCtSeUtHCgsHXLGrSTWKmyjaQDbDNpP4rb0i%2BRE%2BL2FTXSA@mail.gmail.com/

By Chris Murphy, 23 days ago; 47 activities, latest 3 days ago.
Introduced in v5.16..f1baf68e1383 (v5.16..v5.17-rc4)

Fix incoming:
* https://lore.kernel.org/regressions/1686eb5f-7484-8ec2-8564-84fe04bf6a70@leemhuis.info/


=========================================================================================
previous cycle (v5.15..v5.16), culprit identified, with activity in the past three months
=========================================================================================


drm: fb_helper:  Build failure of mainline kernel with qcom_defconfig
---------------------------------------------------------------------
https://linux-regtracking.leemhuis.info/regzbot/regression/YhofdlzadzRmy7tj@debian/
https://lore.kernel.org/lkml/YhofdlzadzRmy7tj@debian/

By Sudip Mukherjee, 8 days ago; 10 activities, latest 2 days ago.
Introduced in 9d6366e743f3 (v5.16-rc1)

Fix incoming:
* drm/panel: Select DRM_DP_HELPER for DRM_PANEL_EDP
  https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=master&id=eea89dff4c39a106f98d1cb5e4d626f8c63908b9


net: wireless: rtl8723bs (SDIO) - Access point mode causes a kernel panic
-------------------------------------------------------------------------
https://linux-regtracking.leemhuis.info/regzbot/regression/d58625ad-6f3e-a7d7-b5b4-d18eb16f4082@leemhuis.info/
https://lore.kernel.org/regressions/d58625ad-6f3e-a7d7-b5b4-d18eb16f4082@leemhuis.info/

By José Ángel Pastrana, 35 days ago; 3 activities, latest 2 days ago.
Introduced in 54659ca026e5 (v5.16-rc1)

Fix incoming:
* staging: rtl8723bs: Fix access-point mode deadlock
  https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=master&id=8f4347081be32e67b0873827e0138ab0fdaaf450


bluetooth: HSP/HFP mSBC profile broken with QCA6174
---------------------------------------------------
https://linux-regtracking.leemhuis.info/regzbot/regression/bug-215576-62941@https.bugzilla.kernel.org//
https://lore.kernel.org/linux-bluetooth/bug-215576-62941@https.bugzilla.kernel.org%2F/

By bugzilla-daemon@kernel.org, 27 days ago; 11 activities, latest 7 days ago.
Introduced in b2af264ad3af (v5.16-rc1)

2 patch postings are associated with this regression, the latest is this:
* [Bug 215576] HSP/HFP mSBC profile broken with QCA6174
  https://lore.kernel.org/linux-bluetooth/bug-215576-62941-2nprEl3omz@https.bugzilla.kernel.org%2F/
  15 days ago, by bugzilla-daemon@kernel.org

Noteworthy links:
* https://bugzilla.kernel.org/show_bug.cgi?id=215576


==================================================================================
older cycles (..v5.15), culprit identified, with activity in the past three months
==================================================================================


mtd: cfi_cmdset_0002: flash write accesses on the hardware fail on a PowerPC MPC8313 to a 8-bit-parallel S29GL064N flash
------------------------------------------------------------------------------------------------------------------------
https://linux-regtracking.leemhuis.info/regzbot/regression/b687c259-6413-26c9-d4c9-b3afa69ea124@pengutronix.de/
https://lore.kernel.org/lkml/b687c259-6413-26c9-d4c9-b3afa69ea124@pengutronix.de/

By Ahmad Fatoum, 83 days ago; 16 activities, latest 0 days ago.
Introduced in dfeae1073583 (v4.18-rc1)

Recent activities from: Tokunori Ikegami (3), Ahmad Fatoum (1), Vignesh
  Raghavendra (1)

2 patch postings are associated with this regression, the latest is this:
* [PATCH v2] mtd: cfi_cmdset_0002: Use chip_ready() for write on S29GL064N
  https://lore.kernel.org/stable/20220306153213.411425-1-ikegami.t@gmail.com/
  0 days ago, by Tokunori Ikegami; thread monitored.

Noteworthy links:
* [PATCH] mtd: cfi_cmdset_0002: Use chip_ready() for write on S29GL064N
  https://lore.kernel.org/stable/20220214182011.8493-1-ikegami.t@gmail.com/
  20 days ago, by Tokunori Ikegami; thread monitored.


[ *NEW* ] memory corruption on Atmel SAMA5D31
---------------------------------------------
https://linux-regtracking.leemhuis.info/regzbot/regression/13c6c9a2-6db5-c3bf-349b-4c127ad3496a@axentia.se/
https://lore.kernel.org/lkml/13c6c9a2-6db5-c3bf-349b-4c127ad3496a@axentia.se/

By Peter Rosin, 3 days ago; 10 activities, latest 1 days ago.
Introduced in f9aa460672c9 (v5.11-rc1)

Recent activities from: Peter Rosin (5), Saravana Kannan (3),
  Tudor.Ambarus@microchip.com (2)


btrfs: deadlocks in dedupe
--------------------------
https://linux-regtracking.leemhuis.info/regzbot/regression/20211210183456.GP17148@hungrycats.org/
https://lore.kernel.org/linux-btrfs/20211210183456.GP17148@hungrycats.org/

By Zygo Blaxell, 86 days ago; 15 activities, latest 16 days ago; poked 0 days ago.
Introduced in 3078d85c9a10 (v5.11-rc1)


gpio: some GPIO lines have stopped working
------------------------------------------
https://linux-regtracking.leemhuis.info/regzbot/regression/20211217153555.9413-1-marcelo.jimenez@gmail.com/
https://lore.kernel.org/stable/20211217153555.9413-1-marcelo.jimenez@gmail.com/

By Marcelo Roberto Jimenez, 79 days ago; 19 activities, latest 17 days ago; poked 2 days ago.
Introduced in 2ab73c6d8323 (v5.7-rc1)

One patch associated with this regression:
* Patch "ARM: dts: gpio-ranges property is now required" has been added to the 5.4-stable tree
  https://lore.kernel.org/linux-arm-kernel/16432993096685@kroah.com/
  38 days ago, by gregkh@linuxfoundation.org


drm: amdgpu: Too-low frequency limit for AMD GPU PCI-passed-through to Windows VM
---------------------------------------------------------------------------------
https://linux-regtracking.leemhuis.info/regzbot/regression/87ee57c8fu.fsf@turner.link/
https://lore.kernel.org/lkml/87ee57c8fu.fsf@turner.link/

By James D. Turner, 48 days ago; 19 activities, latest 18 days ago; poked 0 days ago.
Introduced in f9b7f3703ff9 (v5.14-rc1)


Intel TGL notebook no longer enters power states deeper than PC2
----------------------------------------------------------------
https://linux-regtracking.leemhuis.info/regzbot/regression/34eb9d46-d937-fc29-02b1-7cfb9162f9b8@leemhuis.info/
https://lore.kernel.org/regressions/34eb9d46-d937-fc29-02b1-7cfb9162f9b8@leemhuis.info/

By MarcelHB, 45 days ago; 19 activities, latest 24 days ago.
Introduced in e5ad96f388b7 (v5.15-rc1)

One patch associated with this regression:
* Re: [PATCH] nvme/pci: default to simple suspend
  https://lore.kernel.org/linux-nvme/20220207160655.GB635727@dhcp-10-100-145-180.wdc.com/
  27 days ago, by Keith Busch

Noteworthy links:
* https://bugzilla.kernel.org/show_bug.cgi?id=215467
* [Bug] nvme blocks PC10 since v5.15 - bisected
  https://lore.kernel.org/lkml/CAJZ5v0hvvYedSn5u-i7sjpoEHU4P65t7i1b2pVn=S1q0nHWgqQ@mail.gmail.com/
  44 days ago, by Rafael J. Wysocki; thread monitored.
* [PATCH] nvme/pci: default to simple suspend
  https://lore.kernel.org/linux-nvme/20220201165006.3074615-1-kbusch@kernel.org/
  33 days ago, by Keith Busch; thread monitored.


=============================================================================
older cycles (..v5.15), unkown culprit, with activity in the past three weeks
=============================================================================


Regression in workingset_refault latency on 5.15
------------------------------------------------
https://linux-regtracking.leemhuis.info/regzbot/regression/CA+wXwBSyO87ZX5PVwdHm-=dBjZYECGmfnydUicUyrQqndgX2MQ@mail.gmail.com/
https://lore.kernel.org/linux-mm/CA%2BwXwBSyO87ZX5PVwdHm-=dBjZYECGmfnydUicUyrQqndgX2MQ@mail.gmail.com/

By Daniel Dao, 11 days ago; 49 activities, latest 1 days ago.
Introduced in v3.0..v5.15.19

Recent activities from: Shakeel Butt (11), Ivan Babrou (8), Michal
  Koutný (3), Andrew Morton (1), Frank Hofmann (1), Michal Hocko (1)

8 patch postings are associated with this regression, the latest is this:
* + memcg-sync-flush-only-if-periodic-flush-is-delayed.patch added to -mm tree
  https://lore.kernel.org/stable/20220304235350.5043FC340E9@smtp.kernel.org/
  1 days ago, by Andrew Morton; thread monitored.

Noteworthy links:
* [PATCH] memcg: async flush memcg stats from perf sensitive codepaths
  https://lore.kernel.org/stable/20220226002412.113819-1-shakeelb@google.com/
  8 days ago, by Shakeel Butt; thread monitored.
* [PATCH] memcg: sync flush only if periodic flush is delayed
  https://lore.kernel.org/stable/20220304184040.1304781-1-shakeelb@google.com/
  2 days ago, by Shakeel Butt; thread monitored.


cifs: Failure to access cifs mount of samba share after resume from sleep
-------------------------------------------------------------------------
https://linux-regtracking.leemhuis.info/regzbot/regression/CAFrh3J9soC36+BVuwHB=g9z_KB5Og2+p2_W+BBoBOZveErz14w@mail.gmail.com/
https://lore.kernel.org/linux-cifs/CAFrh3J9soC36%2BBVuwHB=g9z_KB5Og2%2Bp2_W%2BBBoBOZveErz14w@mail.gmail.com/

By Satadru Pramanik, 7 days ago; 10 activities, latest 2 days ago.
Introduced in v5.16.11..v5.17-rc5

Recent activities from: Satadru Pramanik (6), Shyam Prasad N (2), Steve
  French (1)


md: unable to handle page fault while running badblocks (fsck.ext4 -c) on a raid5 md array
------------------------------------------------------------------------------------------
https://linux-regtracking.leemhuis.info/regzbot/regression/53e7de78-4d27-5089-f159-0d443b354666@leemhuis.info/
https://lore.kernel.org/lkml/53e7de78-4d27-5089-f159-0d443b354666@leemhuis.info/

By Dominik Mierzejewski, 12 days ago; 4 activities, latest 2 days ago.
Introduced in v5.13..v5.14.10

Recent activities from: Song Liu (2), Dominik Mierzejewski (1)

Noteworthy links:
* https://bugzilla.kernel.org/show_bug.cgi?id=215605


====================================================================
all others with unkown culprit and activity in the past three months
====================================================================


backlight: Intel_backlight does not work after updating from 5.10.89 to latest 5.15.17
--------------------------------------------------------------------------------------
https://linux-regtracking.leemhuis.info/regzbot/regression/74ee2216-a295-c2b6-328b-3e6d0cc1847e@leemhuis.info/
https://lore.kernel.org/regressions/74ee2216-a295-c2b6-328b-3e6d0cc1847e@leemhuis.info/

By Filippo Falezza, 34 days ago; 1 activities, latest 34 days ago.
Introduced in v5.10.89..v5.15.17

Noteworthy links:
* https://bugzilla.kernel.org/show_bug.cgi?id=215553


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

All regressions marked '[ *NEW* ]' were added since the previous report,
which can be found here:
https://lore.kernel.org/r/164598944963.346832.10219407090470852309@leemhuis.info

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@lists.linux.dev 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@klaava.Helsinki.FI/

Re: Linux regressions report for mainline [2022-03-06]

[Linus Torvalds]

On Sun, Mar 6, 2022 at 11:58 AM Regzbot (on behalf of Thorsten
Leemhuis) <regressions@leemhuis.info> wrote:
>
> ========================================================
> current cycle (v5.16.. aka v5.17-rc), culprit identified
> ========================================================
>
> Follow-up error for the commit fixing "PCIe regression on APM Merlin (aarch64 dev platform) preventing NVME initialization"
> ---------------------------------------------------------------------------------------------------------------------------
> https://linux-regtracking.leemhuis.info/regzbot/regression/Yf2wTLjmcRj+AbDv@xps13.dannf/
> https://lore.kernel.org/stable/Yf2wTLjmcRj%2BAbDv@xps13.dannf/
>
> By dann frazier, 29 days ago; 7 activities, latest 23 days ago; poked 13 days ago.
> Introduced in c7a75d07827a (v5.17-rc1)

Hmm. The culprit may be identified, but it looks like we don't have a
fix for it, so this may be one of those "left for later" things. It
being Xgene, there's a limited number of people who care, I'm afraid.

Alternatively, maybe 6dce5aa59e0b ("PCI: xgene: Use inbound resources
for setup") should just be reverted as broken?

> ====================================================
> current cycle (v5.16.. aka v5.17-rc), unknown culprit
> ====================================================
>
>
> net: bluetooth: qualcom and intel adapters, unable to reliably connect to bluetooth devices
> -------------------------------------------------------------------------------------------
> https://linux-regtracking.leemhuis.info/regzbot/regression/CAJCQCtSeUtHCgsHXLGrSTWKmyjaQDbDNpP4rb0i+RE+L2FTXSA@mail.gmail.com/
> https://lore.kernel.org/linux-bluetooth/CAJCQCtSeUtHCgsHXLGrSTWKmyjaQDbDNpP4rb0i%2BRE%2BL2FTXSA@mail.gmail.com/
>
> By Chris Murphy, 23 days ago; 47 activities, latest 3 days ago.
> Introduced in v5.16..f1baf68e1383 (v5.16..v5.17-rc4)
>
> Fix incoming:
> * https://lore.kernel.org/regressions/1686eb5f-7484-8ec2-8564-84fe04bf6a70@leemhuis.info/

That's a recent fix, it seems to be only in the bluetooth tree right
now, and won't be in rc7. I'm hoping that I'll get it in next week's
networking dump.

Cc'ing the right people just to prod them, since we've had much too
many "Oh, I didn't even realize it was a regression" issues this time
around.

                       Linus

Re: Linux regressions report for mainline [2022-03-06]

[Thorsten Leemhuis]

On 06.03.22 22:33, Linus Torvalds wrote:
> On Sun, Mar 6, 2022 at 11:58 AM Regzbot (on behalf of Thorsten
> Leemhuis) <regressions@leemhuis.info> wrote:
>>
>> ========================================================
>> current cycle (v5.16.. aka v5.17-rc), culprit identified
>> ========================================================
>>
>> Follow-up error for the commit fixing "PCIe regression on APM Merlin (aarch64 dev platform) preventing NVME initialization"
>> ---------------------------------------------------------------------------------------------------------------------------
>> https://linux-regtracking.leemhuis.info/regzbot/regression/Yf2wTLjmcRj+AbDv@xps13.dannf/
>> https://lore.kernel.org/stable/Yf2wTLjmcRj%2BAbDv@xps13.dannf/
>>
>> By dann frazier, 29 days ago; 7 activities, latest 23 days ago; poked 13 days ago.
>> Introduced in c7a75d07827a (v5.17-rc1)
> 
> Hmm. The culprit may be identified, but it looks like we don't have a
> fix for it, so this may be one of those "left for later" things. It
> being Xgene, there's a limited number of people who care, I'm afraid.
> 
> Alternatively, maybe 6dce5aa59e0b ("PCI: xgene: Use inbound resources
> for setup") should just be reverted as broken?

I don't care much, I just hope someone once again will look into this,
as this (and the previous) regression are on my list for quite a while
already and process once again seems to have slowed down. :-/

>> ====================================================
>> current cycle (v5.16.. aka v5.17-rc), unknown culprit
>> ====================================================
>>
>>
>> net: bluetooth: qualcom and intel adapters, unable to reliably connect to bluetooth devices
>> -------------------------------------------------------------------------------------------
>> https://linux-regtracking.leemhuis.info/regzbot/regression/CAJCQCtSeUtHCgsHXLGrSTWKmyjaQDbDNpP4rb0i+RE+L2FTXSA@mail.gmail.com/
>> https://lore.kernel.org/linux-bluetooth/CAJCQCtSeUtHCgsHXLGrSTWKmyjaQDbDNpP4rb0i%2BRE%2BL2FTXSA@mail.gmail.com/
>>
>> By Chris Murphy, 23 days ago; 47 activities, latest 3 days ago.
>> Introduced in v5.16..f1baf68e1383 (v5.16..v5.17-rc4)
>>
>> Fix incoming:
>> * https://lore.kernel.org/regressions/1686eb5f-7484-8ec2-8564-84fe04bf6a70@leemhuis.info/
> 
> That's a recent fix, it seems to be only in the bluetooth tree right
> now, and won't be in rc7. I'm hoping that I'll get it in next week's
> networking dump.

You will, it afaics already got merged into the right branch already:
https://lore.kernel.org/all/164637060982.7623.2431046217416492091.git-patchwork-notify@kernel.org/

It just came slightly too late for the last pull into the net. The same
had happened a week earlier with regression fixes, that's why I already
brought this up:

https://lore.kernel.org/netdev/37349299-c47b-1f67-2229-78ae9b9b4488@leemhuis.info/

Short story: things should hopefully improve soon.

BTW: @bluetooth maintainers, I noticed your -next branch is in next, but
your -fixes branch
git://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth.git is
not. Is that on purpose? Some (many?) of the other trees downstream to
the net tree have both their -fixes and their -next branches included
there regularly.

> Cc'ing the right people just to prod them, since we've had much too
> many "Oh, I didn't even realize it was a regression" issues this time
> around.

Yeah, since I started regression tracking again I noticed that quite a
few regressions fixes are merged quite slowly because maintainers put
them in their -next branches instead of sending them towards mainline
within a few days. I always try to make the maintainers aware of this
when I noticed it. That already helped a little afaics, but there is
more work ahead of me afaics...

Ciao, Thorsten

Re: Linux regressions report for mainline [2022-03-06]

[Rob Herring]

On Mon, Mar 7, 2022 at 1:32 AM Thorsten Leemhuis
<regressions@leemhuis.info> wrote:
>
> On 06.03.22 22:33, Linus Torvalds wrote:
> > On Sun, Mar 6, 2022 at 11:58 AM Regzbot (on behalf of Thorsten
> > Leemhuis) <regressions@leemhuis.info> wrote:
> >>
> >> ========================================================
> >> current cycle (v5.16.. aka v5.17-rc), culprit identified
> >> ========================================================
> >>
> >> Follow-up error for the commit fixing "PCIe regression on APM Merlin (aarch64 dev platform) preventing NVME initialization"
> >> ---------------------------------------------------------------------------------------------------------------------------
> >> https://linux-regtracking.leemhuis.info/regzbot/regression/Yf2wTLjmcRj+AbDv@xps13.dannf/
> >> https://lore.kernel.org/stable/Yf2wTLjmcRj%2BAbDv@xps13.dannf/
> >>
> >> By dann frazier, 29 days ago; 7 activities, latest 23 days ago; poked 13 days ago.
> >> Introduced in c7a75d07827a (v5.17-rc1)

Actually, it was introduced over a year ago in 6dce5aa59e0b. It was
fixed in c7a75d07827a for XGene2, but that *further* broke XGene1
which was just reported this cycle.

> > Hmm. The culprit may be identified, but it looks like we don't have a
> > fix for it, so this may be one of those "left for later" things. It
> > being Xgene, there's a limited number of people who care, I'm afraid.
> >
> > Alternatively, maybe 6dce5aa59e0b ("PCI: xgene: Use inbound resources
> > for setup") should just be reverted as broken?
>
> I don't care much, I just hope someone once again will look into this,
> as this (and the previous) regression are on my list for quite a while
> already and process once again seems to have slowed down. :-/

It's going to take some more debug patches from me as what's been
tried so far didn't work and I'm not ready to give up and revert this
cleanup.

Rob

Re: Linux regressions report for mainline [2022-03-06]

[Thorsten Leemhuis]

On 07.03.22 14:34, Rob Herring wrote:
> On Mon, Mar 7, 2022 at 1:32 AM Thorsten Leemhuis
> <regressions@leemhuis.info> wrote:
>>
>> On 06.03.22 22:33, Linus Torvalds wrote:
>>> On Sun, Mar 6, 2022 at 11:58 AM Regzbot (on behalf of Thorsten
>>> Leemhuis) <regressions@leemhuis.info> wrote:
>>>>
>>>> ========================================================
>>>> current cycle (v5.16.. aka v5.17-rc), culprit identified
>>>> ========================================================
>>>>
>>>> Follow-up error for the commit fixing "PCIe regression on APM Merlin (aarch64 dev platform) preventing NVME initialization"
>>>> ---------------------------------------------------------------------------------------------------------------------------
>>>> https://linux-regtracking.leemhuis.info/regzbot/regression/Yf2wTLjmcRj+AbDv@xps13.dannf/
>>>> https://lore.kernel.org/stable/Yf2wTLjmcRj%2BAbDv@xps13.dannf/
>>>>
>>>> By dann frazier, 29 days ago; 7 activities, latest 23 days ago; poked 13 days ago.
>>>> Introduced in c7a75d07827a (v5.17-rc1)
> Actually, it was introduced over a year ago in 6dce5aa59e0b. It was
> fixed in c7a75d07827a for XGene2, but that *further* broke XGene1
> which was just reported this cycle.

Many thx for the clarification, I'll update the regzbot entry
accordingly and..

>>> Hmm. The culprit may be identified, but it looks like we don't have a
>>> fix for it, so this may be one of those "left for later" things. It
>>> being Xgene, there's a limited number of people who care, I'm afraid.
>>>
>>> Alternatively, maybe 6dce5aa59e0b ("PCI: xgene: Use inbound resources
>>> for setup") should just be reverted as broken?
>>
>> I don't care much, I just hope someone once again will look into this,
>> as this (and the previous) regression are on my list for quite a while
>> already and process once again seems to have slowed down. :-/
> 
> It's going to take some more debug patches from me as what's been
> tried so far didn't work and I'm not ready to give up and revert this
> cleanup.

...will mark it as "on backburner" then, which stands for "get it out of
sight, but don't forget about this completely".

Ciao, Thorsten

Re: Linux regressions report for mainline [2022-03-06]

[Kalle Valo]

"Regzbot (on behalf of Thorsten Leemhuis)" <regressions@leemhuis.info>
writes:
> net: wireless: rtl8723bs (SDIO) - Access point mode causes a kernel panic
> -------------------------------------------------------------------------
> https://linux-regtracking.leemhuis.info/regzbot/regression/d58625ad-6f3e-a7d7-b5b4-d18eb16f4082@leemhuis.info/
> https://lore.kernel.org/regressions/d58625ad-6f3e-a7d7-b5b4-d18eb16f4082@leemhuis.info/
>
> By José Ángel Pastrana, 35 days ago; 3 activities, latest 2 days ago.
> Introduced in 54659ca026e5 (v5.16-rc1)
>
> Fix incoming:
> * staging: rtl8723bs: Fix access-point mode deadlock
>   https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=master&id=8f4347081be32e67b0873827e0138ab0fdaaf450

Just a small wish for the future, no need to change this report, but for
staging drivers it would be good use "staging:" instead of "wireless:"
in the title. This makes it easier for people to see that this is a
staging driver, not a normal wireless driver.

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

Re: Linux regressions report for mainline [2022-03-06]

[Thorsten Leemhuis]

On 09.03.22 09:34, Kalle Valo wrote:
> "Regzbot (on behalf of Thorsten Leemhuis)" <regressions@leemhuis.info>
> writes:
>> net: wireless: rtl8723bs (SDIO) - Access point mode causes a kernel panic
>> -------------------------------------------------------------------------
>> https://linux-regtracking.leemhuis.info/regzbot/regression/d58625ad-6f3e-a7d7-b5b4-d18eb16f4082@leemhuis.info/
>> https://lore.kernel.org/regressions/d58625ad-6f3e-a7d7-b5b4-d18eb16f4082@leemhuis.info/
>>
>> By José Ángel Pastrana, 35 days ago; 3 activities, latest 2 days ago.
>> Introduced in 54659ca026e5 (v5.16-rc1)
>>
>> Fix incoming:
>> * staging: rtl8723bs: Fix access-point mode deadlock
>>   https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=master&id=8f4347081be32e67b0873827e0138ab0fdaaf450
> 
> Just a small wish for the future, no need to change this report, but for
> staging drivers it would be good use "staging:" instead of "wireless:"
> in the title. This makes it easier for people to see that this is a
> staging driver, not a normal wireless driver.

Yeah, sorry about that, that is actually what I would do normally, but
seems for some reason I got it wrong here.

BTW, for anybody who cares: Jakub had a good idea to handle the "which
subsystem is this about" way better (in short: by checking which lists
are CCed), but I currently lack time to implement that. :-/

Ciao, Thorsten