Re: Intermittent failure of routing/gateway with ix(4) (x86_64)

From: Kevin Bowling <kevin.bowling_at_kev009.com>
Date: Sun, 24 Aug 2025 05:32:05 UTC
On Sat, Aug 23, 2025 at 6:32 PM R Tyler Croy <rtyler@brokenco.de> wrote:
>
> (replies inline)
>
>
> On Saturday, August 23rd, 2025 at 6:24 PM, Karl Denninger <karl@denninger.net> wrote:
>
> >
>
> > What physical hardware is on that driver?
> >
>
> > I have a box here with two ix interfaces in it that is my edge router and beat the SNOT out of it without problems. This is what the boot messages are for them in my machine here:
>
>
> These are both identical 10GigE NICs, from dmesg
>
> ix0: <Intel(R) X540-AT2> mem 0xe0400000-0xe05fffff,0xe0600000-0xe0603fff irq 18 at device 0.0 on pci1
> ix0: Using 2048 TX descriptors and 2048 RX descriptors
> ix0: Using 2 RX queues 2 TX queues
> ix0: Using MSI-X interrupts with 3 vectors
> ix0: allocated for 2 queues
> ix0: allocated for 2 rx queues
> ix0: Ethernet address: a0:36:9f:38:44:a8
> ix0: PCI Express Bus: Speed 5.0GT/s Width x8
> ix0: fw 4.2.0 nvm 4.03.0 eTrack 0x8000037c
> ix0: netmap queues/slots: TX 2/2048, RX 2/2048

ix is generally regarded as stable as others have stated.  It would be
helpful to see 'sysctl dev.ix' after a stall, and maybe a clean one
prior to it.

On X540 I'd pay some attention to thermals, the PHY generates a real
amount of heat.

>
> System: FreeBSD 14.2-RELEASE-p4
>
> When I was chasing that arpresolve warning I saw in the console, I did see some discussion like this (https://be-virtual.net/pfsense-arpresolve-cant-allocate-llinfo-for-x-x-x-x-on-emx/) about funky routers on the other end of the link causing trouble. Since this is a newer fiber rollout from my local ISP (Sonic) I wouldn't be surprised if there was something funky happening there. Since the LAN-side routing goes haywire, I'm thinking that's a red herring.
>
>
>
> Cheers
>