From owner-freebsd-stable@FreeBSD.ORG Sat Oct 20 04:10:21 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 0D18316A417 for ; Sat, 20 Oct 2007 04:10:21 +0000 (UTC) (envelope-from pmurray@nevada.net.nz) Received: from bellagio.open2view.net (bellagio.open2view.net [210.48.79.75]) by mx1.freebsd.org (Postfix) with ESMTP id F070413C457 for ; Sat, 20 Oct 2007 04:09:42 +0000 (UTC) (envelope-from pmurray@nevada.net.nz) Received: from [10.0.0.5] (125-237-174-244.jetstream.xtra.co.nz [125.237.174.244]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by bellagio.open2view.net (Postfix) with ESMTP id D158995E68A; Sat, 20 Oct 2007 17:09:40 +1300 (NZDT) Message-Id: From: Philip Murray To: Jeremy Chadwick In-Reply-To: <20071020040347.GA71660@eos.sc1.parodius.com> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v890.2) Date: Sat, 20 Oct 2007 17:09:39 +1300 References: <5CCABF9E-80DD-4E46-80AA-6E3E1F156645@nevada.net.nz> <20071020040347.GA71660@eos.sc1.parodius.com> X-Mailer: Apple Mail (2.890.2) Cc: freebsd-stable@freebsd.org 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: Sat, 20 Oct 2007 04:10:21 -0000 On 20/10/2007, at 5:03 PM, 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 have two 5015M-T+ boxes, one running RELENG_7 and one running > RELENG_6, and neither exhibit this problem. Here's relevant em(4) > information from both boxes; I do find the vmstat -i IRQ on the 2nd > box a little odd, but operationally it seems fine. > > box1 (RELENG_6) > =============== > em0: port > 0x4000-0x401f mem 0xe0200000-0xe021ffff irq 16 at device 0.0 on pci13 > em1: port > 0x5000-0x501f mem 0xe0300000-0xe031ffff irq 17 at device 0.0 on pci14 > > irq16: em0 uhci3 117371806 11 > irq17: em1 49605005 4 > > > box2 (RELENG_7) > =============== > em0: port > 0x4000-0x401f mem 0xe8000000-0xe801ffff irq 16 at device 0.0 on pci13 > em1: port > 0x5000-0x501f mem 0xe8200000-0xe821ffff irq 17 at device 0.0 on pci14 > > irq256: em0 502854 4 > irq257: em1 5438 0 > > > On box2, IRQ 16 is also shared with uhci3 and vgapci0, but vmstat > doesn't seem to show that. > > uhci3: port 0x3060-0x307f irq 16 at > device 29.3 on pci0 > vgapci0: port 0x6000-0x60ff mem > 0xe0000000-0xe7ffffff,0xe8300000-0xe830ffff irq 16 at device 0.0 on > pci15 > Hi Jeremy You don't seem to be running the 6.6.6 driver, which is when the watchdog timeouts started occurring. Had no problems with 6.2.9. Cheers Phil