From owner-freebsd-net@FreeBSD.ORG Wed Apr 18 21:56:57 2012 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D7E0E106564A for ; Wed, 18 Apr 2012 21:56:57 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: from mail-we0-f182.google.com (mail-we0-f182.google.com [74.125.82.182]) by mx1.freebsd.org (Postfix) with ESMTP id 606618FC14 for ; Wed, 18 Apr 2012 21:56:57 +0000 (UTC) Received: by wern13 with SMTP id n13so6611471wer.13 for ; Wed, 18 Apr 2012 14:56:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=+0hcAoxrg0rdOECnnjHYCDjdMveZ7gZ4HVdg4LKW0ZI=; b=WPElrhwgsuJPKeJ0PnRiB0RJ5vu0kqoaJ8ipNciNYlasUrn+jfT6LBm6CtlexXFtwq Y2meqkQ942vxxPTE4hUEj/8IuC6Wdu1OAQX8cVPBdjV8oEInZ8RepIfC1nAl+siTCTcR O1Q0HY+JFKeHQNzy1tliBjf7Vhc/2+OkuNTcmlsXkSu77v0Fg8mQ2Fy9qRwplpxe/PeX 2bls5FZwU1P0DsRckAFDl9G6ozuUL6Rm7OWF0A6VvJLHNWbenC5efK0D7udepHMR8kBt V9kD0QsbSxyMfQHH8vLlZN9Sb+3lrHlynpAbwXC39QbWwY56XH7hqGncwcLcsFvLfri0 O+kA== MIME-Version: 1.0 Received: by 10.216.134.155 with SMTP id s27mr2705253wei.80.1334786215519; Wed, 18 Apr 2012 14:56:55 -0700 (PDT) Received: by 10.180.3.170 with HTTP; Wed, 18 Apr 2012 14:56:55 -0700 (PDT) In-Reply-To: <8ol369-4nf.ln1@lwilke.de> References: <8ol369-4nf.ln1@lwilke.de> Date: Wed, 18 Apr 2012 14:56:55 -0700 Message-ID: From: Jack Vogel To: Lars Wilke Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-net@freebsd.org Subject: Re: Watchdog timeout em driver 8.2-R X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Apr 2012 21:56:57 -0000 On Wed, Apr 18, 2012 at 1:45 PM, Lars Wilke wrote: > Hi Jack, > > thanks for your response. > > * Jack Vogel wrote: > > On Wed, Apr 18, 2012 at 7:01 AM, Lars Wilke wrote: > > > Apr 13 08:53:07 san02 kernel: em1: Watchdog timeout -- resetting > > > Apr 13 08:53:07 san02 kernel: em1: Queue(0) tdh = 232, hw tdt = 190 > > > Apr 13 08:53:07 san02 kernel: em1: TX(0) desc avail = 31,Next TX to > > > Clean = 221 > > > Apr 13 08:53:07 san02 kernel: em1: Link is Down > > > Apr 13 08:53:07 san02 kernel: em1: link state changed to DOWN > > > > > > Sometimes nothing for days, sometimes under high Network load (NFSv3), > > > sometimes > > > multiple times a day. I see this message/behaviour on always the same > two > > > of the > > > four interfaces (em1 and em3). > > > > > > Then the NIC does not have the ACTIVE flag anymore, an ifconfig em1 up > > > solves the issue. But why does it loose the ACTIVE state and why does > the > > > NIC reset itself in the first place? > > > > > > > Because a watchdog reset is just that, a reset, so it causes the > hardware to > > reinitialize. It should come back up, I do not know why it did not, > maybe > > the renegotiation with the switch fails for some reason? > > Hm, my main problem is that it did a reset in the first place. > > > One thought is to get the latest em driver and see if the behavior > changes, > > if that driver is the distributed 8.2 its pretty old. > > ok then i guess i will upgrade to 8.3-R, is the driver there reasonably > new? > > Yes, that should be fine. Jack