From owner-freebsd-stable@FreeBSD.ORG  Sat Oct 20 04:03:47 2007
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
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 82CB216A418
	for <freebsd-stable@freebsd.org>; Sat, 20 Oct 2007 04:03:47 +0000 (UTC)
	(envelope-from jdc@parodius.com)
Received: from mx01.sc1.parodius.com (mx01.sc1.parodius.com [72.20.106.3])
	by mx1.freebsd.org (Postfix) with ESMTP id 5F34013C467
	for <freebsd-stable@freebsd.org>; Sat, 20 Oct 2007 04:03:47 +0000 (UTC)
	(envelope-from jdc@parodius.com)
Received: by mx01.sc1.parodius.com (Postfix, from userid 1000)
	id 23BE21CC02E; Fri, 19 Oct 2007 21:03:47 -0700 (PDT)
Date: Fri, 19 Oct 2007 21:03:47 -0700
From: Jeremy Chadwick <koitsu@FreeBSD.org>
To: Philip Murray <pmurray@nevada.net.nz>
Message-ID: <20071020040347.GA71660@eos.sc1.parodius.com>
Mail-Followup-To: Philip Murray <pmurray@nevada.net.nz>,
	Goran Lowkrantz <goran.lowkrantz@ismobile.com>,
	freebsd-stable@freebsd.org
References: <DF00B541F0F46F5A6BE2414E@viglaf>
	<5CCABF9E-80DD-4E46-80AA-6E3E1F156645@nevada.net.nz>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <5CCABF9E-80DD-4E46-80AA-6E3E1F156645@nevada.net.nz>
User-Agent: Mutt/1.5.16 (2007-06-09)
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 <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, 
	<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 20 Oct 2007 04:03:47 -0000

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: <Intel(R) PRO/1000 Network Connection Version - 6.2.9> port 0x4000-0x401f mem 0xe0200000-0xe021ffff irq 16 at device 0.0 on pci13
em1: <Intel(R) PRO/1000 Network Connection Version - 6.2.9> 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: <Intel(R) PRO/1000 Network Connection Version - 6.5.3> port 0x4000-0x401f mem 0xe8000000-0xe801ffff irq 16 at device 0.0 on pci13
em1: <Intel(R) PRO/1000 Network Connection Version - 6.5.3> 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: <UHCI (generic) USB controller> port 0x3060-0x307f irq 16 at device 29.3 on pci0
vgapci0: <VGA-compatible display> port 0x6000-0x60ff mem 0xe0000000-0xe7ffffff,0xe8300000-0xe830ffff irq 16 at device 0.0 on pci15

-- 
| Jeremy Chadwick                                    jdc at parodius.com |
| Parodius Networking                           http://www.parodius.com/ |
| UNIX Systems Administrator                      Mountain View, CA, USA |
| Making life hard for others since 1977.                  PGP: 4BD6C0CB |