[Bug 268995] Hardware Probe dies on pci_host_generic_core_alloc_resource FAIL
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Tue, 17 Jan 2023 00:26:34 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268995 Bug ID: 268995 Summary: Hardware Probe dies on pci_host_generic_core_alloc_resource FAIL Product: Base System Version: CURRENT Hardware: arm64 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: arm Assignee: freebsd-arm@FreeBSD.org Reporter: daniel@morante.net Created attachment 239519 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=239519&action=edit Failed Boot Log Booting the latest snapshot of 14-CURRENT for aarch64 on my system fails during hardware probe. The system is a Gigbyte R281-T91. Hardware probe dies on the following lines and causes the system to halt: ``` pcib0: <Generic PCI host controller> numa-domain 0 on acpi0 pci0: <PCI bus> numa-domain 0 on pcib0 pcib0: pci_host_generic_core_alloc_resource FAIL: type=3, rid=24, start=4224100042230000, end=422410004223ffff, count=0000000000010000, flags=4040 pcib0: pci_host_generic_core_alloc_resource FAIL: type=3, rid=24, start=4224000042210000, end=422400004221ffff, count=0000000000010000, flags=4040 pcib1: <PCI-PCI bridge> irq 269 at device 1.0 numa-domain 0 on pci0 pci1: <PCI bus> numa-domain 0 on pcib1 pcib2: <PCI-PCI bridge> irq 270 at device 2.0 numa-domain 0 on pci0 pci2: <PCI bus> numa-domain 0 on pcib2 pcib3: <PCI-PCI bridge> irq 271 at device 3.0 numa-domain 0 on pci0 pci3: <PCI bus> numa-domain 0 on pcib3 pcib4: <PCI-PCI bridge> irq 272 at device 4.0 numa-domain 0 on pci0 pci4: <PCI bus> numa-domain 0 on pcib4 pcib5: <PCI-PCI bridge> irq 273 at device 5.0 numa-domain 0 on pci0 pci5: <PCI bus> numa-domain 0 on pcib5 pcib6: <PCI-PCI bridge> irq 274 at device 6.0 numa-domain 0 on pci0 pci6: <PCI bus> numa-domain 0 on pcib6 pcib7: <PCI-PCI bridge> at device 7.0 numa-domain 0 on pci0 pci7: <PCI bus> numa-domain 0 on pcib7 pci7: <network, ethernet> at device 0.0 (no driver attached) pci7: <network, ethernet> at device 0.1 (no driver attached) pcib8: <PCI-PCI bridge> irq 275 at device 8.0 numa-domain 0 on pci0 pci8: <PCI bus> numa-domain 0 on pcib8 pcib9: <PCI-PCI bridge> irq 276 at device 9.0 numa-domain 0 on pci0 pci9: <PCI bus> numa-domain 0 on pcib9 pcib10: <PCI-PCI bridge> irq 277 at device 10.0 numa-domain 0 on pci0 pci10: <PCI bus> numa-domain 0 on pcib10 pcib11: <PCI-PCI bridge> at device 11.0 numa-domain 0 on pci0 pci11: <PCI bus> numa-domain 0 on pcib11 pci11: <network, ethernet> at device 0.0 (no driver attached) pci11: <network, ethernet> at device 0.1 (no driver attached) pcib12: <PCI-PCI bridge> at device 12.0 numa-domain 0 on pci0 pcib0: pci_host_generic_core_alloc_resource FAIL: type=3, rid=32, start=0000000040000000, end=00000000420fffff, count=0000000002100000, flags=0 pcib12: failed to allocate initial memory window: 0x40000000-0x420fffff ``` Full boot log is attached as `14-CURRENT-bd93b5f79ab4.log`. The breaking commit is: https://cgit.freebsd.org/src/commit/?id=bd93b5f79ab489fb0ed6ab25d6be48242eb8c028 Commits prior to that do not result in the described behavior. Prior to the commit the hardware probe would display the following: ``` ahci0: <AHCI SATA controller> mem 0x42220000-0x4222ffff at device 16.0 numa-domain 0 on pci0 pcib0: Failed to translate resource 0-ffffffffffffffff type 3 for ahci0 ahci0: 0x10000 bytes of rid 0x18 res 3 failed (0, 0xffffffffffffffff). device_attach: ahci0 attach returned 6 ahci0: <AHCI SATA controller> mem 0x42200000-0x4220ffff at device 16.1 numa-domain 0 on pci0 pcib0: Failed to translate resource 0-ffffffffffffffff type 3 for ahci0 ahci0: 0x10000 bytes of rid 0x18 res 3 failed (0, 0xffffffffffffffff). device_attach: ahci0 attach returned 6 ``` A full log of a successful boot is also attached as `14-CURRENT-818cae0ff752.log` -- You are receiving this mail because: You are the assignee for the bug.