From: "guanghuifeng@linux.alibaba.com" <guanghuifeng@linux.alibaba.com>
To: Lukas Wunner <lukas@wunner.de>
Cc: "Bjorn Helgaas" <helgaas@kernel.org>,
linux-pci <linux-pci@vger.kernel.org>,
kanie <kanie@linux.alibaba.com>,
alikernel-developer <alikernel-developer@linux.alibaba.com>,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
Subject: Re: [PATCH] PCI: Fix PCIe SBR dev/link wait error
Date: Mon, 1 Dec 2025 22:46:00 +0800 [thread overview]
Message-ID: <238d7010-b54a-49cc-b5d0-e8422f59310f@linux.alibaba.com> (raw)
In-Reply-To: <aS2XeetaEW1RoWus@wunner.de>
在 2025/12/1 21:26, Lukas Wunner 写道:
> On Mon, Dec 01, 2025 at 08:56:10PM +0800, guanghuifeng@linux.alibaba.com wrote:
>> 2025/12/1 18:03, Lukas Wunner :
>>> It seems highly unusual that the different functions of the same physical
>>> device require different delays until they're accessible. I don't think
>>> we can accept such a sweeping change wholesale without more details,
>>> so please share what the topology looks like (lspci -tv), what devices are
>>> involved (lspci -vvv) and which device requires extra wait time for some
>>> of its functions.
> Could you please provide the details I asked for above?
>
> Thanks,
>
> Lukas
Thanks.
1. Currently, there are significant differences in reset recovery times
among
some PCIe multifunction devices, especially when the functions and
complexities
vary greatly, including some devices used for testing purposes.
2. Furthermore, similar implementations exist in various commercial devices
(with vastly different functions), such as the multifunction devices
(including VGA, audio functions, etc.) mentioned in the following link:
https://forums.developer.nvidia.com/t/nvidia-rtx-5090-not-detected-by-nvidia-smi-on-ubuntu-server-24-04/327409?page=2
[from the link]
lspci -nn | grep -i nvidia
c1:00.0 VGA compatible controller [0300]: NVIDIA Corporation GB202
[GeForce RTX 5090] [10de:2b85] (rev a1)
c1:00.1 Audio device [0403]: NVIDIA Corporation Device [10de:22e8] (rev a1)
[from the link]
next prev parent reply other threads:[~2025-12-01 14:46 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-24 10:45 [PATCH] PCI: Fix PCIe SBR dev/link wait error Guanghui Feng
2025-11-24 23:58 ` Bjorn Helgaas
2025-11-25 6:20 ` guanghui.fgh
2025-12-01 10:03 ` Lukas Wunner
2025-12-01 12:56 ` guanghuifeng
2025-12-01 13:26 ` Lukas Wunner
2025-12-01 14:46 ` guanghuifeng [this message]
2025-12-01 16:18 ` Lukas Wunner
2025-11-26 8:20 ` Ilpo Järvinen
2025-11-26 12:08 ` guanghui.fgh
2025-11-26 12:37 ` Ilpo Järvinen
2025-11-26 14:22 ` guanghui.fgh
2025-11-26 14:47 ` Ilpo Järvinen
2025-11-29 16:36 ` [PATCH v2] " Guanghui Feng
2025-12-01 9:21 ` Ilpo Järvinen
2025-12-01 12:21 ` guanghuifeng
2025-12-01 13:08 ` Ilpo Järvinen
2025-12-02 4:32 ` [PATCH v4 0/1] " Guanghui Feng
2025-12-02 4:32 ` [PATCH v4 v4 1/1] " Guanghui Feng
2025-12-02 16:49 ` Bjorn Helgaas
2025-12-02 16:51 ` Bjorn Helgaas
2025-12-03 14:41 ` Ilpo Järvinen
2025-11-30 5:17 ` [PATCH v3] " Guanghui Feng
2025-12-01 9:24 ` Ilpo Järvinen
2025-12-01 12:31 ` guanghuifeng
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=238d7010-b54a-49cc-b5d0-e8422f59310f@linux.alibaba.com \
--to=guanghuifeng@linux.alibaba.com \
--cc=alikernel-developer@linux.alibaba.com \
--cc=helgaas@kernel.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=kanie@linux.alibaba.com \
--cc=linux-pci@vger.kernel.org \
--cc=lukas@wunner.de \
/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