From owner-freebsd-stable@FreeBSD.ORG  Thu May 29 17:09:14 2008
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 D7B7E1065679
	for <freebsd-stable@freebsd.org>; Thu, 29 May 2008 17:09:14 +0000 (UTC)
	(envelope-from dimitry@andric.com)
Received: from tensor.andric.com (cl-327.ede-01.nl.sixxs.net
	[IPv6:2001:7b8:2ff:146::2])
	by mx1.freebsd.org (Postfix) with ESMTP id 80ACA8FC0C
	for <freebsd-stable@freebsd.org>; Thu, 29 May 2008 17:09:14 +0000 (UTC)
	(envelope-from dimitry@andric.com)
Received: from [IPv6:2001:7b8:3a7:0:19dc:ae3d:fbec:8ec] (unknown
	[IPv6:2001:7b8:3a7:0:19dc:ae3d:fbec:8ec])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by tensor.andric.com (Postfix) with ESMTPSA id 6BD713C;
	Thu, 29 May 2008 19:09:13 +0200 (CEST)
Message-ID: <483EE338.9080609@andric.com>
Date: Thu, 29 May 2008 19:09:12 +0200
From: Dimitry Andric <dimitry@andric.com>
User-Agent: Thunderbird 2.0.0.15pre (Windows/20080517)
MIME-Version: 1.0
To: =?ISO-8859-1?Q?Gerrit_K=FChn?= <gerrit@pmp.uni-hannover.de>
References: <20080527165232.2acbb00f.gerrit@pmp.uni-hannover.de>	<20080528002823.GA63696@cdnetworks.co.kr>	<20080528175610.0ffe4c1c.gerrit@pmp.uni-hannover.de>	<20080529115825.2da70cba.gerrit@pmp.uni-hannover.de>	<483E8F38.6070109@andric.com>
	<20080529171351.a3dd5111.gerrit@pmp.uni-hannover.de>
In-Reply-To: <20080529171351.a3dd5111.gerrit@pmp.uni-hannover.de>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: pyunyh@gmail.com, freebsd-stable@freebsd.org
Subject: Re: broken re(4)
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: Thu, 29 May 2008 17:09:14 -0000

On 2008-05-29 17:13, Gerrit K=FChn wrote:
> On Thu, 29 May 2008 13:10:48 +0200 Dimitry Andric <dimitry@andric.com>
> Meanwhile I have set up two more machines. Now I have 5 ITX systems, ea=
ch
> with 2 re-NICs, and only one is behaving strange.

Just as a data point, my ITX board is a JetWay J7F4K1G2E.=20

=2E..
re0: <RealTek 8169SC/8110SC Single-chip Gigabit Ethernet> port 0xf000-0xf=
0ff mem 0xfdfff000-0xfdfff0ff irq 18 at device 9.0 on pci0
re0: Chip rev. 0x18000000
re0: MAC rev. 0x00000000
miibus0: <MII bus> on re0
rgephy0: <RTL8169S/8110S/8211B media interface> PHY 1 on miibus0
rgephy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000=
baseT-FDX, auto
re0: Ethernet address: 00:30:18:a6:f1:a8
re0: [FILTER]
re1: <RealTek 8169SC/8110SC Single-chip Gigabit Ethernet> port 0xf200-0xf=
2ff mem 0xfdffe000-0xfdffe0ff irq 19 at device 11.0 on pci0
re1: Chip rev. 0x18000000
re1: MAC rev. 0x00000000
miibus1: <MII bus> on re1
rgephy1: <RTL8169S/8110S/8211B media interface> PHY 1 on miibus1
rgephy1:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000=
baseT-FDX, auto
re1: Ethernet address: 00:30:18:a6:f1:a9
re1: [FILTER]
atapci0: <VIA 6420 SATA150 controller> port 0xff00-0xff07,0xfe00-0xfe03,0=
xfd00-0xfd07,0xfc00-0xfc03,0xfb00-0xfb0f,0xf400-0xf4ff irq 20 at device 1=
5.0 on pci0
atapci0: [ITHREAD]

As you can see, re0 is on irq 18, re1 on irq 19 and the SATA controller
on irq 20, so no conflicts there.

It also seems to work okay with this latest patch.



> The only hardware thing
> that is different in this system from the others is an additional
> SATA-controller. Can there be conflicts with this card which are
> triggering the problems?

I'd just suspect a bad board instead...