From: Lukas Wunner <lukas@wunner.de>
To: sashiko-reviews@lists.linux.dev
Cc: Emmanuel Grumbach <emmanuel.grumbach@intel.com>,
linux-pci@vger.kernel.org
Subject: Re: [PATCH] PCI: Disable NoSnoop and Relaxed ordering for Intel wireless BE200
Date: Thu, 23 Jul 2026 08:47:40 +0200 [thread overview]
Message-ID: <amG5DN8sEetoZtvS@wunner.de> (raw)
In-Reply-To: <20260621071242.B20F31F000E9@smtp.kernel.org>
On Sun, Jun 21, 2026 at 07:12:42AM +0000, sashiko-bot@kernel.org wrote:
> > +++ b/drivers/pci/quirks.c
> > @@ -4674,6 +4674,13 @@ static void quirk_chelsio_T5_disable_root_port_attributes(struct pci_dev *pdev)
> > DECLARE_PCI_FIXUP_HEADER(PCI_VENDOR_ID_CHELSIO, PCI_ANY_ID,
> > quirk_chelsio_T5_disable_root_port_attributes);
> >
> > +/*
> > + * The Intel wireless BE200 fails to copy TLP Attributes from a Request to the
> > + * Completion it generates.
> > + */
> > +DECLARE_PCI_FIXUP_HEADER(PCI_VENDOR_ID_INTEL, 0x272b,
> > + quirk_disable_root_port_attributes);
>
> [Severity: High]
> Will this workaround survive a system suspend and resume cycle?
>
> When the Intel BE200 device is hotplugged, the upstream Root Port's
> configuration state is saved at boot time by pcie_portdrv_probe(), which calls
> pci_save_state(). The workaround modifies the Root Port's current
> configuration to disable Relaxed Ordering and No Snoop, but it does not update
> the Root Port's saved state array.
>
> Upon system suspend, the PCI core skips saving the Root Port's state because
> its state_saved flag is already true. During resume, pci_restore_state()
> restores the Root Port to its original boot-time state, which would re-enable
> the problematic attributes.
Hallucination. pci_pm_suspend() resets the state_saved flag to false.
Usage of the state_saved flag was recently changed by 894f475f88e0 and
a2f1e22390ac. Perhaps the LLM used by sashiko was trained with an older
version of the kernel source tree and is thus oblivious to those changes.
> Should there also be a DECLARE_PCI_FIXUP_RESUME_EARLY hook registered here to
> ensure the workaround is re-applied when the device resumes?
No.
Thanks,
Lukas
next prev parent reply other threads:[~2026-07-23 6:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-21 6:54 [PATCH] PCI: Disable NoSnoop and Relaxed ordering for Intel wireless BE200 Emmanuel Grumbach
2026-06-21 7:12 ` sashiko-bot
2026-06-21 7:30 ` Grumbach, Emmanuel
2026-07-22 14:56 ` Bjorn Helgaas
2026-07-22 15:14 ` Grumbach, Emmanuel
2026-07-22 17:04 ` Bjorn Helgaas
2026-07-23 9:49 ` Manikanta Maddireddy
2026-07-23 11:35 ` Grumbach, Emmanuel
2026-07-23 6:47 ` Lukas Wunner [this message]
2026-06-21 8:10 ` Lukas Wunner
2026-06-21 8:28 ` Grumbach, Emmanuel
2026-07-22 11:01 ` Grumbach, Emmanuel
2026-07-22 14:36 ` Lukas Wunner
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=amG5DN8sEetoZtvS@wunner.de \
--to=lukas@wunner.de \
--cc=emmanuel.grumbach@intel.com \
--cc=linux-pci@vger.kernel.org \
--cc=sashiko-reviews@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.