Date: Tue, 18 Feb 2025 17:14:06 +0000 From: Andrew Turner <andrew@fubar.geek.nz> To: Shawn Webb <shawn.webb@hardenedbsd.org> Cc: FreeBSD ARM List <freebsd-arm@freebsd.org> Subject: Re: Issues with FreeBSD 15-CURRENT on the ThunderX1 Message-ID: <F4C9BC2E-A13B-4476-866F-5D810C168920@fubar.geek.nz> In-Reply-To: <7lodkufpcjqb44xayx4xug3bfabi6xqqxrj6vchp2yeakkup45@2btxqbvzfeyh> References: <7lodkufpcjqb44xayx4xug3bfabi6xqqxrj6vchp2yeakkup45@2btxqbvzfeyh>
next in thread | previous in thread | raw e-mail | index | archive | help
> On 18 Feb 2025, at 16:43, Shawn Webb <shawn.webb@hardenedbsd.org> = wrote: >=20 > Hey all, >=20 > It appears that probing PCI devices might be busted on FreeBSD > 15-CURRENT snapshot > = FreeBSD-15.0-CURRENT-arm64-aarch64-20250213-6156da866e7d-275409-memstick. >=20 > I have two ThunderX1 servers, both with PCI-connected Intel NICs. They > used to work on FreeBSD/HardenedBSD. I noticed in the boot-up dmesg > output that the kernel couldn't successfully probe the PCI devices. > I've attached /var/run/dmesg.boot and the output of `pciconf -lv`. >=20 > I don't know what exactly is broken, but I suspect the PCI probing > errors are at least symptomatic of the underlying problem. >=20 > I also tried HardenedBSD 15-CURRENT, and experienced the same issue. It looks like the driver is missing ACPI support [1]. You can force FDT = by setting =E2=80=9Ckern.cfg.order=3Dfdt=E2=80=9D in loader. Andrew [1] = https://cgit.freebsd.org/src/tree/sys/dev/vnic/thunder_bgx.c?id=3Dc76c2a19= ae3763d17aa6a60a5831ed24cbc16e83#n1122=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?F4C9BC2E-A13B-4476-866F-5D810C168920>