Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 17 Jan 2007 14:19:44 -0500
From:      Mike Andrews <mandrews@bit0.com>
To:        Jack Vogel <jfvogel@gmail.com>
Cc:        freebsd-stable@freebsd.org
Subject:   Re: 6.2-RELEASE em0 watchdog timeouts -- sometimes (w/ partial   workaround)
Message-ID:  <45AE76D0.1050300@bit0.com>
In-Reply-To: <2a41acea0701161053s67c6100cqf03284626116f04c@mail.gmail.com>
References:  <20070116123019.I46509@bit0.com> <2a41acea0701161053s67c6100cqf03284626116f04c@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
Jack Vogel wrote:

> On 1/16/07, Mike Andrews <mandrews@bit0.com> wrote:
>> I have a strange issue with em0 watchdog timeouts that I think is not the
>> same as the ones everyone was having during the 6.2 beta cycle...
>>
>> I have six systems, each with two Intel GigE ports onboard:
>>
>> Systems A and B: Supermicro PDSMi+
>> Systems C and D: Supermicro PDSMi (without the plus)
 >>[snip]
>> Several times a day, em0 will go down, give a watchdog timeout error on
>> the console, then come right back up on its own a few seconds later.  But
>> here's the weird twist: it ONLY happens on systems A and B, and ONLY when
>> running at gigabit speed.  If I knock the two switch ports down to 100
>> meg, the problem goes away.
[snip]
> There are some management related issues with this NIC, first if you
> have not done so make a DOS bootable device, and run this app I
> am enclosing, it fixes the prom setting that is wrong on some devices.
> It will do no harm, and it may solve things.
> 
> Let me know if it does fix it please.


No problems since running that tool almost 24 hours ago.  Looks like a 
fix.  Thanks again!


-- 
Mike Andrews  *  mandrews@bit0.com  *  http://www.bit0.com
It's not news, it's Fark.com.                  Carpe cavy!



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?45AE76D0.1050300>