From owner-freebsd-net@FreeBSD.ORG  Wed May  5 11:57:05 2004
Return-Path: <owner-freebsd-net@FreeBSD.ORG>
Delivered-To: freebsd-net@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 013AA16A4CE; Wed,  5 May 2004 11:57:05 -0700 (PDT)
Received: from spider.deepcore.dk
	(cpe.atm2-0-53484.0x50a6c9a6.abnxx9.customer.tele.dk [80.166.201.166])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 17AA643D54; Wed,  5 May 2004 11:57:03 -0700 (PDT)
	(envelope-from sos@DeepCore.dk)
Received: from DeepCore.dk (sos.deepcore.dk [194.192.25.130])
	by spider.deepcore.dk (8.12.11/8.12.10) with ESMTP id i45Iutw6049977;
	Wed, 5 May 2004 20:57:00 +0200 (CEST)
	(envelope-from sos@DeepCore.dk)
Message-ID: <409938F7.2090603@DeepCore.dk>
Date: Wed, 05 May 2004 20:56:55 +0200
From: =?ISO-8859-1?Q?S=F8ren_Schmidt?= <sos@DeepCore.dk>
User-Agent: Mozilla Thunderbird 0.5 (X11/20040329)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: John Polstra <jdp@polstra.com>
References: <XFMail.20040505115403.jdp@polstra.com>
In-Reply-To: <XFMail.20040505115403.jdp@polstra.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
X-mail-scanned: by DeepCore Virus & Spam killer v1.4
cc: freebsd-net@freebsd.org
cc: freebsd-current@freebsd.org
Subject: Re: em(4) problems.
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 05 May 2004 18:57:05 -0000

John Polstra wrote:
> On 05-May-2004 Søren Schmidt wrote:
> 
>>For what its worth I have problems with one em based interface as well, 
>>it locks the machine solid when used:
>>
>>em0: <Intel(R) PRO/1000 Network Connection, Version - 1.7.25> port 
>>0xb000-0xb01f mem 0xfb100000-0xfb11ffff irq 10 at device 1.0 on pci1
>>em0: Reserved 0x20000 bytes for rid 0x10 type 3 at 0xfb100000
>>em0: Reserved 0x20 bytes for rid 0x18 type 4 at 0xb000
>>em0: [GIANT-LOCKED]
>>em0: Ethernet address: 00:30:48:80:9f:b6
>>
>>where this one works just fine:
>>
>>em1: <Intel(R) PRO/1000 Network Connection, Version - 1.7.25> port 
>>0xa800-0xa83f mem 0xfa000000-0xfa01ffff irq 19 at device 10.0 on pci3
>>em1: Reserved 0x20000 bytes for rid 0x10 type 3 at 0xfa000000
>>em1: Reserved 0x40 bytes for rid 0x18 type 4 at 0xa800
>>em1: [GIANT-LOCKED]
>>em1: Ethernet address: 00:30:48:80:9f:b7
>>
>>
>>The chips are these
>>em0@pci1:1:0:   class=0x020000 card=0x10758086 chip=0x10758086 rev=0x00 
>>hdr=0x00
>>em1@pci3:10:0:  class=0x020000 card=0x10768086 chip=0x10768086 rev=0x00 
>>hdr=0x00
> 
> 
> Are either of the IRQs (10 and 19) shared with other devices?

Yes, the working one is shared with an (unused) USB port

-- 
-Søren