interface down, console output: igb3: TX(7) desc avail = 41, pidx = 308

[Kevin Bowling]

Sean Bruno committed a couple fixes to the watchdog code this week that
should at least allow for a usable TSO although the frequency of the
watchdog events is still cause for concern.  It seems some timeouts are
part of Intel's expectations during normal operations for several chipsets.

If you could share which exact NIC chipset you have I will check the
datasheets and see if we're missing anything.

Regards,

On Sat, Apr 1, 2017 at 6:41 PM, Ben Woods <woodsb02 at gmail.com> wrote:

> On 27 March 2017 at 15:35, Kevin Bowling <kevin.bowling at kev009.com> wrote:
>
>> Try turning TSO off.. i.e. ifconfig igb3 -tso or sysctl net.inet.tcp.tso=0
>>
>> The transition to iflib has exposed much jankiness in the Intel "shared
>> code" of the e1000 drivers.  In particular, the locking contracts may not
>> align with FreeBSD locking primitives.  I have boxes running the legacy
>> driver that are clearly reliant on the watchdog reset for steady state
>> which is unacceptable.  We are actively looking into this at LLNW, but
>> additional reports and help are appreciated.
>>
>
>
> Hi Kevin,
>
> Thanks for the reply. Sorry it took so long for me to get back to you, I
> first had to wait for the problem to be repeated.
>
> Indeed, running "ifconfig igb3 -tso" did fix the issue. It didn't seem to
> the first time, but I may have been too quick to judge. After re-enabling
> TSO and disabling it a second time, the problem stopped, and the interface
> immediately came up.
>
> Please let me know if there is anything I can do to try and help diagnose
> this. In the mean time, I have added net.inet.tcp.tso=0 to my
> /etc/sysctl.conf, so I don't think this will re-occur unless I remove it.
>
> Regards,
> Ben
>
> --
> From: Benjamin Woods
> woodsb02 at gmail.com
>