regressions.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Thorsten Leemhuis <regressions@leemhuis.info>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Marcel Holtmann <marcel@holtmann.org>,
	 Jakub Kicinski <kuba@kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	 Linux regressions mailing list <regressions@lists.linux.dev>,
	Netdev <netdev@vger.kernel.org>,
	 Linux PCI <linux-pci@vger.kernel.org>
Subject: Re: Linux regressions report for mainline [2022-03-06]
Date: Mon, 7 Mar 2022 07:34:50 -0600	[thread overview]
Message-ID: <CAL_JsqLHun+X4jMwTbVMmjjETfbP73j52XCwWBj9MJCkpQ41mA@mail.gmail.com> (raw)
In-Reply-To: <4a28b83b-37ef-1533-563a-39b66c5ff158@leemhuis.info>

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

  reply	other threads:[~2022-03-07 13:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-06 19:58 Regzbot (on behalf of Thorsten Leemhuis)
2022-03-06 21:33 ` Linus Torvalds
2022-03-07  7:31   ` Thorsten Leemhuis
2022-03-07 13:34     ` Rob Herring [this message]
2022-03-07 14:26       ` Thorsten Leemhuis
2022-03-09  8:34 ` Kalle Valo
2022-03-09  8:55   ` Thorsten Leemhuis

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAL_JsqLHun+X4jMwTbVMmjjETfbP73j52XCwWBj9MJCkpQ41mA@mail.gmail.com \
    --to=robh@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=marcel@holtmann.org \
    --cc=netdev@vger.kernel.org \
    --cc=regressions@leemhuis.info \
    --cc=regressions@lists.linux.dev \
    --cc=torvalds@linux-foundation.org \
    --subject='Re: Linux regressions report for mainline [2022-03-06]' \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).