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: Fri, 10 Jan 2014 08:41:59 +0400 [thread overview]
Message-ID: <52CF7A17.60703@gmail.com> (raw)
In-Reply-To: <CAE9FiQWxpRMX-0vyd5hML-Hnto8H+C83dcne9FBZcN9qsmGCEw@mail.gmail.com>
On 10.01.2014 00:17, Yinghai Lu wrote:
> On Wed, Jan 8, 2014 at 9:14 PM, `VL <vl.homutov@gmail.com> wrote:
>> I've put all logs here: http://inspert.ru/pci/
>>> CONFIG_PCI_DEBUG=y
>>>
>>> and boot with "debug ignore_loglevel initcall_debug"?
> Jan 9 08:51:49 10 pci 0000:04:00.0: BAR 7: assigned [io 0x2000-0x4fff]
> Jan 9 08:51:49 10 pci 0000:05:01.0: BAR 7: assigned [io 0x2000-0x2fff]
> Jan 9 08:51:49 10 pci 0000:06:00.0: BAR 7: assigned [io 0x2000-0x2fff]
> Jan 9 08:51:49 10 pci 0000:07:00.0: BAR 3: assigned [io 0x2000-0x203f]
> Jan 9 08:51:49 10 pci 0000:07:00.0: BAR 3: error updating (0x002001
> != 0xffffffff)
> Jan 9 08:51:49 10 pci 0000:07:00.0: BAR 3: set to [io 0x2000-0x203f]
> (PCI address [0x2000-0x203f])
> Jan 9 08:51:49 10 pci 0000:07:00.0: BAR 0: assigned [io 0x2040-0x205f]
> Jan 9 08:51:49 10 pci 0000:07:00.0: BAR 0: error updating (0x002041
> != 0xffffffff)
> Jan 9 08:51:49 10 pci 0000:07:00.0: BAR 0: set to [io 0x2040-0x205f]
> (PCI address [0x2040-0x205f])
> Jan 9 08:51:49 10 pci 0000:07:00.0: BAR 1: assigned [io 0x2060-0x206f]
> Jan 9 08:51:49 10 pci 0000:07:00.0: BAR 1: error updating (0x002061
> != 0xffffffff)
> Jan 9 08:51:49 10 pci 0000:07:00.0: BAR 1: set to [io 0x2060-0x206f]
> (PCI address [0x2060-0x206f])
> Jan 9 08:51:49 10 pci 0000:07:00.0: BAR 2: assigned [io 0x2070-0x207f]
> Jan 9 08:51:49 10 pci 0000:07:00.0: BAR 2: error updating (0x002071
> != 0xffffffff)
> Jan 9 08:51:49 10 pci 0000:07:00.0: BAR 2: set to [io 0x2070-0x207f]
> (PCI address [0x2070-0x207f])
> Jan 9 08:51:49 10 pci 0000:06:00.0: PCI bridge to [bus 07]
> Jan 9 08:51:49 10 pci 0000:06:00.0: bridge window [io 0x2000-0x2fff]
> Jan 9 08:51:49 10 pci 0000:05:01.0: PCI bridge to [bus 06-07]
> Jan 9 08:51:49 10 pci 0000:05:01.0: bridge window [io 0x2000-0x2fff]
> Jan 9 08:51:49 10 pci 0000:0d:00.0: BAR 0: set to [io 0x4020-0x4027]
> (PCI address [0x4020-0x4027])
> Jan 9 08:51:49 10 pci 0000:0d:00.0: BAR 2: assigned [io 0x4028-0x402f]
> Jan 9 08:51:49 10 pci 0000:0d:00.0: BAR 3: assigned [io 0x4034-0x4037]
> Jan 9 08:51:49 10 pci 0000:0d:00.0: BAR 3: set to [io 0x4034-0x4037]
> (PCI address [0x4034-0x4037])
> Jan 9 08:51:49 10 pci 0000:05:09.0: PCI bridge to [bus 0d]
> Jan 9 08:51:49 10 pci 0000:05:09.0: bridge window [io 0x4000-0x4fff]
> Jan 9 08:51:49 10 pci 0000:05:09.0: bridge window [mem 0xf7600000-0xf76fffff]
> Jan 9 08:51:49 10 pci 0000:04:00.0: PCI bridge to [bus 05-0d]
> Jan 9 08:51:49 10 pci 0000:04:00.0: bridge window [io 0x2000-0x4fff]
> Jan 9 08:51:49 10 pci 0000:04:00.0: bridge window [mem 0xf7200000-0xf77fffff]
> Jan 9 08:51:49 10 pci 0000:04:00.0: bridge window [mem
> 0xf0000000-0xf00fffff 64bit pref]
> Jan 9 08:51:49 10 pci 0000:00:1c.3: PCI bridge to [bus 04-0d]
> Jan 9 08:51:49 10 pci 0000:00:1c.3: bridge window [io 0x2000-0x4fff]
> Jan 9 08:51:49 10 pci 0000:00:1c.3: bridge window [mem 0xf7200000-0xf78fffff]
> Jan 9 08:51:49 10 pci 0000:00:1c.3: bridge window [mem
> 0xf0000000-0xf00fffff 64bit pref]
>
> The realloc code does reassign big range to the devices.
>
> but one device refuse to change bar to new assigned vaule, or it is read-only?
>
> Jan 9 08:51:49 10 pci 0000:07:00.0: BAR 3: assigned [io 0x2000-0x203f]
> Jan 9 08:51:49 10 pci 0000:07:00.0: BAR 3: error updating (0x002001
> != 0xffffffff)
> Jan 9 08:51:49 10 pci 0000:07:00.0: BAR 3: set to [io 0x2000-0x203f]
> (PCI address [0x2000-0x203f])
> Jan 9 08:51:49 10 pci 0000:07:00.0: BAR 0: assigned [io 0x2040-0x205f]
> Jan 9 08:51:49 10 pci 0000:07:00.0: BAR 0: error updating (0x002041
> != 0xffffffff)
> Jan 9 08:51:49 10 pci 0000:07:00.0: BAR 0: set to [io 0x2040-0x205f]
> (PCI address [0x2040-0x205f])
> Jan 9 08:51:49 10 pci 0000:07:00.0: BAR 1: assigned [io 0x2060-0x206f]
> Jan 9 08:51:49 10 pci 0000:07:00.0: BAR 1: error updating (0x002061
> != 0xffffffff)
> Jan 9 08:51:49 10 pci 0000:07:00.0: BAR 1: set to [io 0x2060-0x206f]
> (PCI address [0x2060-0x206f])
> Jan 9 08:51:49 10 pci 0000:07:00.0: BAR 2: assigned [io 0x2070-0x207f]
> Jan 9 08:51:49 10 pci 0000:07:00.0: BAR 2: error updating (0x002071
> != 0xffffffff)
> Jan 9 08:51:49 10 pci 0000:07:00.0: BAR 2: set to [io 0x2070-0x207f]
> (PCI address [0x2070-0x207f])
>
>
> also BIOS does not assign any vaule to it:
>
> Jan 9 08:51:49 10 pci 0000:07:00.0: reg 0x10: [io 0x0000-0x001f]
> Jan 9 08:51:49 10 pci 0000:07:00.0: reg 0x18: [io 0x0000-0x000f]
> Jan 9 08:51:49 10 pci 0000:07:00.0: reg 0x1c: [io 0x0000-0x003f]
>
> It is strange 05:01.0/07:00.0 does not work, but 05:09.0/0d:00.0 does work.
>
> Can you boot with "pci=earlydump"?
>
> Yinghai
Here it is: http://inspert.ru/pci/netconsole-realloc-earlydump.txt
next prev parent reply other threads:[~2014-01-10 4:42 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 [this message]
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
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=52CF7A17.60703@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).