From owner-freebsd-current@FreeBSD.ORG  Thu May  6 11:40:05 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 7EA7D16A4CE; Thu,  6 May 2004 11:40:05 -0700 (PDT)
Received: from rms04.rommon.net (rms04.rommon.net [212.54.2.140])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 3305743D49; Thu,  6 May 2004 11:40:04 -0700 (PDT)
	(envelope-from pete@he.iki.fi)
Received: from he.iki.fi (h91.vuokselantie10.fi [193.64.42.145])
	by rms04.rommon.net (8.12.10/8.12.9) with ESMTP id i46Idqmo043698;
	Thu, 6 May 2004 21:39:52 +0300 (EEST)
	(envelope-from pete@he.iki.fi)
Message-ID: <409A8675.3080102@he.iki.fi>
Date: Thu, 06 May 2004 21:39:49 +0300
From: Petri Helenius <pete@he.iki.fi>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.6) Gecko/20040113
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: =?ISO-8859-1?Q?S=F8ren_Schmidt?= <sos@DeepCore.dk>
References: <XFMail.20040505115403.jdp@polstra.com>
	<409938F7.2090603@DeepCore.dk>
In-Reply-To: <409938F7.2090603@DeepCore.dk>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
X-Mailman-Approved-At: Fri, 07 May 2004 10:56:57 -0700
cc: freebsd-net@freebsd.org
cc: freebsd-current@freebsd.org
cc: John Polstra <jdp@polstra.com>
Subject: Re: em(4) problems.
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 06 May 2004 18:40:05 -0000

I´m highly confident that this is a case of integrated "CSA" ethernet 
with broken BIOS. I suspect you get an message about that when booting.

Pete


Søren Schmidt wrote:

> 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
>