From owner-freebsd-net@FreeBSD.ORG Sat Nov 13 07:09:21 2010 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A1388106566B for ; Sat, 13 Nov 2010 07:09:21 +0000 (UTC) (envelope-from zeus@relay.ibs.dn.ua) Received: from relay.ibs.dn.ua (relay.ibs.dn.ua [91.216.196.25]) by mx1.freebsd.org (Postfix) with ESMTP id 1AB208FC08 for ; Sat, 13 Nov 2010 07:09:20 +0000 (UTC) Received: from relay.ibs.dn.ua (localhost [127.0.0.1]) by relay.ibs.dn.ua with ESMTP id oAD79Ik9061291; Sat, 13 Nov 2010 09:09:18 +0200 (EET) Received: (from zeus@localhost) by relay.ibs.dn.ua (8.14.4/8.14.4/Submit) id oAD79Iwr061290; Sat, 13 Nov 2010 09:09:18 +0200 (EET) Date: Sat, 13 Nov 2010 09:09:18 +0200 From: Zeus V Panchenko To: Pyun YongHyeon Message-ID: <20101113070918.GB15278@relay.ibs.dn.ua> References: <20101112070759.GA36248@relay.ibs.dn.ua> <20101112230000.GD22460@michelle.cdnetworks.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20101112230000.GD22460@michelle.cdnetworks.com> User-Agent: Mutt/1.4.2.3i X-Operating-System: FreeBSD 8.1-RELEASE X-Editor: GNU Emacs 23.2.1 Cc: freebsd-net@freebsd.org Subject: Re: Problem with re0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: zeus@ibs.dn.ua List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Nov 2010 07:09:21 -0000 Pyun YongHyeon (pyunyh@gmail.com) [10.11.13 01:01] wrote: > > Please be more specific for the issue. Your description is hard to > narrow down possible cause. > > > i was sure it is the problem of the onboard rt nics ... > > > > pciconf output of all re(4) controllers are useless because the > vendor uses the same device id. Please show me the output of dmesg > which will contain necessary information to identify your > controller revision. > oh, sorry :( here is what you say: the integrated onboard nic: re0: port 0xe800-0xe8ff mem 0xfafff000-0xfaffffff,0xfaff8000-0xfaffbfff irq 17 at device 0.0 on pci2 re0: Using 1 MSI messages re0: Chip rev. 0x28000000 re0: MAC rev. 0x00000000 miibus0: on re0 rgephy0: PHY 1 on miibus0 rgephy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto re0: Ethernet address: 48:5b:39:d2:1d:89 re0: [FILTER] external PCI nic: re1: port 0xd800-0xd8ff mem 0xfbeffc00-0xfbeffcff irq 17 at device 0.0 on pci1 re1: Chip rev. 0x10000000 re1: MAC rev. 0x00000000 miibus1: on re1 rgephy1: PHY 1 on miibus1 rgephy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto re1: Ethernet address: 00:21:91:f4:5f:e4 re1: [FILTER] all that data i was posting here before (several months ago) and nothing changed since that time due to production state of the boxes i was forced finally to switch to external nics and to configure it with vlans and even to unplug the cable of the onboard nic since nic with plugged cable but without assigned ip address did begin flap (may be it's specific of the swith it plugged in, it is TP-Link TL-SG5426 but no other nic behaves this way) i have 7 boxes of this configuration and all 6 are running now on external nics if i can provide any debug/info/e.t.c. please let me know, i'd be happy it'd work at last :) -- Zeus V. Panchenko IT Dpt., IBS ltd GMT+2 (EET)