From: Nicholas Johnson <nicholas.johnson-opensource@outlook.com.au>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: Yicong Yang <yangyicong@hisilicon.com>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
fangjian 00545541 <f.fangjian@huawei.com>
Subject: Re: PCI: bus resource allocation error
Date: Thu, 9 Jan 2020 23:55:18 +0000 [thread overview]
Message-ID: <PSXP216MB0438B0DAE881F9B7F7581D3080390@PSXP216MB0438.KORP216.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <20200109215517.GA255522@google.com>
On Thu, Jan 09, 2020 at 03:55:17PM -0600, Bjorn Helgaas wrote:
> On Thu, Jan 09, 2020 at 06:31:57PM +0800, Yicong Yang wrote:
> > On 2020/1/9 12:27, Bjorn Helgaas wrote:
> > > [+cc Nicholas, who is working in this area]
> > >
> > > On Thu, Jan 09, 2020 at 11:35:09AM +0800, Yicong Yang wrote:
> > >> Hi,
> > >>
> > >> recently I met a problem with pci bus resource allocation. The allocation strategy
> > >> makes me confused and leads to a wrong allocation results.
> > >>
> > >> There is a hisilicon network device with four functions under one root port. The
> > >> original bios resources allocation looks like:
> > > What kernel is this? Can you collect the complete dmesg log?
> >
> > The kernel version is 5.4.0.
>
> Good; at least we know this isn't related to Nicholas' new resource
> code that's in -next right now.
It is not in next - it is in the release candidates, right?
>
> > the dmesg log is like:
>
> The below is not the complete dmesg log. I don't know what your
> system is, but the complete log might be in /var/log/dmesg, or maybe
> you could capture it with the "ignore_loglevel" kernel parameter and a
> serial console?
>
> > [ 496.598130] hns3 0000:7d:00.3 eth11: net stop
> > ...
Yicong, please provide the full outputs of: "dmesg" and "sudo lspci
-xxxx" and "sudo cat /proc/iomem" in a location that is publicly
accessible so that anybody reading this email can find it.
Kind regards,
Nicholas
next prev parent reply other threads:[~2020-01-09 23:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-09 3:35 PCI: bus resource allocation error Yicong Yang
2020-01-09 4:27 ` Bjorn Helgaas
2020-01-09 10:31 ` Yicong Yang
2020-01-09 21:55 ` Bjorn Helgaas
2020-01-09 23:55 ` Nicholas Johnson [this message]
2020-01-10 0:08 ` Bjorn Helgaas
2020-01-09 23:00 ` Bjorn Helgaas
2020-01-10 7:08 ` Yicong Yang
2020-01-10 7:33 ` Yicong Yang
2020-01-10 7:40 ` Nicholas Johnson
2020-01-14 8:25 ` Yicong Yang
2020-02-11 10:36 ` Yicong Yang
2020-02-11 13:43 ` Nicholas Johnson
2020-02-11 19:43 ` Bjorn Helgaas
2020-02-18 3:18 ` Yicong Yang
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=PSXP216MB0438B0DAE881F9B7F7581D3080390@PSXP216MB0438.KORP216.PROD.OUTLOOK.COM \
--to=nicholas.johnson-opensource@outlook.com.au \
--cc=f.fangjian@huawei.com \
--cc=helgaas@kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=yangyicong@hisilicon.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.