From owner-freebsd-stable@FreeBSD.ORG Wed Jan 17 19:16:35 2007 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A257616A4C2 for ; Wed, 17 Jan 2007 19:16:35 +0000 (UTC) (envelope-from mandrews@bit0.com) Received: from mindcrime.bit0.com (bit0.com [207.246.88.211]) by mx1.freebsd.org (Postfix) with ESMTP id 6338B13C4A7 for ; Wed, 17 Jan 2007 19:16:35 +0000 (UTC) (envelope-from mandrews@bit0.com) Received: from [172.27.0.11] (nat.bit0.com [207.246.88.210]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mindcrime.bit0.com (Postfix) with ESMTP id 3C6DA730002; Wed, 17 Jan 2007 14:16:34 -0500 (EST) Message-ID: <45AE76D0.1050300@bit0.com> Date: Wed, 17 Jan 2007 14:19:44 -0500 From: Mike Andrews User-Agent: Thunderbird 1.5.0.9 (Windows/20061207) MIME-Version: 1.0 To: Jack Vogel References: <20070116123019.I46509@bit0.com> <2a41acea0701161053s67c6100cqf03284626116f04c@mail.gmail.com> In-Reply-To: <2a41acea0701161053s67c6100cqf03284626116f04c@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: 6.2-RELEASE em0 watchdog timeouts -- sometimes (w/ partial workaround) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 17 Jan 2007 19:16:35 -0000 Jack Vogel wrote: > On 1/16/07, Mike Andrews 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!