Date: Thu, 1 Feb 2018 21:39:18 +0100 From: Rainer Duffner <rainer@ultra-secure.de> To: Matt Joras <mjoras@freebsd.org> Cc: Marius Halden <marius.h@lden.org>, FreeBSD Net <freebsd-net@freebsd.org> Subject: Re: Issues with bxe NIC Message-ID: <8D9EE21E-687F-4F33-B971-D093CFB404ED@ultra-secure.de> In-Reply-To: <CADdTf%2BgDLLr0WBxcxp83a4N1J0S-NLQvGzkft6OqpqrGHcuVcQ@mail.gmail.com> References: <1517494674.4068747.1255940744.6E4465CF@webmail.messagingengine.com> <1517497005.912910.1255997344.7F24E8FC@webmail.messagingengine.com> <CADdTf%2BgDLLr0WBxcxp83a4N1J0S-NLQvGzkft6OqpqrGHcuVcQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> Am 01.02.2018 um 21:21 schrieb Matt Joras <mjoras@freebsd.org>: >=20 > This is one of many issues we have seen with the NetXtreme II device. After I had problems with lagg(4) (well, it just didn=E2=80=99t work at = all), I opened a PR (or I found an existing one) and added to it. I didn=E2=80=99t even really realize it was bxe(4) at first. After a while, I switched to ix(4) and there was no further issue with = the server.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?8D9EE21E-687F-4F33-B971-D093CFB404ED>