Date:   Sun, 21 Nov 2021 07:35:06 +0100
From:   Lukas Wunner <lukas@wunner.de>
To:     luanshi <zhangliguang@linux.alibaba.com>
Cc:     Bjorn Helgaas <bhelgaas@google.com>,
        Kuppuswamy Sathyanarayanan 
        <sathyanarayanan.kuppuswamy@linux.intel.com>,
        Amey Narkhede <ameynarkhede03@gmail.com>,
        linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] PCI: pciehp: clear cmd_busy bit when Command Completed
 in polling mode
Message-ID: <20211121063506.GA20043@wunner.de>
References: <20211111054258.7309-1-zhangliguang@linux.alibaba.com>
 <20211119120012.GC9692@wunner.de>
 <d226b80f-8e11-dcf9-084b-af22f4803b93@linux.alibaba.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <d226b80f-8e11-dcf9-084b-af22f4803b93@linux.alibaba.com>
User-Agent: Mutt/1.10.1 (2018-07-13)
Precedence: bulk

On Sun, Nov 21, 2021 at 09:50:38AM +0800, luanshi wrote:
> 2021/11/19 20:00, Lukas Wunner:
> > Please open a bug on bugzilla.kernel.org and attach full output
> > of lspci -vv and dmesg.  Be sure to add the following to the
> > command line:
> >    pciehp.pciehp_debug=1 dyndbg="file pciehp* +p"
> > 
> > Once you've done that, please report the bugzilla link here
> > so that we can analyze the issue properly.

I really need you to perform the above steps in order to analyze
what's going on here.

Again, if you get such timeout messages, it's usually not caused
by a bug in the driver but by an erratum in the hardware,
i.e. the hardware neglected to signal Command Completed in response
to a Slot Control register write.

Thanks,

Lukas