From: `VL <vl.homutov@gmail.com>
To: Yinghai Lu <yinghai@kernel.org>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>
Subject: Re: pci->pcie bridge issue: kernel unable to find a free I/O port range.
Date: Sat, 01 Feb 2014 14:30:14 +0400 [thread overview]
Message-ID: <52ECCCB6.8010202@gmail.com> (raw)
In-Reply-To: <CAE9FiQVD-qx-12G3j89SRqt3hUyLaUw8XKngjkFUsLwOrKSNrA@mail.gmail.com>
On 30.01.2014 22:56, Yinghai Lu wrote:
> On Wed, Jan 29, 2014 at 9:31 PM, `VL <vl.homutov@gmail.com> wrote:
>> On 15.01.2014 22:09, `VL wrote:
>>> On 15.01.2014 13:10, `VL wrote:
>>>>> looks like the your adapter need more time to settle down?
>>>>> Can you check if you can enable slow boot mode in BIOS setup?
>>>> yes, probably. I'll try to repeat steps with disabled fast boot.
>>> no, this is not the case. I've disabled all fast boot in BIOS and nothing
>>> changed in logs.
>>>
>>> so this is the best of what we have:
>>> http://inspert.ru/pci/dmesg-earlydump.txt
>>>
>>> I was also able to reproduce the issue without pci=realloc. I have
>>> disabled
>>> all builtin devices on motherboard (unused controllers, NICs and audio).
>>> Looks like in this conditions kernel was able to allocate some resource
>>> and hang during snd_ice1712 driver load.
>>>
>>> Attached is the photo of boot with this situation.
>>> Unfortunately, since NICs are disabled and there is no serial onboard,
>>> I cannot provide full log.
>>>
>> up: any concluision/suggestions?
> I don't know why the io bar of 07:00.0 can not be updated.
> also it's weird that 07:0.0 is not showing up in earlydump.
>
> anyway please try attached patch to see if it could make any difference.
>
> Thanks
>
> Yinghai
thank you, I'll try the patch and report results.
next prev parent reply other threads:[~2014-02-01 10:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-07 9:11 pci->pcie bridge issue: kernel unable to find a free I/O port range `VL
2014-01-07 18:27 ` Bjorn Helgaas
[not found] ` <52CD2387.2030403@gmail.com>
2014-01-08 20:28 ` Yinghai Lu
2014-01-09 5:14 ` `VL
2014-01-09 20:17 ` Yinghai Lu
2014-01-10 4:41 ` `VL
2014-01-10 5:19 ` Yinghai Lu
2014-01-11 8:38 ` `VL
2014-01-14 19:31 ` Yinghai Lu
2014-01-15 9:10 ` `VL
[not found] ` <52D6CEC6.2000901@gmail.com>
2014-01-30 5:31 ` `VL
2014-01-30 18:56 ` Yinghai Lu
2014-02-01 10:30 ` `VL [this message]
2014-10-13 20:48 ` Bjorn Helgaas
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=52ECCCB6.8010202@gmail.com \
--to=vl.homutov@gmail.com \
--cc=bhelgaas@google.com \
--cc=linux-pci@vger.kernel.org \
--cc=yinghai@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).