From: Jiang Liu <liuj97@gmail.com>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: Yijing Wang <wangyijing@huawei.com>,
Giridhar Malavali <giridhar.malavali@qlogic.com>,
Jon Mason <jdmason@kudzu.us>,
Andrew Vasquez <andrew.vasquez@qlogic.com>,
linux-driver@qlogic.com, linux-scsi@vger.kernel.org,
PCI <linux-pci@vger.kernel.org>,
Saurav Kashyap <saurav.kashyap@qlogic.com>,
Chad Dupuis <chad.dupuis@qlogic.com>
Subject: Re: Fail to probe qla2xxx fiber channel card while doing pci hotplug
Date: Thu, 20 Sep 2012 23:58:52 +0800 [thread overview]
Message-ID: <505B3D3C.6030109@gmail.com> (raw)
In-Reply-To: <CAErSpo6Wvn_cdOJg-OULbjyDQ0Qibq_+X78QMSqBeoC0GuB2VQ@mail.gmail.com>
Hi Bjorn,
We will try to work out a patch for this issue, won't silently ignore it.
We also found another issue related to ARI. The steps to reproduce the bug is:
1) Boot with a ARI-capable device connected to ARI-capable port, so ARI will be enabled.
2) Hot-remove the ARI-capable device.
3) Hot-add another non-ARI-capable multifunction device into the same slot.
4) Now only the function 0 of the hot-added device could be enumerated.
I think Yijing is going to work on the above two issues.
Thanks!
Gerry
On 09/20/2012 11:46 PM, Bjorn Helgaas wrote:
>>>> tried any. Does "pci=pcie_bus_safe" make any difference?
prev parent reply other threads:[~2012-09-20 15:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-15 10:22 Fail to probe qla2xxx fiber channel card while doing pci hotplug Yijing Wang
2012-09-16 3:30 ` Bjorn Helgaas
[not found] ` <50571243.4050001@huawei.com>
2012-09-17 18:15 ` Giridhar Malavali
2012-09-18 1:26 ` Yijing Wang
2012-09-18 17:54 ` Bjorn Helgaas
2012-09-18 23:49 ` Giridhar Malavali
2012-09-20 1:27 ` Yijing Wang
2012-09-19 1:50 ` Yijing Wang
2012-09-19 13:39 ` Bjorn Helgaas
2012-09-19 15:31 ` Jiang Liu
2012-09-20 1:39 ` Yijing Wang
2012-09-20 1:47 ` Yijing Wang
2012-09-20 12:26 ` Yijing Wang
2012-09-20 15:46 ` Bjorn Helgaas
2012-09-20 15:58 ` Jiang Liu [this message]
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=505B3D3C.6030109@gmail.com \
--to=liuj97@gmail.com \
--cc=andrew.vasquez@qlogic.com \
--cc=bhelgaas@google.com \
--cc=chad.dupuis@qlogic.com \
--cc=giridhar.malavali@qlogic.com \
--cc=jdmason@kudzu.us \
--cc=linux-driver@qlogic.com \
--cc=linux-pci@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=saurav.kashyap@qlogic.com \
--cc=wangyijing@huawei.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).