From owner-freebsd-stable@FreeBSD.ORG Wed Feb 11 20:21:31 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 4EE73D2B for ; Wed, 11 Feb 2015 20:21:31 +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 1554D617 for ; Wed, 11 Feb 2015 20:21:30 +0000 (UTC) Received: from ultimatedns.net (localhost [127.0.0.1]) by udns.ultimatedns.net (8.14.9/8.14.9) with ESMTP id t1BKLULu085513; Wed, 11 Feb 2015 12:21:30 -0800 (PST) (envelope-from bsd-lists@bsdforge.com) To: Brandon Allbery In-Reply-To: References: <126f19356ae6eaf1681262b8ef805dcc@ultimatedns.net>, From: "Chris H" Subject: Re: nfe0: watchdog timeout Date: Wed, 11 Feb 2015 12:21:30 -0800 Content-Type: text/plain; charset=UTF-8; format=fixed MIME-Version: 1.0 Message-id: <2ea9dbbfc43fbe632dabf8681323ebc9@ultimatedns.net> Content-Transfer-Encoding: 8bit Cc: FreeBSD STABLE 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: Wed, 11 Feb 2015 20:21:31 -0000 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. Thanks again, Brandon, for taking the time to respond. > > -- > brandon s allbery kf8nh sine nomine associates > allbery.b@gmail.com ballbery@sinenomine.net > unix, openafs, kerberos, infrastructure, xmonad http://sinenomine.net > _______________________________________________ > 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 --