New Version 2.4.4 - Interface Error --> aq_add_macvlan err -53, aq_error 14

Juve

A quick FollowUP running 1.11.20 :

9 days uptime
no error so far.
throuhput is good, no issue
we added 6 new vlan in the last 9 Days and everything works as expected for the moment.
we did test multiple master/slave failover/failback, no issues

I'll continue to keep you informed.

JeGr

@stephenw10 said in New Version 2.4.4 - Interface Error --> aq_add_macvlan err -53, aq_error 14:

Please add that info to the bug report if you have confirmed it.
https://redmine.pfsense.org/issues/9123

Steve

@Juve could you add those intel to the ticket, Stephen mentioned?
It would provide additional help/info.

also @stephenw10 if that driver release seems to solve the problem, how are chances that it be included in a 2.4.5 release? As we're currently having information from two customers they are seeing similar problems (one with "no response - dead" pfsense when adding VLANs, one having a reboot with queue and VLAN errors shown), that would be a great thing.

best regards

stephenw10

If it's in 11 stable it would likely make it into a 2.4.X release. The drivers in 12 look to be significantly different, I'm not sure that could be brought back.

Steve

Juve

I did update the ticket :-)

Juve

Quick update:
50 days uptime, no error so far.
Looks like the driver was the issue.

JeGr

@Juve said in New Version 2.4.4 - Interface Error --> aq_add_macvlan err -53, aq_error 14:

Quick update:
50 days uptime, no error so far.
Looks like the driver was the issue.

What were the latest changes you were running? Latest driver as you wrote (1.11.20) and HWVLANTSO removal?

If so, any chance @stephenw10 to bring that driver version into the mix for the upcoming 2.4.5?

Juve

It is still super stable.

The only two things we did at the end are:

use the latest driver
use failover LAGG and not LACP lagg (but we did not test LACP with latest driver so we can't confirm is is not working with it)

no VLANTSO removal etc.

stephenw10

Is anyone still seeing this with the 1.11.9 driver in 2.4.5?

Steve

DarkMasta

@stephenw10
with 2.4.5 no error (LACP LAGG, 15 VLANs)

stephenw10

Ah, good. We were trying to replicate it in 2.4.5 and have not done so.

If anyone is seeing it though please let us know the steps required.

Steve

fsir

@stephenw10

Hi, I think I can reproduce this problem with pfSense version 2.4.5-RELEASE-p1 (amd64) and native driver 1.11.9-k.

We have ~45 vlans on one of the interfaces, adding a new vlan on this interface leads to impossibility to ping / reach the system on any of the sub-interfaces related.
Console prompts "queue appears hung" messages, reboot seems to be the only solution to get the system working again (new vlan included).
I did set net.inet.tcp.tso = 0 via Advanced / System tunables : the messages don't show anymore, but still the same problem (system unreachable when adding vlan, reboot needed).

Tested on X710 and X722 Intel NICs, Supermicro server.

I will test upgrading the Intel driver and/or VLANTSO removal, keep you informed.
Don't hesitate to ask if I can provide more info.
Have a nice day,
Fabien

stephenw10

Are you seeing the error messages:

Interface Error --> aq_add_macvlan err -53, aq_error 14

Or just the 'queue appears hung' logs?

Steve

fsir

@stephenw10 Hi !
Just the 'queue appears hung' and server unreachable on the interface.
Fabien