From owner-freebsd-stable@FreeBSD.ORG Wed Jan 17 02:50:14 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 29CD916A416 for ; Wed, 17 Jan 2007 02:50:14 +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 C2F3013C44B for ; Wed, 17 Jan 2007 02:50:13 +0000 (UTC) (envelope-from mandrews@bit0.com) Received: from [172.27.1.254] (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 B0D03730002; Tue, 16 Jan 2007 21:50:10 -0500 (EST) Message-ID: <45AD8E86.3020906@bit0.com> Date: Tue, 16 Jan 2007 21:48:38 -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 02:50:14 -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. So far it seems like it DID fix it, but give me another day or two to watch it to be sure. Thanks! FYI, it only changed the PROM on the first NIC on each PDSMi+ box; it said the second NIC was fine. (But since the first NIC was the one I was having trouble with...) I ran it on the older PDSMi boxes and it said it changed both NICs on those, even though they were (and still are) working fine. -- Mike Andrews * mandrews@bit0.com * http://www.bit0.com It's not news, it's Fark.com. Carpe cavy!