From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Huacai Chen <chenhuacai@loongson.cn>,
Bjorn Helgaas <bhelgaas@google.com>,
jiaxun.yang@flygoat.com, Aurelien Jarno <aurel32@debian.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Regressions <regressions@lists.linux.dev>,
Linux PCI <linux-pci@vger.kernel.org>,
Linux Loongarch <loongarch@lists.linux.dev>
Subject: Fwd: PCI: Loongson: 8b3517f88ff2 breaks PCIe on some system
Date: Sun, 23 Jul 2023 09:03:03 +0700 [thread overview]
Message-ID: <871f22f4-c456-db15-3466-085971bd1221@gmail.com> (raw)
Hi,
I notice a regression report on Bugzilla [1]. Quoting from it:
> After 8b3517f88ff2 ("PCI: loongson: Prevent LS7A MRRS increases") backported to stable, we have received multiple regression reports including one from Debian build farm[1] that some systems failed to initialize some PCIe devices.
>
> I was able to reproduce on one of my Loongson-3A4000+7A system. It seems like the root cause is firmware on those systems didn't set MRRS properly but 8b3517f88ff2 ("PCI: loongson: Prevent LS7A MRRS increases") assumed firmware's maximum MRRS is always valid.
>
> [1]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035587
See Bugzilla for the full thread.
The linked Debian BTS entry have debugging details on this regression
(boot log, cpuinfo, and lspci).
Anyway, I'm adding this regression to regzbot:
#regzbot introduced: 8b3517f88ff298 https://bugzilla.kernel.org/show_bug.cgi?id=217680
#regzbot title: LS7A MRRS quirk fails to initialize PCIe devices
#regzbot link: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035587
Thanks.
[1]: https://bugzilla.kernel.org/show_bug.cgi?id=217680
--
An old man doll... just what I always wanted! - Clara
next reply other threads:[~2023-07-23 2:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-23 2:03 Bagas Sanjaya [this message]
2023-07-23 11:13 ` Fwd: PCI: Loongson: 8b3517f88ff2 breaks PCIe on some system 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=871f22f4-c456-db15-3466-085971bd1221@gmail.com \
--to=bagasdotme@gmail.com \
--cc=aurel32@debian.org \
--cc=bhelgaas@google.com \
--cc=chenhuacai@loongson.cn \
--cc=jiaxun.yang@flygoat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=loongarch@lists.linux.dev \
--cc=regressions@lists.linux.dev \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).