Date: Thu, 04 Apr 2019 10:38:06 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 237010] mlx5 with LACP can stop work with vlanhwfilter enabled Message-ID: <bug-237010-227@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D237010 Bug ID: 237010 Summary: mlx5 with LACP can stop work with vlanhwfilter enabled Product: Base System Version: 12.0-STABLE Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: bugs@FreeBSD.org Reporter: ae@FreeBSD.org We have faced this problem several times, but it is not easy to reproduce. We use several mce(4) cards in one or two LACP lagg(4). The system is mostly router with firewall. Each lagg(4) has several vlans. vlanhwfilter is enabl= ed by default. Each IRQ is bound to dedicated CPU core, but each mce* interface shares CPU cores with each other. The number of queues is limited to 26, the last two are dedicated to user processes. The problem can occur when management software does some network reconfiguration, i.e. creates new vlan interfaces or destroys some old. Looks like the system stops receiving any packets. If we turn off vlanhwfil= ter via ipmi console, it starts work again. At the moment when problem occurs, = the network loading is about 500-800kpps.=20 It seems this can not be reproduced with single card, i.e. without LACP lag= g. We already saw this problem in 11-CURRENT, 12-CURRENT, 12-STABLE. But since= our configuration is very specific with patches to driver, this report is mostly JFYI. For now we just disable vlanhwfilter by default. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-237010-227>