Date: Tue, 1 Feb 2022 15:35:56 -0800 From: Pete Wright <pete@nomadlogic.org> To: questions@freebsd.org Subject: Re: ena0: Cannot get hash function - after upgrade to 12.3 Message-ID: <ea3c173f-14e4-8641-979f-03176c4bf8d3@nomadlogic.org> In-Reply-To: <44E45176-8AE5-46E0-BE2E-E20F70D35C1F@msqr.us>
index | next in thread | previous in thread | raw e-mail
On 2/1/22 14:30, Matt Magoffin wrote: > Hello, > > I recently upgraded some EC2 instances from 12.2-RELEASE to 12.3-RELEASE and now the kernel log has several hundred log messages each day like this: > > ena0: Cannot get hash function > > The system seems to be running OK, and networking is working AFAIK, but I wondered if I could fix/suppress those messages. I could not find references to this message via online searches, but I do see it in the source: > > https://github.com/freebsd/freebsd-src/blob/8a5b4859c7fcefac7db611ef38450ef0a66d68a8/sys/dev/ena/ena_sysctl.c#L761-L764 > > I see there is mention of a dev.ena.X.rss.key sysctl that I wondered if was relevant: > > https://github.com/freebsd/freebsd-src/blob/8a5b4859c7fcefac7db611ef38450ef0a66d68a8/sys/dev/ena/ena_sysctl.c#L455-L458 The man page for ena(4) defines these errors as: "Error occurred during initialization of one of RSS resources. The device will work with reduced performance because all RX packets will be passed to queue 0 and there will be no hash information" Unfortunately it does not provide additional information for debugging purposes. I'm actually upgrading some EC2 systems now from 12.2 to 12.3 - I'll update this thread if I can reproduce on my end. -pete -- Pete Wright pete@nomadlogic.org @nomadlogicLAhelp
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ea3c173f-14e4-8641-979f-03176c4bf8d3>
