From: Yinghai Lu <yinghai@kernel.org>
To: Johannes Thumshirn <johannes.thumshirn@men.de>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>
Subject: Re: PCI reset problem
Date: Mon, 2 Sep 2013 15:18:48 -0700 [thread overview]
Message-ID: <CAE9FiQVb4GHFS6jwLbGKcPjF0HJ_mkACsj_kPrXvOKsjNDHd8g@mail.gmail.com> (raw)
In-Reply-To: <20130902080057.GA14515@jtlinux>
On Mon, Sep 2, 2013 at 1:00 AM, Johannes Thumshirn
<johannes.thumshirn@men.de> wrote:
> I've tested the board with your for-pci-busn-alloc-3.11 branch. Initial
> enumeration is just as it was before. With the difference that a "sysfs-rescan"
> now results in:
>
> root@generic-powerpc:~# lspci
> 00:00.0 PCI bridge: Freescale Semiconductor Inc P4080 (rev 20)
> root@generic-powerpc:~# echo 1 > /sys/bus/pci/rescan
> pci_bus 0000:00: scanning bus
> pcieport 0000:00:00.0: scanning [bus 01-01] behind bridge, pass 0
> pcieport 0000:00:00.0: scanning [bus 00-00] behind bridge, pass 1
> pcieport 0000:00:00.0: rescan scaned bridge as broken one again ?
> pci_bus 0000:00: bus scan returning with max=00
> root@generic-powerpc:~# lspci
> 00:00.0 PCI bridge: Freescale Semiconductor Inc P4080 (rev 20)
please send out whole boot log with "debug ignore_loglevel initcall_debug" ?
please make sure you have "CONFIG_PCI_DEBUG=y" in .config.
Yinghai
next prev parent reply other threads:[~2013-09-02 22:18 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-28 13:33 PCI reset problem Johannes Thumshirn
2013-08-28 16:50 ` Bjorn Helgaas
2013-08-29 8:29 ` Johannes Thumshirn
2013-08-29 12:01 ` Bjorn Helgaas
2013-08-29 15:07 ` Johannes Thumshirn
2013-08-29 15:52 ` Bjorn Helgaas
2013-08-30 8:01 ` Johannes Thumshirn
2013-08-30 13:40 ` Bjorn Helgaas
2013-08-30 13:58 ` Johannes Thumshirn
2013-08-30 19:46 ` Yinghai Lu
2013-09-02 8:00 ` Johannes Thumshirn
2013-09-02 22:18 ` Yinghai Lu [this message]
2013-09-03 9:55 ` Johannes Thumshirn
2013-09-03 19:38 ` Yinghai Lu
2013-09-04 8:10 ` Johannes Thumshirn
2013-08-29 17:40 ` Yinghai Lu
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=CAE9FiQVb4GHFS6jwLbGKcPjF0HJ_mkACsj_kPrXvOKsjNDHd8g@mail.gmail.com \
--to=yinghai@kernel.org \
--cc=bhelgaas@google.com \
--cc=johannes.thumshirn@men.de \
--cc=linux-pci@vger.kernel.org \
/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).