On Wed, 11 Feb 2015 14:39:41 -0500 Brandon Allbery <allbery.b at gmail.com> wrote> On Wed, Feb 11, 2015 at 2:12 PM, Chris H <bsd-lists at bsdforge.com> 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 at gmail.com ballbery at sinenomine.net > unix, openafs, kerberos, infrastructure, xmonad http://sinenomine.net > _______________________________________________ > freebsd-stable at freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe at freebsd.org"--Chris --
On Wed, Feb 11, 2015 at 3:21 PM, Chris H <bsd-lists at bsdforge.com> wrote:> > 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. ;) >That was why the "or etc.". I keep various OSes on USB keys for tests of integrated devices --- if it is throwing fits in FreeBSD and it also does so when I boot from a Linux live key, it's a good bet that there's hardware issues. And yes, fully removing power can also help --- often power coming back on is far from clean (may start with an undervoltage or a series of brief "pulses" of power before coming on for real), and integrated devices often get some amount of power even when the machine is "off". (This was also included in "or etc."; there's a number of "standard" things worth trying when a hardware-related failure follows a power event.) -- brandon s allbery kf8nh sine nomine associates allbery.b at gmail.com ballbery at sinenomine.net unix, openafs, kerberos, infrastructure, xmonad http://sinenomine.net
On Wed, Feb 11, 2015 at 12:21:30PM -0800, Chris H wrote:> On Wed, 11 Feb 2015 14:39:41 -0500 Brandon Allbery <allbery.b at gmail.com> wrote > > > On Wed, Feb 11, 2015 at 2:12 PM, Chris H <bsd-lists at bsdforge.com> 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.