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: Tue, 13 Oct 2015 10:32:04 +0300 (EEST) [thread overview]
Message-ID: <alpine.LRH.2.20.1510131020140.9747@math.ut.ee> (raw)
In-Reply-To: <CAE9FiQVAtPGgzwwMaHjGjyzOD8wKb0TqCd1wynF6-ZmFqZzEaQ@mail.gmail.com>
> > Updated on V210 - the others were more recent. Now I get more BAR
> > warning there too:
> >
> > http://kodu.ut.ee/~mroos/dm/dm.v210+patches
> >
>
> interesting, mem and mem64 is overlapping.
>
> [ 38.824625] /pci@1f,700000: TOMATILLO PCI Bus Module ver[4:0]
> [ 38.824654] /pci@1f,700000: PCI IO [io
> 0x7f601000000-0x7f601ffffff] offset 7f601000000
> [ 38.824680] /pci@1f,700000: PCI MEM [mem
> 0x7f700000000-0x7f7ffffffff] offset 7f700000000
> [ 38.824704] /pci@1f,700000: PCI MEM64 [mem
> 0x7f700000000-0x7f7ffffffff] offset 7f700000000
> [ 38.826310] PCI: Scanning PBM /pci@1f,700000
> [ 38.826479] schizo f0069c00: PCI host bridge to bus 0000:00
> [ 38.826506] pci_bus 0000:00: root bus resource [io
> 0x7f601000000-0x7f601ffffff] (bus address [0x0000-0xffffff])
> [ 38.826536] pci_bus 0000:00: root bus resource [mem
> 0x7f700000000-0x7f7ffffffff] (bus address [0x00000000-0xffffffff])
> [ 38.826565] pci_bus 0000:00: root bus resource [mem
> 0x7f700000000-0x7f7ffffffff] (bus address [0x00000000-0xffffffff])
>
> We need to add more sanitary checking.
>
> Can you send boot log after booting with "debug ignore_loglevel ofpci_debug=1" ?
http://kodu.ut.ee/~mroos/dm/dm.v210+patch+debug
Applied the fix_mem_mem64_overlapping.patch and retested. The BAR
allocation problems are still there:
http://kodu.ut.ee/~mroos/dm/dm.v210+patch+mem64patch+debug
--
Meelis Roos (mroos@linux.ee)
next prev parent reply other threads:[~2015-10-13 7:32 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-07 9:25 4.3-rc3 BAR allocation problems on multiple machines Meelis Roos
2015-10-07 22:49 ` Yinghai Lu
2015-10-12 13:04 ` Meelis Roos
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 [this message]
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.1510131020140.9747@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;
as well as URLs for NNTP newsgroup(s).