Claudio Jeker writes: > On Mon, Oct 28, 2024 at 09:55:53PM +0000, Stuart Henderson wrote: > > On 2024/10/29 00:11, Vitaliy Makkoveev wrote: > > > > - Set up vio(4) interfaces with -tcplro and enable wg(4) interfaces as > > > > usual (In my case, I'm routing IPv4 and IPv6 traffic through wg(4) > > > > tunnel). > > > > > > So, problem lays in vio(4). > > > > Or perhaps that is a trigger but the problem is elsewhere. > > > > bentley@ saw similar wg(4) problems on a machine with just em(4): > > > > em0 at pci0 dev 31 function 6 "Intel I219-V" rev 0x21: msi, address 94:c6:9 > 1:a3:6d:8a > > > > Now, if I looked at the right files, only ix(4) vm(4) vio(4) have LRO - > > em(4) does not. > > > > We do support TSO on some em(4). Though, while I am not certain, I don't > > think we do on I219-V... Anthony, do you still have that machine available? > > Can you do an "ifconfig em hwfeatures" please so we can be sure? > > > > My best guess from the information I have (I don't think it's possible > > to map from a dmesg attach line to a mac_type without more information - > > the pci id isn't printed) is that it's an em_pch_spt which doesn't do > > TSO... > > > > People should try the following diff. It cleans up some of the mbuf > handling and a possible buffer overflow in wg_encap that could be the > cause of the pool corruption.
I'm late, but tested this and got >24 hours uptime (more than I ever got since 7.5) with no crashes in sight. Thanks for committing it.
