13-CURRENT on Gigabyte ThunderX system: "pci_host_generic_core_alloc_resource FAIL" and "bgx0: Could not find matching PHY"
Rebecca Cran
rebecca at bluestop.org
Tue Apr 30 05:28:08 UTC 2019
I recently got a Gigabyte ThunderX system. There are some problems
booting FreeBSD 13-CURRENT (from March) on it. I tried booting with both
kern.cfg.order=acpi and kern.cfg.order=fdt . In ACPI mode I saw
complaints that it couldn't find FDT related data, so I guess that's an
unsupported configuration. With kern.cfg.order unset, I see the
following in dmesg:
pci0: <PCI bus> on pcib0
pcib1: <PCI-PCI bridge> at device 1.0 on pci0
pcib0: pci_host_generic_core_alloc_resource FAIL: type=3, rid=32,
start=0000000000000000, end=00000000000fffff, count=0000000000100000,
flags=0
pcib1: failed to allocate initial memory window: 0-0xfffff
pci1: <PCI bus> on pcib1
pci1: <serial bus> at device 0.11 (no driver attached)
pci1: <memory> at device 0.12 (no driver attached)
...
pci1: <memory> at device 0.81 (no driver attached)
bgx0: <ThunderX BGX Ethernet I/O Interface> mem
0x87e0e0000000-0x87e0e03fffff,0x87e0e0400000-0x87e0e07fffff at device
0.128 on pci1
bgx0: Could not find matching PHY
device_attach: bgx0 attach returned 6
bgx0: <ThunderX BGX Ethernet I/O Interface> mem
0x87e0e1000000-0x87e0e13fffff,0x87e0e1400000-0x87e0e17fffff at device
0.129 on pci1
bgx0: Could not find matching PHY
device_attach: bgx0 attach returned 6
pci0: <unknown> at device 9.0 (no driver attached)
xhci0: <Cavium ThunderX USB 3.0 controller> mem
0x868000000000-0x8680001fffff,0x868000200000-0x8680002fffff at device
16.0 on pci0
xhci0: 64 bytes context size, 64-bit DMA
usbus0 on xhci0
xhci1: <Cavium ThunderX USB 3.0 controller> mem
0x869000000000-0x8690001fffff,0x869000200000-0x8690002fffff at device
17.0 on pci0
xhci1: 64 bytes context size, 64-bit DMA
usbus1 on xhci1
pcib2: <PCI-PCI bridge> at device 20.0 on pci0
pcib0: pci_host_generic_core_alloc_resource FAIL: type=3, rid=32,
start=0000000000000000, end=00000000000fffff, count=0000000000100000,
flags=0
pcib2: failed to allocate initial memory window: 0-0xfffff
--
Rebecca Cran
More information about the freebsd-arm
mailing list