Date: Sat, 20 Jul 2019 13:08:21 -0400 From: Patrick Kelsey <pkelsey@freebsd.org> To: Andriy Gapon <avg@freebsd.org> Cc: freebsd-net@freebsd.org, FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: vmx0: watchdog timeout on queue 2, no interrupts on BSP Message-ID: <CAD44qMUA_-vT7-374WGZH1bUFCA-sVo_UHi1uQjKkgpk9358bA@mail.gmail.com> In-Reply-To: <9c509f7b-8294-d2fe-ea3e-f10fd51f5736@FreeBSD.org> References: <9c509f7b-8294-d2fe-ea3e-f10fd51f5736@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Jul 19, 2019 at 10:07 AM Andriy Gapon <avg@freebsd.org> wrote: > > Recently we experienced a strange problem. > We noticed a lot of these messages in the logs: > vmx0: watchdog timeout on queue 2 > (always queue 2) > Also, we noticed that connections to some end points did not work at all > while others worked without problems. I assume that that was because > specific flows got assigned to that queue 2. > > Further investigation has shown that none of interrupts assigned to the > BSP has ever fired (since boot, of course). That included vmx0:rx2 and > vmx0:tx2. But also interrupts for other drivers as well. > > Trying to get more information I rebooted the system and the problem > disappeared. > > Has anyone seen anything like that? > Any thoughts on possible causes? > Any suggestions what to check if/when the problem reoccurs? > > Thanks! > > If you are running head at or after r347221 or stable/12 at or after r349112, then this could be due to https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239118 (see Comment 4 - short story is that an iflib change has broken the vmx driver). -Patrick
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAD44qMUA_-vT7-374WGZH1bUFCA-sVo_UHi1uQjKkgpk9358bA>