Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 05 Oct 2015 19:10:25 +0200
From:      "Frank de Bot (lists)" <lists@searchy.net>
To:        Jack Vogel <jfvogel@gmail.com>
Cc:        FreeBSD Stable <freebsd-stable@freebsd.org>
Subject:   Re: em0 and em1 watchdog timed out
Message-ID:  <5612AF01.1040806@searchy.net>
In-Reply-To: <56117BD8.10806@searchy.net>
References:  <560EC0C6.409@searchy.net> <CAFOYbcknVEKzdcncifnUzUpkPeMkfQ%2ByJ4EnTY%2BWORSh4OAhaQ@mail.gmail.com> <56117BD8.10806@searchy.net>

next in thread | previous in thread | raw e-mail | index | archive | help
The connection is fine when working without lagg/lacp. As soon I
configure it, on load it the network devices will have watchdog
timeouts. The switch I use is a HP 1810-24G, PL.1.9

One of the other threads mentioned he used an other router (/switch) and
problems didn't occur anymore.

Unfortunately  I don't  have an other switch lying around to test with.


Frank


Frank de Bot (lists) wrote:
> FreeBSD 10.2 r286666 . The drivers is Intel(R) PRO/1000 Network
> Connection 7.4.2 I will start some tests without lagg configured.
> 
> 
> Regards,
> 
> Frank de Bot
> 
> 
> Jack Vogel wrote:
>> You missed the all-important details: OS version, driver version.
>> And another question I can think of, do these interfaces watchdog if they
>> are not configured with lagg?
>>
>> Cheers,
>>
>> Jack
>>
>>
>> On Fri, Oct 2, 2015 at 10:37 AM, Frank de Bot (lists) <lists@searchy.net>
>> wrote:
>>
>>> On a server I have 2 interfaces configured in a lagg. It seemed to be
>>> running stable until now (about a week), both interfaces repeatable go
>>> down after a watchdog timeout.
>>>
>>> Output from /var/log/messages
>>>
>>> Oct  2 10:15:11 nas kernel: em0: Watchdog timeout Queue[0]-- resetting
>>> Oct  2 10:15:11 nas kernel: Interface is RUNNING and ACTIVE
>>> Oct  2 10:15:11 nas kernel: em0: TX Queue 0 ------
>>> Oct  2 10:15:11 nas kernel: em0: hw tdh = 804, hw tdt = 905
>>> Oct  2 10:15:11 nas kernel: em0: Tx Queue Status = -2147483648
>>> Oct  2 10:15:11 nas kernel: em0: TX descriptors avail = 915
>>> Oct  2 10:15:11 nas kernel: em0: Tx Descriptors avail failure = 0
>>> Oct  2 10:15:11 nas kernel: em0: RX Queue 0 ------
>>> Oct  2 10:15:11 nas kernel: em0: hw rdh = 912, hw rdt = 911
>>> Oct  2 10:15:11 nas kernel: em0: RX discarded packets = 0
>>> Oct  2 10:15:11 nas kernel: em0: RX Next to Check = 912
>>> Oct  2 10:15:11 nas kernel: em0: RX Next to Refresh = 911
>>> Oct  2 10:15:11 nas kernel: em0: link state changed to DOWN
>>> Oct  2 10:15:13 nas kernel: em0: link state changed to UP
>>> Oct  2 10:15:13 nas devd: Executing '/etc/rc.d/dhclient quietstart em0'
>>> Oct  2 10:21:56 nas kernel: em1: Interface stopped DISTRIBUTING,
>>> possible flapping
>>> Oct  2 10:21:59 nas kernel: em1: Watchdog timeout Queue[0]-- resetting
>>> Oct  2 10:21:59 nas kernel: Interface is RUNNING and ACTIVE
>>> Oct  2 10:21:59 nas kernel: em1: TX Queue 0 ------
>>> Oct  2 10:21:59 nas kernel: em1: hw tdh = 686, hw tdt = 806
>>> Oct  2 10:21:59 nas kernel: em1: Tx Queue Status = -2147483648
>>> Oct  2 10:21:59 nas kernel: em1: TX descriptors avail = 896
>>> Oct  2 10:21:59 nas kernel: em1: Tx Descriptors avail failure = 0
>>> Oct  2 10:21:59 nas kernel: em1: RX Queue 0 ------
>>> Oct  2 10:21:59 nas kernel: em1: hw rdh = 167, hw rdt = 166
>>> Oct  2 10:21:59 nas kernel: em1: RX discarded packets = 0
>>> Oct  2 10:21:59 nas kernel: em1: RX Next to Check = 167
>>> Oct  2 10:21:59 nas kernel: em1: RX Next to Refresh = 166
>>> Oct  2 10:21:59 nas kernel: em1: link state changed to DOWN
>>> Oct  2 10:22:02 nas kernel: em1: link state changed to UP
>>> Oct  2 10:22:02 nas devd: Executing '/etc/rc.d/dhclient quietstart em1'
>>>
>>> it seems to occur when the interface are loaded. On the same server I
>>> also have a PCI card, the same issue occurs here. em0 and em1 are both
>>> onboard 80003ES2LAN. the PCI card is 82571EB.
>>>
>>> I've found different threads, but I couldn't manage to find  a fix for
>>> this.
>>>
>>> What else can be wrong?
>>>
>>> Regards,
>>>
>>> Frank de Bot
>>> _______________________________________________
>>> freebsd-stable@freebsd.org mailing list
>>> https://lists.freebsd.org/mailman/listinfo/freebsd-stable
>>> To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"
>>>
>> _______________________________________________
>> freebsd-stable@freebsd.org mailing list
>> https://lists.freebsd.org/mailman/listinfo/freebsd-stable
>> To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"
>>
> 
> _______________________________________________
> freebsd-stable@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"
> 




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5612AF01.1040806>