Re: Issues with FreeBSD 15-CURRENT on the ThunderX1
- In reply to: Andrew Turner : "Re: Issues with FreeBSD 15-CURRENT on the ThunderX1"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Fri, 21 Feb 2025 23:00:44 UTC
On Tue, Feb 18, 2025 at 05:14:06PM +0000, Andrew Turner wrote: > > > On 18 Feb 2025, at 16:43, Shawn Webb <shawn.webb@hardenedbsd.org> wrote: > > > > Hey all, > > > > It appears that probing PCI devices might be busted on FreeBSD > > 15-CURRENT snapshot > > FreeBSD-15.0-CURRENT-arm64-aarch64-20250213-6156da866e7d-275409-memstick. > > > > 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`. > > > > I don't know what exactly is broken, but I suspect the PCI probing > > errors are at least symptomatic of the underlying problem. > > > > 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 “kern.cfg.order=fdt” in loader. > > Andrew > > [1] https://cgit.freebsd.org/src/tree/sys/dev/vnic/thunder_bgx.c?id=c76c2a19ae3763d17aa6a60a5831ed24cbc16e83#n1122 Hey Andrew, Thanks for the response! I've tested out forcing FDT and that seems to make the ThunderX1 happier. Thanks again, -- Shawn Webb Cofounder / Security Engineer HardenedBSD Tor-ified Signal: +1 303-901-1600 / shawn_webb_opsec.50 https://git.hardenedbsd.org/hardenedbsd/pubkeys/-/raw/master/Shawn_Webb/03A4CBEBB82EA5A67D9F3853FF2E67A277F8E1FA.pub.asc