From owner-freebsd-stable@FreeBSD.ORG Thu Feb 12 02:15:47 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 5B125774 for ; Thu, 12 Feb 2015 02:15:47 +0000 (UTC) Received: from udns.ultimatedns.net (unknown [IPv6:2602:d1:b4d6:e600:4261:86ff:fef6:aa2a]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 2A32A7D for ; Thu, 12 Feb 2015 02:15:47 +0000 (UTC) Received: from ultimatedns.net (localhost [127.0.0.1]) by udns.ultimatedns.net (8.14.9/8.14.9) with ESMTP id t1C2FkEn047012; Wed, 11 Feb 2015 18:15:47 -0800 (PST) (envelope-from bsd-lists@bsdforge.com) To: Yonghyeon PYUN In-Reply-To: <20150212014727.GA4152@michelle.fasterthan.com> References: <2ea9dbbfc43fbe632dabf8681323ebc9@ultimatedns.net>, <20150212014727.GA4152@michelle.fasterthan.com> From: "Chris H" Subject: Re: nfe0: watchdog timeout Date: Wed, 11 Feb 2015 18:15:47 -0800 Content-Type: text/plain; charset=UTF-8; format=fixed MIME-Version: 1.0 Message-id: Content-Transfer-Encoding: 8bit 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 02:15:47 -0000 On Thu, 12 Feb 2015 10:47:27 +0900 Yonghyeon PYUN wrote > 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. Good call, and thanks for confirming that. I *knew* it ust have been one, or the other. As it would actually communicate a few packets periodically. So I was left with either IRQ's arbitrarily moving (suspected video) because of the intermittent packet activity. Or simply a need to drain the caps, to force a cold post. Anyway, thanks for taking the time to reply. Greatly appreciated! > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" --Chris --