From: Yijing Wang <wangyijing@huawei.com>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: Rajat Jain <rajatxjain@gmail.com>, PCI <linux-pci@vger.kernel.org>
Subject: pciehp command complete timeout issue
Date: Thu, 18 Jun 2015 20:06:23 +0800 [thread overview]
Message-ID: <5582B43F.4090303@huawei.com> (raw)
When I tried to unbind pciehp driver on a pcie root port(bound pciehp driver),
a lot timeout warning appeared.
The first timeout value is 102387672 msec :(
I debug and found that when pciehp complete pcie_enable_notification(), there was no command complete interrupt
be triggered, so cmd_busy always be set, and once another command post, a very long timeout warning noised.
+-[0000:40]-+-00.0-[41]--
| +-01.0-[42-43]--+-00.0 Intel Corporation 82599ES 10-Gigabit SFI/SFP+ Network Connection
| | \-00.1 Intel Corporation 82599ES 10-Gigabit SFI/SFP+ Network Connection
| +-03.0-[44-45]--+-00.0 Intel Corporation 82599ES 10-Gigabit SFI/SFP+ Network Connection
| | \-00.1 Intel Corporation 82599ES 10-Gigabit SFI/SFP+ Network Connection
[root@hulk slots]# ls
0 0-1 0-2 0-3 0-4 0-5 1 10 11 12 13 14 15 16 2 3 4 5 6 7 8 9
[root@hulk slots]# cat 6/address
0000:44:00
[root@hulk slots]#
[root@hulk pciehp]# echo 0000:40:03.0:pcie04 > unbind
[root@hulk pciehp]#
...
[102413.749632] pciehp 0000:40:03.0:pcie04: unloading service driver pciehp
[102413.749638] pciehp_remove dev 0000:40:03.0, cmd_busy 1
[102413.754929] pcie_disable_notification: ctrl cmd busy 1
[102413.765903] pciehp 0000:40:03.0:pcie04: Timeout on hotplug command 0x11f1 (issued 102387672 msec ago)
[102413.775171] pcie_do_write_cmd: dev 0000:40:03.0, cmd_busy set to 1
[102415.377950] pciehp 0000:40:03.0:pcie04: Timeout on hotplug command 0x01c0 (issued 1600 msec ago)
...
--
Thanks!
Yijing
next reply other threads:[~2015-06-18 12:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-18 12:06 Yijing Wang [this message]
2015-06-24 23:05 ` pciehp command complete timeout issue Bjorn Helgaas
2015-06-25 1:18 ` Yijing Wang
2015-06-25 19:17 ` Bjorn Helgaas
2015-06-26 2:07 ` Yijing Wang
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=5582B43F.4090303@huawei.com \
--to=wangyijing@huawei.com \
--cc=bhelgaas@google.com \
--cc=linux-pci@vger.kernel.org \
--cc=rajatxjain@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.