From: Jiang Liu <liuj97@gmail.com>
To: Frank Rizzo <thefrankrizzo@hotmail.com>
Cc: Yijing Wang <wangyijing@huawei.com>,
Bjorn Helgaas <bhelgaas@google.com>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>
Subject: Re: Rescan PCIE bus to find recently powered on device.
Date: Sun, 21 Apr 2013 00:17:08 +0800 [thread overview]
Message-ID: <5172BF84.9090307@gmail.com> (raw)
In-Reply-To: <BLU0-SMTP106EAAAE910BEDD2F047B19B2C90@phx.gbl>
On 04/20/2013 11:26 AM, Frank Rizzo wrote:
> On Fri, 19 Apr 2013 19:59:58 -0700, Yijing Wang <wangyijing@huawei.com> wrote:
>
>> On 2013/4/20 10:22, Frank Rizzo wrote:
>>> (with device powered on AFTER boot)
>>>
>>> root@frank-System-Product-Name:~# echo 1 > /sys/bus/pci/rescan
>>
>> Hi Frank,
>> When you do rescan here, any new message info will print in dmesg?
>> Compare the two lspci info, it seems like your external device is
>> 02.0-[02]----00.0 Device 1a39:0004, which include a pci bridge and a pci endpoint device.
>> But let me confused is that after you rescan (with device powered on AFTER boot),
>> there is no any new device found, normally, at least we should found the bridge device.
>> Maybe the link between host bridge and your external device got some problems? I am not sure.
>
>
> Yijing, when powered on, the device works fine. I can talk to all the registers, and do everything that I need to do. This "late power-on issue" is the only thing holding me back.
>
> This is what I get in dmesg. (Cleared first)
>
> root@frank-System-Product-Name:~# dmesg -c
> (SNIP!)
> root@frank-System-Product-Name:~# echo 1 > /sys/bus/pci/rescan
> root@frank-System-Product-Name:~# dmesg
> [ 1180.917841] fglrx_pci 0000:01:05.0: BAR 6: [??? 0x00000000 flags 0x2] has bogus alignment
> root@frank-System-Product-Name:~#
> --
> To unsubscribe from this list: send the line "unsubscribe linux-pci" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
Hi Frank,
Message from "sudo lspci -vvv" gives more information, including PCIe capabilities,
so please help to send out "sudo lspci -vvv" instead of "lspci -v".
Thanks!
next prev parent reply other threads:[~2013-04-20 16:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-19 2:59 Rescan PCIE bus to find recently powered on device Frank Rizzo
2013-04-19 3:27 ` Yijing Wang
2013-04-19 15:49 ` Bjorn Helgaas
[not found] ` <BLU0-SMTP305A7D1308063E03F4C5CE9B2C90@phx.gbl>
[not found] ` <5171F610.80001@huawei.com>
2013-04-20 2:22 ` Frank Rizzo
2013-04-20 2:59 ` Yijing Wang
2013-04-20 3:26 ` Frank Rizzo
2013-04-20 5:47 ` Yijing Wang
2013-04-20 16:10 ` Jiang Liu
2013-04-20 16:17 ` Jiang Liu [this message]
2013-04-20 20:52 ` Frank Rizzo
2013-04-21 2:21 ` Jiang Liu
2013-04-22 17:21 ` Bjorn Helgaas
2013-05-12 22:13 ` Frank Rizzo
2013-05-13 5:35 ` Frank Rizzo
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=5172BF84.9090307@gmail.com \
--to=liuj97@gmail.com \
--cc=bhelgaas@google.com \
--cc=linux-pci@vger.kernel.org \
--cc=thefrankrizzo@hotmail.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).