mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Alexey Bogoslavsky <Alexey.Bogoslavsky@sandisk.com>,
	Manivannan Sadhasivam <mani@kernel.org>,
	Bjorn Helgaas <helgaas@kernel.org>
Cc: Manivannan Sadhasivam <manivannan.sadhasivam@oss.qualcomm.com>,
	"bhelgaas@google.com" <bhelgaas@google.com>,
	"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Jeffrey Lien <Jeff.Lien@sandisk.com>,
	Avinash M N <Avinash.M.N@sandisk.com>
Subject: Re: [PATCH v2] PCI: Add quirk to disable ASPM L1 for Sandisk SN740 NVMe SSDs
Date: Thu, 27 Nov 2025 19:41:58 +0100	[thread overview]
Message-ID: <a35eb89e-fcd0-4af1-a0d0-655362a2b0d1@oss.qualcomm.com> (raw)
In-Reply-To: <BY5PR16MB339612035106C16822855A5A92D1A@BY5PR16MB3396.namprd16.prod.outlook.com>

On 11/25/25 4:30 PM, Alexey Bogoslavsky wrote:
> On Mon, Nov 24, 2025 at 05:53:07PM -0600, Bjorn Helgaas wrote:
>>> [+cc Alexey, Jeffrey, Avinash]
>>>
>>> On Thu, Nov 20, 2025 at 09:42:53PM +0530, Manivannan Sadhasivam wrote:
>>>> The Sandisk SN740 NVMe SSDs cause below AER errors on the upstream 
>>>> Root Port of PCIe controller in Microsoft Surface Laptop 7, when 
>>>> ASPM L1 is
>>>> enabled:
>>>>
>>>>   pcieport 0006:00:00.0: AER: Correctable error message received from 0006:01:00.0
>>>>   nvme 0006:01:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
>>>>   nvme 0006:01:00.0:   device [15b7:5015] error status/mask=00000001/0000e000
>>>>   nvme 0006:01:00.0:    [ 0] RxErr
>>>
>>> Do we have any information about whether this error happens with the
>>> SN740 on platforms other than the Surface Laptop 7?  Or whether it 
>>> happens on the Surface with other endpoints?
>>>
> 
>> This device comes pre installed with the Surface Laptop 7 I believe. It is not very convenient to replace the NVMe in a laptop for testing.
> 
>>> I'm a little hesitant about quirking devices and claiming they are 
>>> defective without a solid root cause.
>>>
> 
>> There are a couple of points that made me convince myself:
> 
>> * Other X1E laptops are working fine with ASPM L1.
>> * This laptop has WCN785x WiFi/BT combo card connected to the other controller instance and L1 is working fine for it.
>> * There is no known issue with ASPM L1 in X1E chipsets.
> 
>> Because of these, I was so certain that the NVMe is the fault here.
> 
>>> Sandisk folks, do you have any insight into this?  Any known errata or 
>>> possibility of looking into this with an analyzer?
>>>
> 
>> I don't think Konrad has access to the analyzer, neither any of us.
> 
>> If you are still hesitant, I'd suggest adding the platform check so that this quirk is only limited to the Surface Laptop 7:
> 
> We at Sandisk are currently checking and double-checking the issue on several platforms and with several devices.
> We haven't reached final conclusions yet, but what's clear is that quirking out SN740 unconditionally, for all platforms,
> is definitely an overkill. The device performs normally on vast majority of platforms. Applying the quirk for the combination
> of SN740 and Surface Laptop 7, as you suggested, is definitely a better choice. Still, we'd like to check a few more
> platform / device combinations so we cover everything that needs to be covered while sparing the rest of combinations.

Can we interpret that as "SN740 doesn't have L1 issues on at least one
other platform"?

In that case Mani, is there a chance we omitted some related tunable in
pci-qcom that only seems to matter for some PCI devices and not others?

Konrad

  reply	other threads:[~2025-11-27 18:42 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-20 16:12 Manivannan Sadhasivam
2025-11-24 11:42 ` Konrad Dybcio
2025-11-24 23:53 ` Bjorn Helgaas
2025-11-25  5:21   ` Manivannan Sadhasivam
2025-11-25 15:30     ` Alexey Bogoslavsky
2025-11-27 18:41       ` Konrad Dybcio [this message]
2025-11-27 18:40     ` Konrad Dybcio
2025-12-01  6:48     ` Val Packett
2025-12-01 10:37       ` Manivannan Sadhasivam
2025-12-04 12:51       ` Konrad Dybcio
2025-12-04 21:28         ` Val Packett

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=a35eb89e-fcd0-4af1-a0d0-655362a2b0d1@oss.qualcomm.com \
    --to=konrad.dybcio@oss.qualcomm.com \
    --cc=Alexey.Bogoslavsky@sandisk.com \
    --cc=Avinash.M.N@sandisk.com \
    --cc=Jeff.Lien@sandisk.com \
    --cc=bhelgaas@google.com \
    --cc=helgaas@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=mani@kernel.org \
    --cc=manivannan.sadhasivam@oss.qualcomm.com \
    /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

all inboxes | Powered by JetHome®