From owner-freebsd-stable@FreeBSD.ORG Thu Feb 12 01:47:39 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 08C261A6 for ; Thu, 12 Feb 2015 01:47:39 +0000 (UTC) Received: from mail-pd0-f181.google.com (mail-pd0-f181.google.com [209.85.192.181]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id CDBFDD70 for ; Thu, 12 Feb 2015 01:47:38 +0000 (UTC) Received: by pdno5 with SMTP id o5so8350072pdn.8 for ; Wed, 11 Feb 2015 17:47:37 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:date:to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=EbvlSj+srQWT+pDy7aJx3boOC2q7qruwgvrDz4MAsdw=; b=YPB9azvyf/BoYJYIwNq/iX3nDIR6xSzvtnbg0rz5PlV9KVwBiR+uUzDm71QheAI1Hb 3mFROKD8I6lovB0Op/57oRQbmctXkL/lRIiOIn2uzoBp6Aa3GnOliBeltpOJ/lx7/nkh X8505zWP9akMpX7WFVQ+Ryws9fdSYJBq3fzuD/fhX5r6+g+fsb2DIP/0p792l2O9IGgV JP+e0/bgZ/eYUC1UtMKWfU9nFB7U54FP/C2ARlTrVafaamboq7yrpKwYLcdVE6OOOuTk E82hoPY1T8wKF6a/PVFvh79zbBEZzCUrO8uDB1hBMN+v+bKHvMuUGzDVml9lTauZi72Y +giQ== X-Received: by 10.68.69.108 with SMTP id d12mr2045828pbu.137.1423705657614; Wed, 11 Feb 2015 17:47:37 -0800 (PST) Received: from pyunyh@gmail.com ([106.247.248.2]) by mx.google.com with ESMTPSA id j16sm1973896pdm.90.2015.02.11.17.47.33 (version=TLSv1 cipher=RC4-SHA bits=128/128); Wed, 11 Feb 2015 17:47:36 -0800 (PST) From: Yonghyeon PYUN X-Google-Original-From: "Yonghyeon PYUN" Received: by pyunyh@gmail.com (sSMTP sendmail emulation); Thu, 12 Feb 2015 10:47:27 +0900 Date: Thu, 12 Feb 2015 10:47:27 +0900 To: Chris H Subject: Re: nfe0: watchdog timeout Message-ID: <20150212014727.GA4152@michelle.fasterthan.com> Reply-To: pyunyh@gmail.com References: <2ea9dbbfc43fbe632dabf8681323ebc9@ultimatedns.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2ea9dbbfc43fbe632dabf8681323ebc9@ultimatedns.net> User-Agent: Mutt/1.4.2.3i Cc: FreeBSD STABLE , Brandon Allbery X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Feb 2015 01:47:39 -0000 On Wed, Feb 11, 2015 at 12:21:30PM -0800, Chris H wrote: > On Wed, 11 Feb 2015 14:39:41 -0500 Brandon Allbery wrote > > > On Wed, Feb 11, 2015 at 2:12 PM, Chris H wrote: > > > > > Had a power outage at home last night. > > > I fsck'd the disks, and after bring it back up, I was > > > without network, and the: > > > nfe0: watchdog timeout > > > just keeps repeating. > > > > > > > Seeing that after a power outage, I'd be testing the NIC in another machine > > or etc. > Thanks for the reply, Brandon. > That's a no op. It's an onboard NIC. So unless I get out > the exacto knife, or de-solder it. It's not going to happen. ;) > > On the up-side. I pulled the power from the PSU, and pulled > a PCI NIC of the shelf, and shoved into a spare slot. My > intention was to force IRQ reassignment, in case the (onboard) > NIC was forced into sharing an IRQ for some strange reason. > Anyway, plugged in the power cord, and booted the box, and > *viola* the nfe0 NIC was back online. Don't know whether it > was completely removing the power, the additional NIC, or > both. But in the end; all is good. > Due to lack of publicly available documentation, nfe(4) heavily relies on power-on default H/W configurations(e.g. PHY or power saving related thing). Some of those register configurations are sticky so they shall survive from power cycling. The vendor surely knows the correct sequence to reprogram those registers but the required information is not available to open source driver writers. Cold-boot will always perform full H/W initialization and it will put the controller into known good state. So it's good idea to unplug power cord and wait tens of seconds before boot when you encounter power lost or unexpected watchdog timeouts.