From: Yicong Yang <yangyicong@hisilicon.com>
To: Nicholas Johnson <nicholas.johnson-opensource@outlook.com.au>
Cc: Bjorn Helgaas <helgaas@kernel.org>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
fangjian 00545541 <f.fangjian@huawei.com>
Subject: Re: PCI: bus resource allocation error
Date: Tue, 14 Jan 2020 16:25:09 +0800 [thread overview]
Message-ID: <376bafc4-b2a2-a08f-3aa1-8be69ce909a5@hisilicon.com> (raw)
In-Reply-To: <PSXP216MB0438E92832F08A1AEC015D8180380@PSXP216MB0438.KORP216.PROD.OUTLOOK.COM>
Hi,
I cannot get the log on the original machine.
So I tested on another one and got the same error prints.
You can find the console output at
https://paste.ubuntu.com/p/5VHVnKWSty/
as well as the "lspci -xxxx" infomation.
Thanks,
Yang
On 2020/1/10 15:40, Nicholas Johnson wrote:
> Hi,
>
> On Fri, Jan 10, 2020 at 03:33:27PM +0800, Yicong Yang wrote:
>> Hi,
>>
>> It seems the attachments are blocked by the server.
>> The necessary console output is below.
>> The kernel version is 5.4, centos release 7.6. I didn't
>> change the PCI codes.
> It is very difficult for me to get the wider picture of your system
> without the full output of "sudo lspci -xxxx". Can you place them on
> PasteBin and send the links, rather than attaching them directly?
>
> I can try to speculate based on what you sent, but I cannot be sure it
> will be enough. For example, I do not know if your computer has multiple
> root complexes, which have shown to complicate things.
>
> Thanks!
>
>
next prev parent reply other threads:[~2020-01-14 8:24 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
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 [this message]
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=376bafc4-b2a2-a08f-3aa1-8be69ce909a5@hisilicon.com \
--to=yangyicong@hisilicon.com \
--cc=f.fangjian@huawei.com \
--cc=helgaas@kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=nicholas.johnson-opensource@outlook.com.au \
/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).