Bug 117191
|
Description
Bjorn Helgaas
2016-04-25 20:36:53 UTC
Created attachment 214231 [details]
dmesg - sb100
Created attachment 214241 [details]
dmesg - v240
Created attachment 214251 [details]
dmesg - v210
Created attachment 214261 [details]
dmesg - v120
Created attachment 214271 [details]
dmesg - t1-200
Created attachment 214281 [details]
dmesg - t1-105
Created attachment 214291 [details]
lspci - v210
These issues still exist in 4.8 per Meelis: http://lkml.kernel.org/r/alpine.LRH.2.20.1610271756330.32157@math.ut.ee Dmesg snippets from that email: > > 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 Created attachment 243001 [details]
dmesg - t2000
Found similar issue on Sparc T2000 with 4.9-rc2+git. Created an attachment for that too. My logs show that the t2000 issue was there at least in 4.7.0-07753-gc9b95e5. Earlier logs are not available. Created attachment 243431 [details]
dmesg - Dell PE 1650
Another x86 that is showing BAR allocation failure in 4.9.0-rc2-00138-g14970f2 (Dell PowerEdge 1650).
Created attachment 275201 [details]
2018 dmesg of V100
Created attachment 275203 [details]
2018 dmesg Netra X1
Created attachment 275205 [details]
2018 lspci of Netra X1
Created attachment 275207 [details]
2018 lspci of V100
Created attachment 275209 [details]
2018 dmesg of T2000
Created attachment 275211 [details]
2018 lspci of T2000
Created attachment 275213 [details]
2018 dmesg of V245
Created attachment 275215 [details]
2018 lspci of V245
Created attachment 275217 [details]
2018 dmesg of V440
Created attachment 275219 [details]
2018 lspci of V440
Created attachment 275221 [details]
2018 dmesg of V240
Created attachment 275223 [details]
2018 lspci of V240
Created attachment 275225 [details]
2018 dmesg of Netra T1-105
Created attachment 275227 [details]
2018 lspci of Netra T1-105
Created attachment 275229 [details]
2018 dmesg of Netra T1-200
Created attachment 275231 [details]
2018 lspci of Netra T1-200
Created attachment 275233 [details]
2018 dmesg of V120
Created attachment 275235 [details]
2018 lspci of V120
Created attachment 275237 [details]
2018 dmesg of V210
Created attachment 275239 [details]
2018 lspci of V210
Created attachment 275241 [details]
2018 dmesg of Blade 100
Created attachment 275243 [details]
2018 lspci of Blade 100
(In reply to Meelis Roos from comment #13) > Created attachment 275201 [details] > 2018 dmesg of V100 This shows a conflict with the legacy VGA framebuffer at PCI bus addresses 0xa0000-0xbffff: pci_bus 0000:00: root bus resource [mem 0x1ff00000000-0x1ffffffffff] (bus address [0x00000000-0xffffffff]) pci 0000:00:05.0: can't claim BAR 6 [mem 0x1ff00080000-0x1ff000bffff]: address conflict with Video RAM area [??? 0x1ff000a0000-0x1ff000bffff flags 0x80000000] This happens on all the machines here except T2000 and V245. It happens because the sparc arch code unconditionally requests the framebuffer area before we can for PCI devices, and some of those devices might have BARs that overlap the framebuffer area. In this V100 case, attachment 275207 [details] shows that the 00:05.0 expansion ROM is assigned space that overlaps the framebuffer: 00:05.0 21x4x DEC-Tulip compatible 10/100 Ethernet (rev 31) Expansion ROM at 1ff00080000 [disabled] [size=256K] The code paths involved are: pci_fire_pbm_init, schizo_pbm_init, pci_sun4v_pbm_init, psycho_pbm_init_common pci_determine_mem_io_space pci_register_legacy_regions p->start = mem_res->start + 0xa0000 request_resource(mem_res, p) # claim VGA framebuffer pci_scan_one_pbm pci_of_scan_bus # scan DT for PCI devices pci_claim_bus_resources # claim PCI device BARs Created attachment 276101 [details]
Reserve VGA framebuffer only if VGA device is present
This should resolve warnings like this:
pci 0002:00:07.0: can't claim BAR 1 [mem 0x7ff00000000-0x7ff000fffff]: address conflict with Video RAM area [??? 0x7ff000a0000-0x7ff000bffff flags 0x80000000]
which occurred on these systems: V100, Netra X1, V440, V240, Netra T1-105, Netra T1-200, V120, V210, Blade 100
JFYI, sun v215 hardware: $ dmesg | grep BAR [ 5.077808] pci 0000:05:1e.0: can't claim BAR 0 [io 0x7f810000000-0x7f810000fff]: no compatible bridge window # uname -a Linux v215 4.16.0-1-sparc64-smp #1 SMP Debian 4.16.5-1 (2018-04-29) sparc64 GNU/Linux Created attachment 276137 [details] Reserve VGA framebuffer only if VGA device is present (v2) (In reply to Anatoly Pugachev from comment #37) > sun v215 hardware: > > $ dmesg | grep BAR > [ 5.077808] pci 0000:05:1e.0: can't claim BAR 0 [io > 0x7f810000000-0x7f810000fff]: no compatible bridge window > > # uname -a > Linux v215 4.16.0-1-sparc64-smp #1 SMP Debian 4.16.5-1 (2018-04-29) sparc64 > GNU/Linux 4.16 does not contain the proposed fix, so I don't expect any improvement there. If it's convenient, you could test the attached patch (based on v4.17-rc1) and attach the complete dmesg log and "sudo lspci -vv" output. I think it's likely the warning you're seeing will still be there as a result of a conflict with an M7101 device for which a quirk claims some space. Is there something that doesn't work, or is the message itself the only problem? Bjorn, there's nothing in pci-e slots on this machine. But per your last email on sparclinux@ i'm attaching dmesg and lspci output from v215 on kernel 4.18.0-rc2-00169-g90368a37fbbe Created attachment 277071 [details]
v215 lspci short
Created attachment 277073 [details]
v215, dmesg output 4.18.0-rc2
Created attachment 277075 [details]
v215 lspci long, 4.18.0-rc2
Created attachment 277243 [details]
dmesg on T2000 with 4.17.0
Created attachment 277245 [details]
dmesg on V245 with 4.17.0
Created attachment 277247 [details]
dmesg on V245 with 4.18.0-rc2-00169-g90368a3-dirty
-dirty means bpfilter compilation patch, not related to PCI I hope
Created attachment 277249 [details]
dmesg on T2000 with 4.18.0-rc2-00132-gf574943-dirty
-dirty means bpfilter compilation patch, not related to PCI I hope
Created attachment 277339 [details]
dmesg on v215 with 4.18.0-rc3-sparc64-smp (debian kernel)
JFYI booted to latest debian packaged kernel (experimental release), there's no BAR messages in the dmesg on my v215. |