On 20/07/2019 20:08, Patrick Kelsey wrote: > > > On Fri, Jul 19, 2019 at 10:07 AM Andriy Gapon <a...@freebsd.org > <mailto:a...@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).
I am not sure if that bug could lead to all interrupts on the core getting disabled (for all drivers), and right at the boot time. -- Andriy Gapon _______________________________________________ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
