linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: luanshi <zhangliguang@linux.alibaba.com>
To: Lukas Wunner <lukas@wunner.de>
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
Date: Fri, 26 Nov 2021 15:47:30 +0800	[thread overview]
Message-ID: <e5cb4305-5fdd-88b6-8c1e-27b4ca8b8c39@linux.alibaba.com> (raw)
In-Reply-To: <20211121063506.GA20043@wunner.de>

Sorry for the late reply, the machine is occupied by someone else.

For detailed information:

https://bugzilla.kernel.org/show_bug.cgi?id=215143


Thanks,

Liguang

在 2021/11/21 14:35, Lukas Wunner 写道:
> 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

  reply	other threads:[~2021-11-26  7:49 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-11  5:42 [PATCH] PCI: pciehp: clear cmd_busy bit when Command Completed in polling mode Liguang Zhang
2021-11-18 11:00 ` luanshi
2021-11-19 12:00 ` Lukas Wunner
2021-11-21  1:50   ` luanshi
2021-11-21  6:35     ` Lukas Wunner
2021-11-26  7:47       ` luanshi [this message]
2021-11-26 17:33 ` Lukas Wunner
2021-11-26 17:35   ` Lukas Wunner
2022-01-06  8:55   ` luanshi
2022-02-03 19:07   ` Lukas Wunner
2022-02-03 20:38     ` Bjorn Helgaas

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=e5cb4305-5fdd-88b6-8c1e-27b4ca8b8c39@linux.alibaba.com \
    --to=zhangliguang@linux.alibaba.com \
    --cc=ameynarkhede03@gmail.com \
    --cc=bhelgaas@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=lukas@wunner.de \
    --cc=sathyanarayanan.kuppuswamy@linux.intel.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;
as well as URLs for NNTP newsgroup(s).