From: Meelis Roos <mroos@linux.ee>
To: Yinghai Lu <yinghai@kernel.org>
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>
Subject: Re: 4.3-rc3 BAR allocation problems on multiple machines
Date: Mon, 12 Oct 2015 16:04:47 +0300 (EEST) [thread overview]
Message-ID: <alpine.LRH.2.20.1510120808240.3251@math.ut.ee> (raw)
In-Reply-To: <CAE9FiQXM9YxRwcbG577Pcqmj7YbOa0yk6hYELb2FpTtct5u2jg@mail.gmail.com>
> > sparc64 machines:
> >
> > http://kodu.ut.ee/~mroos/dm/dm.t1-105
> > http://kodu.ut.ee/~mroos/dm/dm.t1-200
> > http://kodu.ut.ee/~mroos/dm/dm.v120
> > http://kodu.ut.ee/~mroos/dm/dm.v210
> > http://kodu.ut.ee/~mroos/dm/dm.v240
> > http://kodu.ut.ee/~mroos/dm/dm.sb100
>
> Please try
>
> git://git.kernel.org/pub/scm/linux/kernel/git/yinghai/linux-yinghai.git
> for-pci-v4.4-next
>
> It should fix some "no compatible bridge window"
Blade 100: still has 2 address conflicts:
http://kodu.ut.ee/~mroos/dm/dm.sb100+patch
V240: still has a lot of address conflicts:
http://kodu.ut.ee/~mroos/dm/dm.v240+patch
V210: fixes the line
pci 0001:00:07.0: can't claim BAR 0 [io 0x7fe01000000-0x7fe0100ffff]: address conflict with 0001:00:06.0 [io 0x7fe01000600-0x7fe0100061f]
These lines are still present:
pci 0001:00:07.0: can't claim BAR 1 [mem 0x7ff00000000-0x7ff000fffff]: address conflict with Video RAM area [??? 0x7ff000a0000-0x7ff000bffff flags 0x80000000]
pci 0001:00:07.0: can't claim BAR 2 [mem 0x7ff00000000-0x7ff000fffff]: address conflict with Video RAM area [??? 0x7ff000a0000-0x7ff000bffff flags 0x80000000]
V120: all messages gone, used to have
[ 46.962673] pci 0000:00:01.0: can't claim BAR 8 [mem 0x1ff00000000-0x1ffbfffffff]: address conflict with Video RAM area [??? 0x1ff000a0000-0x1ff000bffff flags 0x80000000]
[ 46.962794] pci 0000:02:08.0: can't claim BAR 1 [mem 0x1ff00002000-0x1ff00003fff]: no compatible bridge window
[ 46.962856] pci 0000:02:08.0: can't claim BAR 3 [mem 0x1ff00004000-0x1ff00005fff]: no compatible bridge window
[ 46.962917] pci 0000:02:08.1: can't claim BAR 1 [mem 0x1ff00006000-0x1ff00007fff]: no compatible bridge window
[ 46.962976] pci 0000:02:08.1: can't claim BAR 3 [mem 0x1ff00008000-0x1ff00009fff]: no compatible bridge window
T1-200: all messages gone, used to have
[ 41.606858] pci 0000:00:01.0: can't claim BAR 8 [mem 0x1ff00000000-0x1ffbfffffff]: address conflict with Video RAM area [??? 0x1ff000a0000-0x1ff000bffff flags 0x80000000]
[ 41.606981] pci 0000:02:08.0: can't claim BAR 1 [mem 0x1ff00002000-0x1ff00003fff]: no compatible bridge window
[ 41.607043] pci 0000:02:08.0: can't claim BAR 3 [mem 0x1ff00004000-0x1ff00005fff]: no compatible bridge window
[ 41.607174] pci 0000:02:08.1: can't claim BAR 1 [mem 0x1ff00006000-0x1ff00007fff]: no compatible bridge window
[ 41.607236] pci 0000:02:08.1: can't claim BAR 3 [mem 0x1ff00008000-0x1ff00009fff]: no compatible bridge window
[ 41.607298] pci 0000:02:05.0: can't claim BAR 1 [mem 0x1ff0000a000-0x1ff0000bfff]: no compatible bridge window
[ 41.607358] pci 0000:02:05.0: can't claim BAR 6 [mem 0x1ff00020000-0x1ff0003ffff]: no compatible bridge window
T1-105: all messages are gone, qla1280 works. used to have
[ 21.107754] pci 0000:00:01.0: can't claim BAR 8 [mem 0x1ff00000000-0x1ffbfffffff]: address conflict with Video RAM area [??? 0x1ff000a0000-0x1ff000bffff flags 0x80000000]
[ 21.107856] pci 0000:02:01.0: can't claim BAR 8 [mem 0x1ff00100000-0x1ff028fffff]: no compatible bridge window
[ 21.107926] pci 0000:03:0f.0: can't claim BAR 8 [mem 0x1ff00100000-0x1ff028fffff]: no compatible bridge window
[ 21.107993] pci 0000:04:00.0: can't claim BAR 0 [mem 0x1ff01000000-0x1ff01ffffff]: no compatible bridge window
[ 21.108058] pci 0000:04:00.0: can't claim BAR 1 [mem 0x1ff02000000-0x1ff027fffff]: no compatible bridge window
[ 21.108124] pci 0000:04:00.1: can't claim BAR 0 [mem 0x1ff02800000-0x1ff0280702f]: no compatible bridge window
[ 21.108190] pci 0000:04:04.0: can't claim BAR 1 [mem 0x1ff02808000-0x1ff02808fff]: no compatible bridge window
[ 21.108256] pci 0000:04:04.0: can't claim BAR 6 [mem 0x1ff02810000-0x1ff0281ffff]: no compatible bridge window
...
[ 53.649523] qla1280 0000:04:04.0: can't ioremap BAR 1: [mem size 0x00001000]
[ 53.742379] qla1280: Unable to map I/O memory
--
Meelis Roos (mroos@linux.ee)
next prev parent reply other threads:[~2015-10-12 13:03 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-07 9:25 Meelis Roos
2015-10-07 22:49 ` Yinghai Lu
2015-10-12 13:04 ` Meelis Roos [this message]
2015-10-12 22:55 ` Yinghai Lu
2015-10-13 5:06 ` Meelis Roos
2015-10-13 5:43 ` Yinghai Lu
2015-10-13 6:21 ` Yinghai Lu
2015-10-13 7:32 ` Meelis Roos
2015-10-13 19:30 ` Yinghai Lu
2015-10-13 19:43 ` Yinghai Lu
2015-10-13 20:39 ` Meelis Roos
2015-10-14 0:43 ` Yinghai Lu
2015-10-14 7:34 ` Meelis Roos
2015-10-14 21:45 ` Yinghai Lu
2015-10-13 6:19 ` Yinghai Lu
2015-10-07 23:16 ` Yinghai Lu
2015-10-08 14:47 ` Bjorn Helgaas
2016-10-26 21:50 ` Bjorn Helgaas
2016-10-27 15:35 ` Meelis Roos
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=alpine.LRH.2.20.1510120808240.3251@math.ut.ee \
--to=mroos@linux.ee \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®