8.1-RELEASE em watchdog timeout broken?
cybercorecentre at gmail.com
Fri Aug 6 08:46:53 UTC 2010
Our company had to deal with the same problem
We going to help you for 10k usd.
On Wed, Aug 4, 2010 at 7:19 AM, Jack Vogel <jfvogel at gmail.com> wrote:
> The watchdog is working in all the internal testing that we've done, if
> some corner case here then I need more info to reproduce it. I'm confused
> about what's what, which machine is your desktop and what is the 'other'
> For instance, we had a loud complaint about the watchdog here a while back,
> and it turned out the user had increased the system HZ value to something
> really high... I've yet to see something that indicates the code is broken.
> If it involves Windows then it goes outside the parameters of my testing so
> who knows :)
> On Tue, Aug 3, 2010 at 7:02 PM, Scott Johnson <scottj75074 at yahoo.com> wrote:
>> Under 8.0-RELEASE I would get warnings from em(4) in /var/log/messages
>> "watchdog timeouts" on em0 whenever my desktop PC connected to em0 was
>> off. This was fine, except for the annoying warnings.
>> Under 8.1-RELEASE I no longer get the warnings, and any time my desktop is
>> powered off, when I turn it back on, it has no connectivity. The interface
>> dead until I log into the console and run:
>> # ifconfig em0 down up
>> The em(4) driver has changed a lot since 8.0-RELEASE. It seems this
>> timeout is no longer working.
>> The board is a Supermicro X7SPA-H with Intel 82574L GbE.
>> Any ideas for debugging?
>> freebsd-net at freebsd.org mailing list
>> To unsubscribe, send any mail to "freebsd-net-unsubscribe at freebsd.org"
> freebsd-net at freebsd.org mailing list
> To unsubscribe, send any mail to "freebsd-net-unsubscribe at freebsd.org"
More information about the freebsd-net