* 4.3-rc3 BAR allocation problems on multiple machines
@ 2015-10-07 9:25 Meelis Roos
2015-10-07 22:49 ` Yinghai Lu
` (2 more replies)
0 siblings, 3 replies; 19+ messages in thread
From: Meelis Roos @ 2015-10-07 9:25 UTC (permalink / raw)
To: Yinghai Lu; +Cc: Linux Kernel list, linux-pci
First I noticed that on Sun Netra t1-150 (sparc64 CPU), PCI allocation
was failing for qla1280 scsi driver. Reading dmesg uncovered "can't
claim BAR" errors. Looking for this in my other test machines I see more
of them - on many sparc64 machines and some on x86.
In another thread for "Resource allocation cleanup for v4.4", Yinghai Lu
asked for full dmesg to solve another similar case. So to help
understanding this one, here are the dmesgs of my machines:
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
amd64 machine:
http://kodu.ut.ee/~mroos/dm/dm.x2100
--
Meelis Roos (mroos@linux.ee)
^ permalink raw reply [flat|nested] 19+ messages in thread* Re: 4.3-rc3 BAR allocation problems on multiple machines 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-07 23:16 ` Yinghai Lu 2016-10-26 21:50 ` Bjorn Helgaas 2 siblings, 1 reply; 19+ messages in thread From: Yinghai Lu @ 2015-10-07 22:49 UTC (permalink / raw) To: Meelis Roos; +Cc: Linux Kernel list, linux-pci@vger.kernel.org On Wed, Oct 7, 2015 at 2:25 AM, Meelis Roos <mroos@linux.ee> wrote: > First I noticed that on Sun Netra t1-150 (sparc64 CPU), PCI allocation > was failing for qla1280 scsi driver. Reading dmesg uncovered "can't > claim BAR" errors. Looking for this in my other test machines I see more > of them - on many sparc64 machines and some on x86. > > In another thread for "Resource allocation cleanup for v4.4", Yinghai Lu > asked for full dmesg to solve another similar case. So to help > understanding this one, here are the dmesgs of my machines: > > 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" Thanks Yinghai ^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: 4.3-rc3 BAR allocation problems on multiple machines 2015-10-07 22:49 ` Yinghai Lu @ 2015-10-12 13:04 ` Meelis Roos 2015-10-12 22:55 ` Yinghai Lu 0 siblings, 1 reply; 19+ messages in thread From: Meelis Roos @ 2015-10-12 13:04 UTC (permalink / raw) To: Yinghai Lu; +Cc: Linux Kernel list, linux-pci@vger.kernel.org > > 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) ^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: 4.3-rc3 BAR allocation problems on multiple machines 2015-10-12 13:04 ` Meelis Roos @ 2015-10-12 22:55 ` Yinghai Lu 2015-10-13 5:06 ` Meelis Roos 0 siblings, 1 reply; 19+ messages in thread From: Yinghai Lu @ 2015-10-12 22:55 UTC (permalink / raw) To: Meelis Roos; +Cc: Linux Kernel list, linux-pci@vger.kernel.org On Mon, Oct 12, 2015 at 6:04 AM, Meelis Roos <mroos@linux.ee> wrote: >> > sparc64 machines: >> >> 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] > you should not have those. Looks like you are using old branch before 2015-10-05. If you use the git directly, please update the branch to local again. Thanks Yinghai ^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: 4.3-rc3 BAR allocation problems on multiple machines 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:19 ` Yinghai Lu 0 siblings, 2 replies; 19+ messages in thread From: Meelis Roos @ 2015-10-13 5:06 UTC (permalink / raw) To: Yinghai Lu; +Cc: Linux Kernel list, linux-pci@vger.kernel.org > >> > sparc64 machines: > >> > >> 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] > > > you should not have those. > > Looks like you are using old branch before 2015-10-05. > > If you use the git directly, please update the branch to local again. 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 -- Meelis Roos (mroos@linux.ee) ^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: 4.3-rc3 BAR allocation problems on multiple machines 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 6:19 ` Yinghai Lu 1 sibling, 2 replies; 19+ messages in thread From: Yinghai Lu @ 2015-10-13 5:43 UTC (permalink / raw) To: Meelis Roos; +Cc: Linux Kernel list, linux-pci@vger.kernel.org On Mon, Oct 12, 2015 at 10:06 PM, Meelis Roos <mroos@linux.ee> wrote: >> >> > sparc64 machines: >> >> >> >> 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] >> > >> you should not have those. >> >> Looks like you are using old branch before 2015-10-05. >> >> If you use the git directly, please update the branch to local again. > > 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" ? Thanks Yinghai ^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: 4.3-rc3 BAR allocation problems on multiple machines 2015-10-13 5:43 ` Yinghai Lu @ 2015-10-13 6:21 ` Yinghai Lu 2015-10-13 7:32 ` Meelis Roos 1 sibling, 0 replies; 19+ messages in thread From: Yinghai Lu @ 2015-10-13 6:21 UTC (permalink / raw) To: Meelis Roos; +Cc: Linux Kernel list, linux-pci@vger.kernel.org [-- Attachment #1: Type: text/plain, Size: 1303 bytes --] On Mon, Oct 12, 2015 at 10:43 PM, Yinghai Lu <yinghai@kernel.org> wrote: > On Mon, Oct 12, 2015 at 10:06 PM, Meelis Roos <mroos@linux.ee> wrote: >>> >> > sparc64 machines: >> >> 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]) > For overlapping, please check attached patch that should fix the problem. Thanks Yinghai [-- Attachment #2: fix_mem_mem64_overlapping.patch --] [-- Type: text/x-patch, Size: 1905 bytes --] Subject: [PATCH] sparc/PCI: check overlapping mmio64 with mmio for root bus Found one system have overlapping between mmio64 and mmio: /pci@1d,700000: TOMATILLO PCI Bus Module ver[4:0] /pci@1d,700000: PCI IO [io 0x7c601000000-0x7c601ffffff] offset 7c601000000 /pci@1d,700000: PCI MEM [mem 0x7c700000000-0x7c7ffffffff] offset 7c700000000 /pci@1d,700000: PCI MEM64 [mem 0x7c700000000-0x7c7ffffffff] offset 7c700000000 PCI: Scanning PBM /pci@1d,700000 schizo f00859d4: PCI host bridge to bus 0003:00 pci_bus 0003:00: root bus resource [io 0x7c601000000-0x7c601ffffff] (bus address [0x0000-0xffffff]) pci_bus 0003:00: root bus resource [mem 0x7c700000000-0x7c7ffffffff] (bus address [0x00000000-0xffffffff]) pci_bus 0003:00: root bus resource [mem 0x7c700000000-0x7c7ffffffff] (bus address [0x00000000-0xffffffff]) so add checking for overlapping, and skip that mem64. Signed-off-by: Yinghai Lu <yinghai@kernel.org> --- arch/sparc/kernel/pci_common.c | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) Index: linux-2.6/arch/sparc/kernel/pci_common.c =================================================================== --- linux-2.6.orig/arch/sparc/kernel/pci_common.c +++ linux-2.6/arch/sparc/kernel/pci_common.c @@ -483,12 +483,17 @@ void pci_determine_mem_io_space(struct p if (mem64_offset != pbm->mem_offset) panic("mem offset %llx != mem64 offset %llx\n", pbm->mem_offset, mem64_offset); + if (pbm->mem64_space.start <= pbm->mem_space.end) + pbm->mem64_space.start = pbm->mem_space.end + 1; + if (pbm->mem64_space.start > pbm->mem64_space.end) + pbm->mem64_space.flags = 0; } else pbm->mem_offset = mem64_offset; + } + if (pbm->mem64_space.flags) printk("%s: PCI MEM64 %pR offset %llx\n", pbm->name, &pbm->mem64_space, pbm->mem_offset); - } pbm->io_space.name = pbm->mem_space.name = pbm->name; pbm->mem64_space.name = pbm->name; ^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: 4.3-rc3 BAR allocation problems on multiple machines 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 1 sibling, 2 replies; 19+ messages in thread From: Meelis Roos @ 2015-10-13 7:32 UTC (permalink / raw) To: Yinghai Lu; +Cc: Linux Kernel list, linux-pci@vger.kernel.org > > 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) ^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: 4.3-rc3 BAR allocation problems on multiple machines 2015-10-13 7:32 ` Meelis Roos @ 2015-10-13 19:30 ` Yinghai Lu 2015-10-13 19:43 ` Yinghai Lu 1 sibling, 0 replies; 19+ messages in thread From: Yinghai Lu @ 2015-10-13 19:30 UTC (permalink / raw) To: Meelis Roos; +Cc: Linux Kernel list, linux-pci@vger.kernel.org On Tue, Oct 13, 2015 at 12:32 AM, Meelis Roos <mroos@linux.ee> wrote: > 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 Good, now MEM64 is gone. [ 34.145275] /pci@1f,700000: TOMATILLO PCI Bus Module ver[4:0] [ 34.145304] /pci@1f,700000: PCI IO [io 0x7f601000000-0x7f601ffffff] offset 7f601000000 [ 34.145330] /pci@1f,700000: PCI MEM [mem 0x7f700000000-0x7f7ffffffff] offset 7f700000000 [ 34.146938] PCI: Scanning PBM /pci@1f,700000 [ 34.147104] schizo f0069c00: PCI host bridge to bus 0000:00 [ 34.147132] pci_bus 0000:00: root bus resource [io 0x7f601000000-0x7f601ffffff] (bus address [0x0000-0xffffff]) [ 34.147162] pci_bus 0000:00: root bus resource [mem 0x7f700000000-0x7f7ffffffff] (bus address [0x00000000-0xffffffff]) ^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: 4.3-rc3 BAR allocation problems on multiple machines 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 1 sibling, 1 reply; 19+ messages in thread From: Yinghai Lu @ 2015-10-13 19:43 UTC (permalink / raw) To: Meelis Roos; +Cc: Linux Kernel list, linux-pci@vger.kernel.org On Tue, Oct 13, 2015 at 12:32 AM, Meelis Roos <mroos@linux.ee> wrote: >> >> Can you send boot log after booting with "debug ignore_loglevel ofpci_debug=1" ? > > http://kodu.ut.ee/~mroos/dm/dm.v210+patch+debug Firmware does reported overlapped resources. [ 34.150035] PCI: scan_bus[/pci@1e,600000] bus no 0 [ 34.150050] * /pci@1e,600000/isa@7 [ 34.150085] create device, devfn: 38, type: [ 34.150114] class: 0x60100 device name: 0001:00:07.0 [ 34.150129] parse addresses (60 bytes) @ fff000123fe92b40 [ 34.150144] start: 7fe01000000, end: 7fe0100ffff, i: 10 ========== [ 34.150159] start: 7ff00000000, end: 7ff000fffff, i: 14 [ 34.150174] start: 7ff00000000, end: 7ff000fffff, i: 18 [ 34.150188] adding to system ... [ 34.150333] PCI: dev header type: 0 [ 34.150348] * /pci@1e,600000/pmu@6 [ 34.150386] create device, devfn: 30, type: [ 34.150409] class: 0x0 device name: 0001:00:06.0 [ 34.150424] parse addresses (20 bytes) @ fff000123fe7d080 [ 34.150439] start: 7fe01000000, end: 7fe0100000f, i: 10 ============= [ 34.150453] adding to system ... [ 34.150582] PCI: dev header type: 0 [ 34.150596] * /pci@1e,600000/usb@a [ 34.150630] create device, devfn: 50, type: [ 34.150655] class: 0xc0310 device name: 0001:00:0a.0 [ 34.150670] parse addresses (20 bytes) @ fff000123fe7aec0 [ 34.150686] start: 7ff01000000, end: 7ff01ffffff, i: 10 [ 34.150699] adding to system ... [ 34.150727] pci 0001:00:0a.0: PME# supported from D3cold [ 34.150888] PCI: dev header type: 0 [ 34.150902] * /pci@1e,600000/ide@d [ 34.150932] create device, devfn: 68, type: ide [ 34.150959] class: 0x101ff device name: 0001:00:0d.0 [ 34.150976] parse addresses (100 bytes) @ fff000123fe79900 [ 34.150991] start: 7fe01000900, end: 7fe01000907, i: 10 ============= [ 34.151006] start: 7fe01000918, end: 7fe0100091f, i: 14 ============= [ 34.151021] start: 7fe01000910, end: 7fe01000917, i: 18 ============== [ 34.151035] start: 7fe01000908, end: 7fe0100090f, i: 1c ============ [ 34.151050] start: 7fe01000920, end: 7fe0100092f, i: 20 ============= can you send out output for lspci -vvxxx lspci -tv Thanks Yinghai ^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: 4.3-rc3 BAR allocation problems on multiple machines 2015-10-13 19:43 ` Yinghai Lu @ 2015-10-13 20:39 ` Meelis Roos 2015-10-14 0:43 ` Yinghai Lu 0 siblings, 1 reply; 19+ messages in thread From: Meelis Roos @ 2015-10-13 20:39 UTC (permalink / raw) To: Yinghai Lu; +Cc: Linux Kernel list, linux-pci@vger.kernel.org > >> Can you send boot log after booting with "debug ignore_loglevel ofpci_debug=1" ? > > > > http://kodu.ut.ee/~mroos/dm/dm.v210+patch+debug > > Firmware does reported overlapped resources. [...] > can you send out output for > lspci -vvxxx > lspci -tv Here you are. 0000:00:02.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5704 Gigabit Ethernet Subsystem: Broadcom Corporation NetXtreme BCM5704 Gigabit Ethernet Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 64 (16000ns min), Cache Line Size: 64 bytes Interrupt: pin A routed to IRQ 6 Region 0: Memory at 00200000 (64-bit, non-prefetchable) [size=2M] Region 2: Memory at 00110000 (64-bit, non-prefetchable) [size=64K] Region 4: [virtual] Memory at fffff80900000000 (32-bit, non-prefetchable) Region 5: [virtual] Memory at fffff80900000000 (32-bit, non-prefetchable) Expansion ROM at fffff80900000000 [disabled] Capabilities: [40] PCI-X non-bridge device Command: DPERE- ERO+ RBC=512 OST=1 Status: Dev=ff:1f.0 64bit+ 133MHz+ SCD- USC- DC=simple DMMRBC=2048 DMOST=1 DMCRS=16 RSCEM- 266MHz- 533MHz- Capabilities: [48] Power Management version 2 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot+,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=1 PME- Capabilities: [50] Vital Product Data Not readable Capabilities: [58] MSI: Enable- Count=1/8 Maskable- 64bit+ Address: 2d92e07bc876dbd0 Data: 0c1b Kernel driver in use: tg3 00: e4 14 48 16 06 00 b0 02 00 00 00 02 10 40 80 00 10: 04 00 20 00 00 00 00 00 04 00 11 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 e4 14 48 16 30: 00 00 81 2b 40 00 00 00 00 00 00 00 a3 01 40 00 40: 07 48 02 00 f8 ff 43 04 01 50 02 40 00 20 00 00 50: 03 58 00 00 3b 79 48 4b 05 00 86 00 d0 db 76 c8 60: 7b e0 92 2d 1b 0c 00 00 98 02 03 20 00 00 3f 76 70: ee 00 00 00 c4 00 00 80 4c 5b 03 00 00 00 00 00 80: 00 00 00 00 00 59 b0 00 36 00 13 04 82 90 20 02 90: 09 97 00 01 01 00 00 00 00 00 00 00 f5 01 00 00 a0: 00 00 00 00 2d 01 00 00 00 00 00 00 e3 01 00 00 b0: 00 00 00 00 00 00 00 71 00 00 00 00 00 00 00 00 c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0000:00:02.1 Ethernet controller: Broadcom Corporation NetXtreme BCM5704 Gigabit Ethernet Subsystem: Oracle/SUN Device 1648 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 64 (16000ns min), Cache Line Size: 64 bytes Interrupt: pin B routed to IRQ 7 Region 0: Memory at 00400000 (64-bit, non-prefetchable) [size=2M] Region 2: Memory at 00120000 (64-bit, non-prefetchable) [size=64K] Region 4: [virtual] Memory at fffff80900000000 (32-bit, non-prefetchable) Region 5: [virtual] Memory at fffff80900000000 (32-bit, non-prefetchable) [virtual] Expansion ROM at fffff80900000000 [disabled] Capabilities: [40] PCI-X non-bridge device Command: DPERE- ERO+ RBC=512 OST=1 Status: Dev=ff:1f.1 64bit+ 133MHz+ SCD- USC- DC=simple DMMRBC=2048 DMOST=1 DMCRS=16 RSCEM- 266MHz- 533MHz- Capabilities: [48] Power Management version 2 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot+,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=1 PME- Capabilities: [50] Vital Product Data Not readable Capabilities: [58] MSI: Enable- Count=1/8 Maskable- 64bit+ Address: 2e047d69dfc7ac80 Data: d6f4 Kernel driver in use: tg3 00: e4 14 48 16 06 00 b0 02 00 00 00 02 10 40 80 00 10: 04 00 40 00 00 00 00 00 04 00 12 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 8e 10 48 16 30: 00 00 00 00 40 00 00 00 00 00 00 00 22 02 40 00 40: 07 48 02 00 f9 ff 43 04 01 50 02 40 00 20 00 00 50: 03 58 00 00 d8 30 08 01 05 00 86 00 80 ac c7 df 60: 69 7d 04 2e f4 d6 00 00 9a 02 03 20 00 00 3f 76 70: 0e 02 00 00 c4 00 00 00 00 00 00 00 00 00 00 00 80: e4 14 48 16 f8 80 3b 05 36 00 00 00 fe 90 60 02 90: 01 07 00 00 00 00 00 00 00 00 00 00 00 00 00 00 a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 b0: 00 00 00 00 00 00 00 00 04 00 00 00 00 00 00 00 c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0001:00:06.0 Non-VGA unclassified device: ULi Electronics Inc. M7101 Power Management Controller [PMU] Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Region 0: [virtual] I/O ports at <unassigned> [size=16] Region 1: [virtual] Memory at fffff80100000000 (32-bit, non-prefetchable) Region 2: [virtual] Memory at fffff80100000000 (32-bit, non-prefetchable) Region 3: [virtual] Memory at fffff80100000000 (32-bit, non-prefetchable) Region 4: [virtual] Memory at fffff80100000000 (32-bit, non-prefetchable) Region 5: [virtual] Memory at fffff80100000000 (32-bit, non-prefetchable) [virtual] Expansion ROM at fffff80100000000 [disabled] 00: b9 10 01 71 00 00 00 02 00 00 00 00 00 00 00 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 40: 00 00 00 00 00 00 20 00 08 18 08 00 00 00 00 00 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 40 01 70: 0f 11 00 00 00 00 00 08 00 00 00 00 00 00 00 00 80: 00 00 10 10 00 00 00 00 01 02 00 00 00 00 00 00 90: 00 00 00 00 00 00 00 08 00 00 01 00 00 00 00 00 a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 b0: 00 40 40 01 00 00 02 00 60 00 00 03 00 00 00 00 c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 d0: 00 06 00 00 00 00 00 00 00 00 00 00 0b 00 00 00 e0: 00 08 00 06 01 00 01 00 00 00 00 00 00 00 00 00 f0: 45 00 88 6e 00 00 00 00 00 00 00 00 00 00 00 00 0001:00:07.0 ISA bridge: ULi Electronics Inc. M1533/M1535/M1543 PCI to ISA Bridge [Aladdin IV/V/V+] Control: I/O+ Mem+ BusMaster+ SpecCycle+ MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0 Region 0: [virtual] I/O ports at 0000 [size=64K] Region 1: Memory at <unassigned> (32-bit, non-prefetchable) [size=1M] Region 2: Memory at <unassigned> (32-bit, non-prefetchable) [size=1M] Region 3: [virtual] Memory at fffff80100000000 (32-bit, non-prefetchable) Region 4: [virtual] Memory at fffff80100000000 (32-bit, non-prefetchable) Region 5: [virtual] Memory at fffff80100000000 (32-bit, non-prefetchable) [virtual] Expansion ROM at fffff80100000000 [disabled] Capabilities: [a0] Power Management version 1 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- 00: b9 10 33 15 0f 00 10 02 00 00 01 06 00 00 00 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 a0 00 00 00 00 00 00 00 00 00 00 00 40: 03 13 4b 80 83 09 00 47 00 00 06 00 00 00 eb 31 50: 00 00 00 20 90 02 20 03 66 03 00 00 00 00 00 08 60: 40 00 00 00 00 00 00 00 00 00 00 00 80 20 00 00 70: 00 00 0a 00 47 00 00 db 04 02 00 04 00 80 01 90 80: a5 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 a0: 01 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00 b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0001:00:0a.0 USB controller: ULi Electronics Inc. USB 1.1 Controller (rev 03) (prog-if 10 [OHCI]) Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Interrupt: pin A routed to IRQ 17 Region 0: Memory at 01000000 (32-bit, non-prefetchable) [disabled] [size=16M] Region 1: [virtual] Memory at fffff80100000000 (32-bit, non-prefetchable) Region 2: [virtual] Memory at fffff80100000000 (32-bit, non-prefetchable) Region 3: [virtual] Memory at fffff80100000000 (32-bit, non-prefetchable) Region 4: [virtual] Memory at fffff80100000000 (32-bit, non-prefetchable) Region 5: [virtual] Memory at fffff80100000000 (32-bit, non-prefetchable) [virtual] Expansion ROM at fffff80100000000 [disabled] Capabilities: [60] Power Management version 2 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold+) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- 00: b9 10 37 52 00 00 90 02 03 10 03 0c 00 40 00 00 10: 00 00 00 01 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 60 00 00 00 00 00 00 00 00 01 00 50 40: 00 00 0f 00 00 00 00 00 00 00 00 00 00 00 00 00 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 60: 01 00 02 80 00 00 00 00 00 00 00 00 00 00 00 00 70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0001:00:0d.0 IDE interface: ULi Electronics Inc. M5229 IDE (rev c4) (prog-if ff) Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 64 (500ns min, 1000ns max) Interrupt: pin A routed to IRQ 18 Region 0: I/O ports at 0900 [disabled] [size=8] Region 1: I/O ports at 0918 [disabled] [size=8] Region 2: I/O ports at 0910 [disabled] [size=8] Region 3: I/O ports at 0908 [disabled] [size=8] Region 4: I/O ports at 0920 [disabled] [size=16] Region 5: [virtual] Memory at fffff80100000000 (32-bit, non-prefetchable) [virtual] Expansion ROM at fffff80100000000 [disabled] Capabilities: [60] Power Management version 2 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- 00: b9 10 29 52 04 00 90 02 c4 ff 01 01 00 40 00 00 10: 01 09 00 00 19 09 00 00 11 09 00 00 09 09 00 00 20: 21 09 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 60 00 00 00 00 00 00 00 00 01 02 04 40: 00 00 00 7f 00 00 00 00 30 00 02 c0 00 80 ba 1a 50: 03 00 00 81 55 55 44 44 03 00 00 00 03 00 00 00 60: 01 00 02 00 00 00 00 00 00 00 00 00 00 00 00 00 70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0002:00:02.0 SCSI storage controller: LSI Logic / Symbios Logic 53c1010 66MHz Ultra3 SCSI Adapter (rev 01) Subsystem: LSI Logic / Symbios Logic LSI53C1000/1000R/1010R/1010-66 PCI to Ultra160 SCSI Controller Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr+ Stepping- SERR+ FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 64 (4250ns min, 4500ns max), Cache Line Size: 64 bytes Interrupt: pin A routed to IRQ 24 Region 0: I/O ports at 0900 [size=256] Region 1: Memory at 00100000 (64-bit, non-prefetchable) [size=8K] Region 3: Memory at 00102000 (64-bit, non-prefetchable) [size=8K] Region 5: [virtual] Memory at fffff83100000000 (32-bit, non-prefetchable) [virtual] Expansion ROM at fffff83100000000 [disabled] Capabilities: [40] Power Management version 2 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Kernel driver in use: sym53c8xx 00: 00 10 21 00 57 01 30 02 01 00 00 01 10 40 80 00 10: 01 09 00 00 04 00 10 00 00 00 00 00 04 20 10 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 10 00 10 30: 00 00 00 00 40 00 00 00 00 00 00 00 00 01 11 12 40: 01 00 02 06 00 00 00 00 00 00 00 00 00 00 00 00 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0002:00:02.1 SCSI storage controller: LSI Logic / Symbios Logic 53c1010 66MHz Ultra3 SCSI Adapter (rev 01) Subsystem: LSI Logic / Symbios Logic LSI53C1000/1000R/1010R/1010-66 PCI to Ultra160 SCSI Controller Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr+ Stepping- SERR+ FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 64 (4250ns min, 4500ns max), Cache Line Size: 64 bytes Interrupt: pin B routed to IRQ 25 Region 0: I/O ports at 0a00 [size=256] Region 1: Memory at 00104000 (64-bit, non-prefetchable) [size=8K] Region 3: Memory at 00106000 (64-bit, non-prefetchable) [size=8K] Region 5: [virtual] Memory at fffff83100000000 (32-bit, non-prefetchable) [virtual] Expansion ROM at fffff83100000000 [disabled] Capabilities: [40] Power Management version 2 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Kernel driver in use: sym53c8xx 00: 00 10 21 00 57 01 30 02 01 00 00 01 10 40 80 00 10: 01 0a 00 00 04 40 10 00 00 00 00 00 04 60 10 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 10 00 10 30: 00 00 00 00 40 00 00 00 00 00 00 00 00 02 11 12 40: 01 00 02 06 00 00 00 00 00 00 00 00 00 00 00 00 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0003:00:02.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5704 Gigabit Ethernet Subsystem: Oracle/SUN Device 1648 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 64 (16000ns min), Cache Line Size: 64 bytes Interrupt: pin A routed to IRQ 31 Region 0: Memory at 00200000 (64-bit, non-prefetchable) [size=2M] Region 2: Memory at 00110000 (64-bit, non-prefetchable) [size=64K] Region 4: [virtual] Memory at fffff83900000000 (32-bit, non-prefetchable) Region 5: [virtual] Memory at fffff83900000000 (32-bit, non-prefetchable) [virtual] Expansion ROM at fffff83900000000 [disabled] Capabilities: [40] PCI-X non-bridge device Command: DPERE- ERO+ RBC=512 OST=1 Status: Dev=ff:1f.0 64bit+ 133MHz+ SCD- USC- DC=simple DMMRBC=2048 DMOST=1 DMCRS=16 RSCEM- 266MHz- 533MHz- Capabilities: [48] Power Management version 2 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot+,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=1 PME- Capabilities: [50] Vital Product Data Not readable Capabilities: [58] MSI: Enable- Count=1/8 Maskable- 64bit+ Address: 3080414020d22000 Data: 3000 Kernel driver in use: tg3 00: e4 14 48 16 06 00 b0 02 00 00 00 02 10 40 80 00 10: 04 00 20 00 00 00 00 00 04 00 11 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 8e 10 48 16 30: 00 00 00 00 40 00 00 00 00 00 00 00 2d 01 40 00 40: 07 48 02 00 f8 ff 43 04 01 50 02 40 00 20 00 00 50: 03 58 00 00 08 04 10 40 05 00 86 00 00 20 d2 20 60: 40 41 80 30 00 30 00 00 9a 02 03 20 00 00 3f 76 70: 8e 02 00 00 c4 00 00 00 00 00 00 00 00 00 00 00 80: e4 14 48 16 ea ec 23 13 36 00 00 00 fe 90 20 02 90: 01 07 00 01 00 00 00 00 00 00 00 00 00 00 00 00 a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0003:00:02.1 Ethernet controller: Broadcom Corporation NetXtreme BCM5704 Gigabit Ethernet Subsystem: Oracle/SUN Device 1648 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 64 (16000ns min), Cache Line Size: 64 bytes Interrupt: pin B routed to IRQ 32 Region 0: Memory at 00400000 (64-bit, non-prefetchable) [size=2M] Region 2: Memory at 00120000 (64-bit, non-prefetchable) [size=64K] Region 4: [virtual] Memory at fffff83900000000 (32-bit, non-prefetchable) Region 5: [virtual] Memory at fffff83900000000 (32-bit, non-prefetchable) [virtual] Expansion ROM at fffff83900000000 [disabled] Capabilities: [40] PCI-X non-bridge device Command: DPERE- ERO+ RBC=512 OST=1 Status: Dev=ff:1f.1 64bit+ 133MHz+ SCD- USC- DC=simple DMMRBC=2048 DMOST=1 DMCRS=16 RSCEM- 266MHz- 533MHz- Capabilities: [48] Power Management version 2 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot+,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=1 PME- Capabilities: [50] Vital Product Data Not readable Capabilities: [58] MSI: Enable- Count=1/8 Maskable- 64bit+ Address: 30001484410f4000 Data: 0500 Kernel driver in use: tg3 00: e4 14 48 16 06 00 b0 02 00 00 00 02 10 40 80 00 10: 04 00 40 00 00 00 00 00 04 00 12 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 8e 10 48 16 30: 00 00 00 00 40 00 00 00 00 00 00 00 02 02 40 00 40: 07 48 02 00 f9 ff 43 04 01 50 02 40 00 20 00 00 50: 03 58 00 00 0c 01 12 02 05 00 86 00 00 40 0f 41 60: 84 14 00 30 00 05 00 00 9a 02 03 20 00 00 3f 76 70: 8e 02 00 00 c4 00 00 00 00 00 00 00 00 00 00 00 80: e4 14 48 16 60 8b 36 00 36 00 00 00 fe 90 60 02 90: 01 07 00 01 00 00 00 00 00 00 00 00 00 00 00 00 a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 b0: 00 00 00 00 00 00 00 00 04 00 00 00 00 00 00 00 c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 -+-[0003:00]-+-02.0 Broadcom Corporation NetXtreme BCM5704 Gigabit Ethernet | \-02.1 Broadcom Corporation NetXtreme BCM5704 Gigabit Ethernet +-[0002:00]-+-02.0 LSI Logic / Symbios Logic 53c1010 66MHz Ultra3 SCSI Adapter | \-02.1 LSI Logic / Symbios Logic 53c1010 66MHz Ultra3 SCSI Adapter +-[0001:00]-+-06.0 ULi Electronics Inc. M7101 Power Management Controller [PMU] | +-07.0 ULi Electronics Inc. M1533/M1535/M1543 PCI to ISA Bridge [Aladdin IV/V/V+] | +-0a.0 ULi Electronics Inc. USB 1.1 Controller | \-0d.0 ULi Electronics Inc. M5229 IDE \-[0000:00]-+-02.0 Broadcom Corporation NetXtreme BCM5704 Gigabit Ethernet \-02.1 Broadcom Corporation NetXtreme BCM5704 Gigabit Ethernet -- Meelis Roos (mroos@linux.ee) ^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: 4.3-rc3 BAR allocation problems on multiple machines 2015-10-13 20:39 ` Meelis Roos @ 2015-10-14 0:43 ` Yinghai Lu 2015-10-14 7:34 ` Meelis Roos 0 siblings, 1 reply; 19+ messages in thread From: Yinghai Lu @ 2015-10-14 0:43 UTC (permalink / raw) To: Meelis Roos; +Cc: Linux Kernel list, linux-pci@vger.kernel.org [-- Attachment #1: Type: text/plain, Size: 2088 bytes --] On Tue, Oct 13, 2015 at 1:39 PM, Meelis Roos <mroos@linux.ee> wrote: > > 0001:00:07.0 ISA bridge: ULi Electronics Inc. M1533/M1535/M1543 PCI to ISA Bridge [Aladdin IV/V/V+] > Control: I/O+ Mem+ BusMaster+ SpecCycle+ MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- > Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- > Latency: 0 > Region 0: [virtual] I/O ports at 0000 [size=64K] > Region 1: Memory at <unassigned> (32-bit, non-prefetchable) [size=1M] > Region 2: Memory at <unassigned> (32-bit, non-prefetchable) [size=1M] > Region 3: [virtual] Memory at fffff80100000000 (32-bit, non-prefetchable) > Region 4: [virtual] Memory at fffff80100000000 (32-bit, non-prefetchable) > Region 5: [virtual] Memory at fffff80100000000 (32-bit, non-prefetchable) > [virtual] Expansion ROM at fffff80100000000 [disabled] > Capabilities: [a0] Power Management version 1 > Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) > Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- > 00: b9 10 33 15 0f 00 10 02 00 00 01 06 00 00 00 00 > 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 30: 00 00 00 00 a0 00 00 00 00 00 00 00 00 00 00 00 > 40: 03 13 4b 80 83 09 00 47 00 00 06 00 00 00 eb 31 > 50: 00 00 00 20 90 02 20 03 66 03 00 00 00 00 00 08 > 60: 40 00 00 00 00 00 00 00 00 00 00 00 80 20 00 00 > 70: 00 00 0a 00 47 00 00 db 04 02 00 04 00 80 01 90 > 80: a5 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > a0: 01 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00 > b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 Please check attached patch. Thanks Yinghai [-- Attachment #2: sparc_no_bar_for_uli_1533.patch --] [-- Type: text/x-patch, Size: 3605 bytes --] Subject: [PATCH] PCI: Ignore BAR for ALi M1533 PCI-ISA bridge Meelis reported strange conflicts on sparc v210: pci 0001:00:07.0: can't claim BAR 2 [mem 0x7ff00000000-0x7ff000fffff]: address conflict with 0001:00:07.0 [mem 0x7ff00000000-0x7ff000fffff] pci 0001:00:06.0: can't claim BAR 0 [io 0x7fe01000000-0x7fe0100000f]: address conflict with 0001:00:07.0 [io 0x7fe01000000-0x7fe0100ffff] pci 0001:00:0d.0: can't claim BAR 0 [io 0x7fe01000900-0x7fe01000907]: address conflict with 0001:00:07.0 [io 0x7fe01000000-0x7fe0100ffff] pci 0001:00:0d.0: can't claim BAR 1 [io 0x7fe01000918-0x7fe0100091f]: address conflict with 0001:00:07.0 [io 0x7fe01000000-0x7fe0100ffff] pci 0001:00:0d.0: can't claim BAR 2 [io 0x7fe01000910-0x7fe01000917]: address conflict with 0001:00:07.0 [io 0x7fe01000000-0x7fe0100ffff] pci 0001:00:0d.0: can't claim BAR 3 [io 0x7fe01000908-0x7fe0100090f]: address conflict with 0001:00:07.0 [io 0x7fe01000000-0x7fe0100ffff] pci 0001:00:0d.0: can't claim BAR 4 [io 0x7fe01000920-0x7fe0100092f]: address conflict with 0001:00:07.0 [io 0x7fe01000000-0x7fe0100ffff] PCI: /pci@1e,600000 can't claim Video RAM area [mem 0x7ff000a0000-0x7ff000bffff]: address conflict with 0001:00:07.0 [mem 0x7ff00000000-0x7ff000fffff] PCI: /pci@1e,600000 can't claim System ROM [mem 0x7ff000f0000-0x7ff000fffff]: address conflict with 0001:00:07.0 [mem 0x7ff00000000-0x7ff000fffff] PCI: /pci@1e,600000 can't claim Video ROM [mem 0x7ff000c0000-0x7ff000c7fff]: address conflict with 0001:00:07.0 [mem 0x7ff00000000-0x7ff000fffff] we have pci_bus 0001:00: root bus resource [io 0x7fe01000000-0x7fe01ffffff] (bus address [0x0000-0xffffff]) pci_bus 0001:00: root bus resource [mem 0x7ff00000000-0x7ffffffffff] (bus address [0x00000000-0xffffffff]) so pci bus address in the bars for 0001:00:07.0 has all 0s. 0001:00:07.0 ISA bridge: ULi Electronics Inc. M1533/M1535/M1543 PCI to ISA Bridge [Aladdin IV/V/V+] Region 0: [virtual] I/O ports at 0000 [size=64K] Region 1: Memory at <unassigned> (32-bit, non-prefetchable) [size=1M] Region 2: Memory at <unassigned> (32-bit, non-prefetchable) [size=1M] 00: b9 10 33 15 0f 00 10 02 00 00 01 06 00 00 00 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 a0 00 00 00 00 00 00 00 00 00 00 00 According to http://www.versalogic.com/Support/Downloads/pdf/ali1543.pdf page 28: The indices before 40h are read-only. and we have all 0 from 0x10-0x2f, according to lspci. So clean flags, and ignore them all the way include claim and sizing and alloc etc. Reported-by: Meelis Roos <mroos@linux.ee> Signed-off-by: Yinghai Lu <yinghai@kernel.org> --- drivers/pci/quirks.c | 15 +++++++++++++++ 1 file changed, 15 insertions(+) Index: linux-2.6/drivers/pci/quirks.c =================================================================== --- linux-2.6.orig/drivers/pci/quirks.c +++ linux-2.6/drivers/pci/quirks.c @@ -470,6 +470,21 @@ static void quirk_amd_nl_class(struct pc DECLARE_PCI_FIXUP_HEADER(PCI_VENDOR_ID_AMD, PCI_DEVICE_ID_AMD_NL_USB, quirk_amd_nl_class); + +/* + * ALi m1533 pci to isa bridge does not have BAR according to datasheet, + * clear the flags, so we will try to claim them or reallocate res. + */ +static void quirk_ali1533(struct pci_dev *dev) +{ + int i; + + for (i = 0; i < PCI_ROM_RESOURCE; i++) + dev->resource[i].flags = 0; +} +DECLARE_PCI_FIXUP_HEADER(PCI_VENDOR_ID_AL, PCI_DEVICE_ID_AL_M1533, + quirk_ali1533); + static void piix4_io_quirk(struct pci_dev *dev, const char *name, unsigned int port, unsigned int enable) { u32 devres; ^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: 4.3-rc3 BAR allocation problems on multiple machines 2015-10-14 0:43 ` Yinghai Lu @ 2015-10-14 7:34 ` Meelis Roos 2015-10-14 21:45 ` Yinghai Lu 0 siblings, 1 reply; 19+ messages in thread From: Meelis Roos @ 2015-10-14 7:34 UTC (permalink / raw) To: Yinghai Lu; +Cc: Linux Kernel list, linux-pci@vger.kernel.org > > 0001:00:07.0 ISA bridge: ULi Electronics Inc. M1533/M1535/M1543 PCI to ISA Bridge [Aladdin IV/V/V+] > > Control: I/O+ Mem+ BusMaster+ SpecCycle+ MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- > > Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- > > Latency: 0 > > Region 0: [virtual] I/O ports at 0000 [size=64K] > > Region 1: Memory at <unassigned> (32-bit, non-prefetchable) [size=1M] > > Region 2: Memory at <unassigned> (32-bit, non-prefetchable) [size=1M] > > Region 3: [virtual] Memory at fffff80100000000 (32-bit, non-prefetchable) > > Region 4: [virtual] Memory at fffff80100000000 (32-bit, non-prefetchable) > > Region 5: [virtual] Memory at fffff80100000000 (32-bit, non-prefetchable) > > [virtual] Expansion ROM at fffff80100000000 [disabled] > > Capabilities: [a0] Power Management version 1 > > Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) > > Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- > > 00: b9 10 33 15 0f 00 10 02 00 00 01 06 00 00 00 00 > > 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > > 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > > 30: 00 00 00 00 a0 00 00 00 00 00 00 00 00 00 00 00 > > 40: 03 13 4b 80 83 09 00 47 00 00 06 00 00 00 eb 31 > > 50: 00 00 00 20 90 02 20 03 66 03 00 00 00 00 00 08 > > 60: 40 00 00 00 00 00 00 00 00 00 00 00 80 20 00 00 > > 70: 00 00 0a 00 47 00 00 db 04 02 00 04 00 80 01 90 > > 80: a5 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > > 90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > > a0: 01 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00 > > b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > > c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > > d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > > e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > > f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > > Please check attached patch. Thank you, it seems to work. First, the following lines are gone: PCI: Claiming 0001:00:07.0: Resource 0: 000007fe01000000..000007fe0100ffff [101] PCI: Claiming 0001:00:07.0: Resource 1: 000007ff00000000..000007ff000fffff [200] PCI: Claiming 0001:00:07.0: Resource 2: 000007ff00000000..000007ff000fffff [200] And then all following PCI: Claiming... lines succeed, with no address conflicts. Now, how can I be sure that removing the ULi ISA bridge allocations does not break anything? It seems I did not have I2C enabled in kernel conf - I emabled it now, recompiled, got this but it seems to be for another PCI device so not related? ali15x3_smbus 0001:00:06.0: ALI15X3_smb region uninitialized - upgrade BIOS or use force_addr=0xaddr ali15x3_smbus 0001:00:06.0: ALI15X3 not detected, module not inserted. Additionally, another driver (i2c-ali1535) claimed 0001:00:06.0 and was happy but did not find anything (but I do not know what it sahould find so I can see no problem at the moment). I also applied the patch on Sun Blade 100 where i2c was working for me. It was still working with this ali quirk patch applied, and no BAR errors. What about other arches - does this patch affect other arches where the firmware has configured some addresses for this ULi bridge? -- Meelis Roos (mroos@linux.ee) ^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: 4.3-rc3 BAR allocation problems on multiple machines 2015-10-14 7:34 ` Meelis Roos @ 2015-10-14 21:45 ` Yinghai Lu 0 siblings, 0 replies; 19+ messages in thread From: Yinghai Lu @ 2015-10-14 21:45 UTC (permalink / raw) To: Meelis Roos; +Cc: Linux Kernel list, linux-pci@vger.kernel.org On Wed, Oct 14, 2015 at 12:34 AM, Meelis Roos <mroos@linux.ee> wrote: >> > 0001:00:07.0 ISA bridge: ULi Electronics Inc. M1533/M1535/M1543 PCI to ISA Bridge [Aladdin IV/V/V+] >> > Control: I/O+ Mem+ BusMaster+ SpecCycle+ MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- >> > Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- >> > Latency: 0 >> > Region 0: [virtual] I/O ports at 0000 [size=64K] >> > Region 1: Memory at <unassigned> (32-bit, non-prefetchable) [size=1M] >> > Region 2: Memory at <unassigned> (32-bit, non-prefetchable) [size=1M] >> > Region 3: [virtual] Memory at fffff80100000000 (32-bit, non-prefetchable) >> > Region 4: [virtual] Memory at fffff80100000000 (32-bit, non-prefetchable) >> > Region 5: [virtual] Memory at fffff80100000000 (32-bit, non-prefetchable) >> > [virtual] Expansion ROM at fffff80100000000 [disabled] >> > Capabilities: [a0] Power Management version 1 >> > Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) >> > Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- >> > 00: b9 10 33 15 0f 00 10 02 00 00 01 06 00 00 00 00 >> > 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 >> > 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 >> > 30: 00 00 00 00 a0 00 00 00 00 00 00 00 00 00 00 00 >> > 40: 03 13 4b 80 83 09 00 47 00 00 06 00 00 00 eb 31 >> > 50: 00 00 00 20 90 02 20 03 66 03 00 00 00 00 00 08 >> > 60: 40 00 00 00 00 00 00 00 00 00 00 00 80 20 00 00 >> > 70: 00 00 0a 00 47 00 00 db 04 02 00 04 00 80 01 90 >> > 80: a5 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 >> > 90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 >> > a0: 01 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00 >> > b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 >> > c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 >> > d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 >> > e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 >> > f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 >> >> Please check attached patch. > > Thank you, it seems to work. First, the following lines are gone: > PCI: Claiming 0001:00:07.0: Resource 0: 000007fe01000000..000007fe0100ffff [101] > PCI: Claiming 0001:00:07.0: Resource 1: 000007ff00000000..000007ff000fffff [200] > PCI: Claiming 0001:00:07.0: Resource 2: 000007ff00000000..000007ff000fffff [200] > > And then all following PCI: Claiming... lines succeed, with no address > conflicts. > > Now, how can I be sure that removing the ULi ISA bridge allocations does > not break anything? It seems I did not have I2C enabled in kernel conf - > I emabled it now, recompiled, got this but it seems to be for another > PCI device so not related? > ali15x3_smbus 0001:00:06.0: ALI15X3_smb region uninitialized - upgrade BIOS or use force_addr=0xaddr > ali15x3_smbus 0001:00:06.0: ALI15X3 not detected, module not inserted. code segment: /* Determine the address of the SMBus area */ pci_read_config_word(ALI15X3_dev, SMBBA, &ali15x3_smba); ali15x3_smba &= (0xffff & ~(ALI15X3_SMB_IOSIZE - 1)); if (ali15x3_smba == 0 && force_addr == 0) { dev_err(&ALI15X3_dev->dev, "ALI15X3_smb region uninitialized " "- upgrade BIOS or use force_addr=0xaddr\n"); return -ENODEV; } SMBBA is 0x14 from lspci: 0001:00:06.0 Non-VGA unclassified device: ULi Electronics Inc. M7101 Power Management Controller [PMU] Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Region 0: [virtual] I/O ports at <unassigned> [size=16] [virtual] Expansion ROM at fffff80100000000 [disabled] 00: b9 10 01 71 00 00 00 02 00 00 00 00 00 00 00 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x14 BAR has 0 really. > > Additionally, another driver (i2c-ali1535) claimed 0001:00:06.0 and was > happy but did not find anything (but I do not know what it sahould find > so I can see no problem at the moment). it should complain too: /* Determine the address of the SMBus area */ pci_read_config_word(dev, SMBBA, &ali1535_offset); dev_dbg(&dev->dev, "ALI1535_smb is at offset 0x%04x\n", ali1535_offset); ali1535_offset &= (0xffff & ~(ALI1535_SMB_IOSIZE - 1)); if (ali1535_offset == 0) { dev_warn(&dev->dev, "ALI1535_smb region uninitialized - upgrade BIOS?\n"); retval = -ENODEV; goto exit; } > > I also applied the patch on Sun Blade 100 where i2c was working for me. > It was still working with this ali quirk patch applied, and no BAR > errors. Good. assume v210 does use those for i2c. > > What about other arches - does this patch affect other arches where the > firmware has configured some addresses for this ULi bridge? According to data sheet, those BAR on 00:07.0 are all 0, and read only. Not sure how are those to to use them. Thanks Yinghai ^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: 4.3-rc3 BAR allocation problems on multiple machines 2015-10-13 5:06 ` Meelis Roos 2015-10-13 5:43 ` Yinghai Lu @ 2015-10-13 6:19 ` Yinghai Lu 1 sibling, 0 replies; 19+ messages in thread From: Yinghai Lu @ 2015-10-13 6:19 UTC (permalink / raw) To: Meelis Roos; +Cc: Linux Kernel list, linux-pci@vger.kernel.org On Mon, Oct 12, 2015 at 10:06 PM, Meelis Roos <mroos@linux.ee> wrote: >> >> > sparc64 machines: > > 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 other warning: [ 38.829890] pci 0001:00:07.0: can't claim BAR 2 [mem 0x7ff00000000-0x7ff000fffff]: address conflict with 0001:00:07.0 [mem 0x7ff00000000-0x7ff000fffff] [ 38.829924] pci 0001:00:06.0: can't claim BAR 0 [io 0x7fe01000000-0x7fe0100000f]: address conflict with 0001:00:07.0 [io 0x7fe01000000-0x7fe0100ffff] [ 38.829957] pci 0001:00:0d.0: can't claim BAR 0 [io 0x7fe01000900-0x7fe01000907]: address conflict with 0001:00:07.0 [io 0x7fe01000000-0x7fe0100ffff] [ 38.829988] pci 0001:00:0d.0: can't claim BAR 1 [io 0x7fe01000918-0x7fe0100091f]: address conflict with 0001:00:07.0 [io 0x7fe01000000-0x7fe0100ffff] [ 38.830019] pci 0001:00:0d.0: can't claim BAR 2 [io 0x7fe01000910-0x7fe01000917]: address conflict with 0001:00:07.0 [io 0x7fe01000000-0x7fe0100ffff] [ 38.830050] pci 0001:00:0d.0: can't claim BAR 3 [io 0x7fe01000908-0x7fe0100090f]: address conflict with 0001:00:07.0 [io 0x7fe01000000-0x7fe0100ffff] [ 38.830081] pci 0001:00:0d.0: can't claim BAR 4 [io 0x7fe01000920-0x7fe0100092f]: address conflict with 0001:00:07.0 [io 0x7fe01000000-0x7fe0100ffff] are real overlapping 1. between BAR1 and BAR2 for 0001:00:07.0. 2. between BAR from 0001:00:07.0 and 0001:00:06.0 io. I would suspect 00001:00:07.0 is not assigned by firmware. [ 38.830112] PCI: /pci@1e,600000 can't claim Video RAM area [mem 0x7ff000a0000-0x7ff000bffff]: address conflict with 0001:00:07.0 [mem 0x7ff00000000-0x7ff000fffff] [ 38.830150] PCI: /pci@1e,600000 can't claim System ROM [mem 0x7ff000f0000-0x7ff000fffff]: address conflict with 0001:00:07.0 [mem 0x7ff00000000-0x7ff000fffff] [ 38.830187] PCI: /pci@1e,600000 can't claim Video ROM [mem 0x7ff000c0000-0x7ff000c7fff]: address conflict with 0001:00:07.0 [mem 0x7ff00000000-0x7ff000fffff] those are intended. Anyway OBP does not assign resource to 00001:00:07.0 ? Thanks Yinghai ^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: 4.3-rc3 BAR allocation problems on multiple machines 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-07 23:16 ` Yinghai Lu 2015-10-08 14:47 ` Bjorn Helgaas 2016-10-26 21:50 ` Bjorn Helgaas 2 siblings, 1 reply; 19+ messages in thread From: Yinghai Lu @ 2015-10-07 23:16 UTC (permalink / raw) To: Meelis Roos; +Cc: Linux Kernel list, linux-pci@vger.kernel.org On Wed, Oct 7, 2015 at 2:25 AM, Meelis Roos <mroos@linux.ee> wrote: > amd64 machine: > > http://kodu.ut.ee/~mroos/dm/dm.x2100 [ 0.156360] bus: [bus 00-05] on node 0 link 0 [ 0.156362] bus: 00 [io 0x0000-0xffff] [ 0.156364] bus: 00 [mem 0x000a0000-0x000bffff] [ 0.156365] bus: 00 [mem 0xfe030000-0xffffffff] [ 0.156366] bus: 00 [mem 0xc0000000-0xefffffff] [ 0.156368] bus: 00 [mem 0xf0000000-0xfe02ffff] [ 0.156369] bus: 00 [mem 0x140000000-0xfcffffffff] [ 0.174069] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug [ 0.180821] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-05]) [ 0.180943] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI] [ 0.181139] acpi PNP0A08:00: _OSC failed (AE_NOT_FOUND); disabling ASPM [ 0.181917] PCI host bridge to bus 0000:00 [ 0.182030] pci_bus 0000:00: root bus resource [bus 00-05] [ 0.182144] pci_bus 0000:00: root bus resource [io 0x0000-0x03af window] [ 0.182262] pci_bus 0000:00: root bus resource [io 0x03e0-0x0cf7 window] [ 0.182379] pci_bus 0000:00: root bus resource [io 0x6000-0xffff window] [ 0.182494] pci_bus 0000:00: root bus resource [io 0x03b0-0x03df window] [ 0.182609] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff window] [ 0.182799] pci_bus 0000:00: root bus resource [mem 0xc0000000-0xdfffffff window] [ 0.182989] pci_bus 0000:00: root bus resource [mem 0xf0000000-0xfe02ffff window] [ 0.183179] pci_bus 0000:00: root bus resource [mem 0xfeb00000-0xfebfffff window] BIOS report different resource from _CRS setting and setting with cpu registers. [ 0.183379] pci 0000:00:00.0: [10de:005e] type 00 class 0x058000 [ 0.183542] pci 0000:00:01.0: [10de:0050] type 00 class 0x060100 root bus io range from _CRS does not include that. boot with pci=nocrs should avoid that and it is safe as we get ranges from register. Thanks Yinghai ^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: 4.3-rc3 BAR allocation problems on multiple machines 2015-10-07 23:16 ` Yinghai Lu @ 2015-10-08 14:47 ` Bjorn Helgaas 0 siblings, 0 replies; 19+ messages in thread From: Bjorn Helgaas @ 2015-10-08 14:47 UTC (permalink / raw) To: Yinghai Lu; +Cc: Meelis Roos, Linux Kernel list, linux-pci@vger.kernel.org On Wed, Oct 07, 2015 at 04:16:37PM -0700, Yinghai Lu wrote: > On Wed, Oct 7, 2015 at 2:25 AM, Meelis Roos <mroos@linux.ee> wrote: > > amd64 machine: > > > > http://kodu.ut.ee/~mroos/dm/dm.x2100 > > [ 0.156360] bus: [bus 00-05] on node 0 link 0 > [ 0.156362] bus: 00 [io 0x0000-0xffff] > [ 0.156364] bus: 00 [mem 0x000a0000-0x000bffff] > [ 0.156365] bus: 00 [mem 0xfe030000-0xffffffff] > [ 0.156366] bus: 00 [mem 0xc0000000-0xefffffff] > [ 0.156368] bus: 00 [mem 0xf0000000-0xfe02ffff] > [ 0.156369] bus: 00 [mem 0x140000000-0xfcffffffff] > > [ 0.174069] PCI: Using host bridge windows from ACPI; if necessary, > use "pci=nocrs" and report a bug > [ 0.180821] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-05]) > [ 0.180943] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM > ClockPM Segments MSI] > [ 0.181139] acpi PNP0A08:00: _OSC failed (AE_NOT_FOUND); disabling ASPM > [ 0.181917] PCI host bridge to bus 0000:00 > [ 0.182030] pci_bus 0000:00: root bus resource [bus 00-05] > [ 0.182144] pci_bus 0000:00: root bus resource [io 0x0000-0x03af window] > [ 0.182262] pci_bus 0000:00: root bus resource [io 0x03e0-0x0cf7 window] > [ 0.182379] pci_bus 0000:00: root bus resource [io 0x6000-0xffff window] > [ 0.182494] pci_bus 0000:00: root bus resource [io 0x03b0-0x03df window] > [ 0.182609] pci_bus 0000:00: root bus resource [mem > 0x000a0000-0x000bffff window] > [ 0.182799] pci_bus 0000:00: root bus resource [mem > 0xc0000000-0xdfffffff window] > [ 0.182989] pci_bus 0000:00: root bus resource [mem > 0xf0000000-0xfe02ffff window] > [ 0.183179] pci_bus 0000:00: root bus resource [mem > 0xfeb00000-0xfebfffff window] > > BIOS report different resource from _CRS setting and setting with cpu registers. > > [ 0.183379] pci 0000:00:00.0: [10de:005e] type 00 class 0x058000 > [ 0.183542] pci 0000:00:01.0: [10de:0050] type 00 class 0x060100 I don't know how the above two devices are related, since they don't have any BARs at all. But 00:01.1 does have two I/O BARs that are invalid per _CRS: pci 0000:00:01.1: can't claim BAR 4 [io 0x1c00-0x1c3f]: no compatible bridge window pci 0000:00:01.1: can't claim BAR 5 [io 0x1c40-0x1c7f]: no compatible bridge window > root bus io range from _CRS does not include that. > > boot with pci=nocrs should avoid that and it is safe as we get ranges > from register. As far as I'm concerned, it is not safe to use "pci=nocrs" in this situation. The BIOS programmed the hardware aperture ("bus: 00 [io 0x0000-0xffff]") *and* it explicitly excluded pieces of that range when it told the OS what it could use. The OS has to assume the BIOS knows what it is doing and is using those excluded ranges for something else, so it is *not* safe for the OS to put devices there. It's certainly possible and even likely that this is a BIOS defect. But we cannot assume "pci=nocrs" is safe in general. If you want to tell users to boot with "pci=nocrs", that's up to you. Personally, I don't think that's an acceptable user experience. Bjorn ^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: 4.3-rc3 BAR allocation problems on multiple machines 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-07 23:16 ` Yinghai Lu @ 2016-10-26 21:50 ` Bjorn Helgaas 2016-10-27 15:35 ` Meelis Roos 2 siblings, 1 reply; 19+ messages in thread From: Bjorn Helgaas @ 2016-10-26 21:50 UTC (permalink / raw) To: Meelis Roos; +Cc: Yinghai Lu, Linux Kernel list, linux-pci Hi Meelis, On Wed, Oct 07, 2015 at 12:25:19PM +0300, Meelis Roos wrote: > First I noticed that on Sun Netra t1-150 (sparc64 CPU), PCI allocation > was failing for qla1280 scsi driver. Reading dmesg uncovered "can't > claim BAR" errors. Looking for this in my other test machines I see more > of them - on many sparc64 machines and some on x86. > > In another thread for "Resource allocation cleanup for v4.4", Yinghai Lu > asked for full dmesg to solve another similar case. So to help > understanding this one, here are the dmesgs of my machines: > > 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 > > amd64 machine: > > http://kodu.ut.ee/~mroos/dm/dm.x2100 I'm looking through the PCI bugs in bugzilla.kernel.org and came across one that I opened for this issue (https://bugzilla.kernel.org/show_bug.cgi?id=117191) Is this still an issue? I've applied some patches from Yinghai, but I know there are a bunch more in the queue, so I'm trying to figure out what's fixed and what's still broken. Bjorn ^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: 4.3-rc3 BAR allocation problems on multiple machines 2016-10-26 21:50 ` Bjorn Helgaas @ 2016-10-27 15:35 ` Meelis Roos 0 siblings, 0 replies; 19+ messages in thread From: Meelis Roos @ 2016-10-27 15:35 UTC (permalink / raw) To: Bjorn Helgaas; +Cc: Yinghai Lu, Linux Kernel list, linux-pci On Wed, 26 Oct 2016, Bjorn Helgaas wrote: > Hi Meelis, > > On Wed, Oct 07, 2015 at 12:25:19PM +0300, Meelis Roos wrote: > > First I noticed that on Sun Netra t1-150 (sparc64 CPU), PCI allocation > > was failing for qla1280 scsi driver. Reading dmesg uncovered "can't > > claim BAR" errors. Looking for this in my other test machines I see more > > of them - on many sparc64 machines and some on x86. > > > > In another thread for "Resource allocation cleanup for v4.4", Yinghai Lu > > asked for full dmesg to solve another similar case. So to help > > understanding this one, here are the dmesgs of my machines: > I'm looking through the PCI bugs in bugzilla.kernel.org and came > across one that I opened for this issue > (https://bugzilla.kernel.org/show_bug.cgi?id=117191) > > Is this still an issue? I've applied some patches from Yinghai, but I > know there are a bunch more in the queue, so I'm trying to figure out > what's fixed and what's still broken. All of these issues seem to be still present: > > > > sparc64 machines: > > > > http://kodu.ut.ee/~mroos/dm/dm.t1-105 Still present in 4.8.0-09031-g95107b3: [ 21.143842] pci 0000:00:01.0: can't claim BAR 8 [mem 0x1ff00000000-0x1ffbfffffff]: address conflict with Video RAM area [??? 0x1ff000a0000-0x1ff000bffff flags 0x80000000] [ 21.143947] pci 0000:02:01.0: can't claim BAR 8 [mem 0x1ff00100000-0x1ff028fffff]: no compatible bridge window [ 21.144020] pci 0000:03:0f.0: can't claim BAR 8 [mem 0x1ff00100000-0x1ff028fffff]: no compatible bridge window [ 21.144087] pci 0000:04:00.0: can't claim BAR 0 [mem 0x1ff01000000-0x1ff01ffffff]: no compatible bridge window [ 21.144153] pci 0000:04:00.0: can't claim BAR 1 [mem 0x1ff02000000-0x1ff027fffff]: no compatible bridge window [ 21.144220] pci 0000:04:00.1: can't claim BAR 0 [mem 0x1ff02800000-0x1ff0280702f]: no compatible bridge window [ 21.144288] pci 0000:04:04.0: can't claim BAR 1 [mem 0x1ff02808000-0x1ff02808fff]: no compatible bridge window [ 21.144355] pci 0000:04:04.0: can't claim BAR 6 [mem 0x1ff02810000-0x1ff0281ffff]: no compatible bridge window ... [ 50.775038] qla1280 0000:04:04.0: can't ioremap BAR 1: [mem size 0x00001000] [ 50.883435] qla1280: Unable to map I/O memory > > http://kodu.ut.ee/~mroos/dm/dm.t1-200 Still present in 4.8.0-09031-g95107b3: [ 51.138280] pci 0000:00:01.0: can't claim BAR 8 [mem 0x1ff00000000-0x1ffbfffffff]: address conflict with Video RAM area [??? 0x1ff000a0000-0x1ff000bffff flags 0x80000000] [ 51.138399] pci 0000:02:08.0: can't claim BAR 1 [mem 0x1ff00002000-0x1ff00003fff 64bit]: no compatible bridge window [ 51.138461] pci 0000:02:08.0: can't claim BAR 3 [mem 0x1ff00004000-0x1ff00005fff 64bit]: no compatible bridge window [ 51.138522] pci 0000:02:08.1: can't claim BAR 1 [mem 0x1ff00006000-0x1ff00007fff 64bit]: no compatible bridge window [ 51.138580] pci 0000:02:08.1: can't claim BAR 3 [mem 0x1ff00008000-0x1ff00009fff 64bit]: no compatible bridge window [ 51.138639] pci 0000:02:05.0: can't claim BAR 1 [mem 0x1ff0000a000-0x1ff0000bfff]: no compatible bridge window [ 51.138695] pci 0000:02:05.0: can't claim BAR 6 [mem 0x1ff00020000-0x1ff0003ffff]: no compatible bridge window > > http://kodu.ut.ee/~mroos/dm/dm.v120 Still present in 4.8.0-09031-g95107b3: [ 51.025122] pci 0000:00:01.0: can't claim BAR 8 [mem 0x1ff00000000-0x1ffbfffffff]: address conflict with Video RAM area [??? 0x1ff000a0000-0x1ff000bffff flags 0x80000000] [ 51.025240] pci 0000:02:08.0: can't claim BAR 1 [mem 0x1ff00002000-0x1ff00003fff 64bit]: no compatible bridge window [ 51.025302] pci 0000:02:08.0: can't claim BAR 3 [mem 0x1ff00004000-0x1ff00005fff 64bit]: no compatible bridge window [ 51.025363] pci 0000:02:08.1: can't claim BAR 1 [mem 0x1ff00006000-0x1ff00007fff 64bit]: no compatible bridge window [ 51.025423] pci 0000:02:08.1: can't claim BAR 3 [mem 0x1ff00008000-0x1ff00009fff 64bit]: no compatible bridge window > > http://kodu.ut.ee/~mroos/dm/dm.v210 Still present in 4.8.0: Oct 5 13:56:52 v210 kernel: [ 39.003270] PCI: Claiming 0001:00:07.0: Resource 0: 000007fe01000000..000007fe0100ffff [101] Oct 5 13:56:52 v210 kernel: [ 39.003309] pci 0001:00:07.0: can't claim BAR 0 [io 0x7fe01000000-0x7fe0100ffff]: address conflict with 0001:00:06.0 [io 0x7fe01000600-0x7fe0100061f]Oct 5 13:56:52 v210 kernel: [ 39.003350] PCI: Claiming 0001:00:07.0: Resource 1: 000007ff00000000..000007ff000fffff [200] Oct 5 13:56:52 v210 kernel: [ 39.003389] pci 0001:00:07.0: can't claim BAR 1 [mem 0x7ff00000000-0x7ff000fffff]: address conflict with Video RAM area [??? 0x7ff000a0000-0x7ff000bffff flags 0x80000000] Oct 5 13:56:52 v210 kernel: [ 39.003437] PCI: Claiming 0001:00:07.0: Resource 2: 000007ff00000000..000007ff000fffff [200] Oct 5 13:56:52 v210 kernel: [ 39.003474] pci 0001:00:07.0: can't claim BAR 2 [mem 0x7ff00000000-0x7ff000fffff]: address conflict with Video RAM area [??? 0x7ff000a0000-0x7ff000bffff flags 0x80000000] > > http://kodu.ut.ee/~mroos/dm/dm.v240 Still present in 4.8.0-09031-g95107b3: [ 41.120991] pci 0001:00:07.0: can't claim BAR 0 [io 0x7fe01000000-0x7fe0100ffff]: address conflict with 0001:00:06.0 [io 0x7fe01000600-0x7fe0100061f] [ 41.121054] pci 0001:00:07.0: can't claim BAR 1 [mem 0x7ff00000000-0x7ff000fffff]: address conflict with Video RAM area [??? 0x7ff000a0000-0x7ff000bffff flags 0x80000000] [ 41.121122] pci 0001:00:07.0: can't claim BAR 2 [mem 0x7ff00000000-0x7ff000fffff]: address conflict with Video RAM area [??? 0x7ff000a0000-0x7ff000bffff flags 0x80000000] > > http://kodu.ut.ee/~mroos/dm/dm.sb100 Still present in 4.9.0-rc1-00067-g1a1891d: [ 41.280647] pci 0000:00:07.0: can't claim BAR 0 [io 0x1fe02000000-0x1fe0200ffff]: address conflict with 0000:00:03.0 [io 0x1fe02000600-0x1fe0200061f] [ 41.282521] pci 0000:00:07.0: can't claim BAR 1 [mem 0x1ff00000000-0x1ff000fffff]: address conflict with Video RAM area [??? 0x1ff000a0000-0x1ff000bffff flags 0x80000000] > > amd64 machine: > > > > http://kodu.ut.ee/~mroos/dm/dm.x2100 Still present in 4.8.0: [ 0.242410] pci 0000:00:01.1: can't claim BAR 4 [io 0x1c00-0x1c3f]: no compatible bridge window [ 0.242609] pci 0000:00:01.1: can't claim BAR 5 [io 0x1c40-0x1c7f]: no compatible bridge window -- Meelis Roos (mroos@linux.ee) ^ permalink raw reply [flat|nested] 19+ messages in thread
end of thread, other threads:[~2016-10-27 15:35 UTC | newest] Thread overview: 19+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 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 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
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).