[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <db8fb91b-e132-4d8e-ab7a-d7954fc6629d@nvidia.com>
Date: Thu, 15 Jan 2026 12:11:09 -0800
From: Terje Bergstrom <tbergstrom@...dia.com>
To: Bjorn Helgaas <helgaas@...nel.org>,
Johnny-CC Chang (張晋嘉)
<Johnny-CC.Chang@...iatek.com>
Cc: "lukas@...ner.de" <lukas@...ner.de>,
Project_Global_Digits_Upstream_Group
<Project_Global_Digits_Upstream_Group@...iatek.com>,
AngeloGioacchino Del Regno <angelogioacchino.delregno@...labora.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>,
"linux-mediatek@...ts.infradead.org" <linux-mediatek@...ts.infradead.org>,
"bhelgaas@...gle.com" <bhelgaas@...gle.com>,
"matthias.bgg@...il.com" <matthias.bgg@...il.com>,
Jason Gunthorpe <jgg@...dia.com>, Alex Williamson <alex@...zbot.org>
Subject: Re: [PATCH] PCI: Mark Nvidia GB10 to avoid bus reset
On 1/14/26 09:28, Bjorn Helgaas wrote:
> What sort of crash happens? It's useful if we can include a bread > crumb that will help people identify the crash and find a fix.
We observed retraining to lower PCIe lane count and config read timeout.
So yes crash is not the best way to describe it.
> I'm confused about what the topology is. I first assumed GB10 was > a PCIe Endpoint, since Secondary Bus Reset only applies to devices > below a bridge, so SBR would be applied to a device by a config > write to that bridge.
gb10 is an SoC designed by NVIDIA and Mediatek in collaboration. It's
not an endpoint, but has its own PCIe controller for connecting PCIe
peripherals like NVMe drives, NIC, etc.
> If this is actually a GB10 issue, it sounds like a hardware erratum > that lots of users would see and Nvidia would likely be aware of.
We're aware. We've maintained a quirk in a kernel tree for DGX Spark
and other gb10 powered products until this gets upstreamed.
Terje
Powered by blists - more mailing lists