From owner-freebsd-stable@FreeBSD.ORG Sun Oct 21 15:17:55 2007 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 72B8116A41A for ; Sun, 21 Oct 2007 15:17:55 +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 AD45613C49D for ; Sun, 21 Oct 2007 15:17:22 +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 1FA301E3357; Sun, 21 Oct 2007 00:10:53 -0400 (EDT) Message-ID: <471AD144.60404@bit0.com> Date: Sun, 21 Oct 2007 00:10:44 -0400 From: Mike Andrews User-Agent: Thunderbird 2.0.0.6 (Windows/20070728) MIME-Version: 1.0 To: Philip Murray , Goran Lowkrantz , freebsd-stable@freebsd.org References: <5CCABF9E-80DD-4E46-80AA-6E3E1F156645@nevada.net.nz> <20071020040347.GA71660@eos.sc1.parodius.com> In-Reply-To: <20071020040347.GA71660@eos.sc1.parodius.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Re: em 6.6.6 - watchdog timeout 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: Sun, 21 Oct 2007 15:17:55 -0000 Jeremy Chadwick wrote: > On Sat, Oct 20, 2007 at 11:21:10AM +1300, Philip Murray wrote: >> "me too" on a Supermicro 5015MT+, although I notice my em0 is also sharing >> an interrupt with USB (uhci3)... not sure if that's the culprit. > > I'm not aware of a 5015MT+ model. Maybe you mean 5015M-MT+ or > 5015M-T+? We've got five 5015M-MT+'s in production. The PDSMI+ motherboard has two 82573's, one of which has a known EEPROM issue that Jack Vogel has sent a DOS-based utility around to fix up (search the archives for dcgdis.exe). It fixed watchdog timeouts I was having way back in the 6.2 beta cycle -- in my case they only happened when I had link at 1G and went away if I dropped to 100M. It might be worth ruling that out first unless you've already done that. :) I haven't tried the 6.6.6 driver on mine yet, though, so this could be something totally different. I was going to bump one of them from RELENG_6 to RELENG_7 as a test soon.