From owner-freebsd-net@FreeBSD.ORG Thu May 30 04:07:47 2013 Return-Path: Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id EC664638; Thu, 30 May 2013 04:07:47 +0000 (UTC) (envelope-from clif@eugeneweb.com) Received: from eugeneweb.com (eugeneweb.com [149.20.56.103]) by mx1.freebsd.org (Postfix) with ESMTP id D9B5DAF4; Thu, 30 May 2013 04:07:47 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by eugeneweb.com (Postfix) with ESMTP id 9F3F824C0FA; Wed, 29 May 2013 20:58:13 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at eugeneweb.com Received: from eugeneweb.com ([127.0.0.1]) by localhost (eugeneweb.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id SdzxpyVbGInY; Wed, 29 May 2013 20:58:13 -0700 (PDT) Received: from [192.168.0.1] (unknown [71.193.185.189]) by eugeneweb.com (Postfix) with ESMTP id C395A24C0F9; Wed, 29 May 2013 20:58:12 -0700 (PDT) Message-ID: <51A6CE52.20501@eugeneweb.com> Date: Wed, 29 May 2013 20:58:10 -0700 From: "Mr. Clif" User-Agent: Mozilla/5.0 (X11; Linux i686; rv:10.0.12) Gecko/20130119 Firefox/10.0.11esrpre Iceape/2.7.12 MIME-Version: 1.0 To: yongari@FreeBSD.org Subject: Re: misc/179033: [dc] dc ethernet driver seems to have issues with some multiport card and mother board combinations References: <201305300113.r4U1DRGp089692@freefall.freebsd.org> In-Reply-To: <201305300113.r4U1DRGp089692@freefall.freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@FreeBSD.org X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 May 2013 04:07:48 -0000 Sorry for the confusion Pyun, I started looking at it in the context of pfsense, but they rejected my bug report which was understandable because it's an upstream issue. They suggested I resubmit it to you guys if I could reproduce it. So I booted FreeBSD and lo and behold the same two ports failed in exactly the same way. I didn't see the point in re-running all the tests because I was assuming that FreeBSD would work as well as pfsense for the ports that worked, and there were no further tests I could think of for the dead ports. This Atom board only has serial headers not a DB9 on the back, so I have to look for the proper back panel adapter for that. Otherwise I should be able to set up that test environment. Though it might take me a couple of days, sorry it's crunch time for me on a volunteer project. One which I would like to deploy routers like this on. :-) Thanks, Clif yongari@FreeBSD.org wrote: > Synopsis: [dc] dc ethernet driver seems to have issues with some multiport card and mother board combinations > > State-Changed-From-To: open->feedback > State-Changed-By: yongari > State-Changed-When: Thu May 30 01:11:55 UTC 2013 > State-Changed-Why: > The information you gave looks confusing to me. > If you're using pfSense on Atom D510MO and seeing the issue I'm > afraid I'm not able to help that. pfSense may have some local > changes and I'm not familiar with that. > Did you try stock FreeBSD 9.1-RELEASE on Atom D510MO? > If you still see the same issue with stock FreeBSD 9.1-REELASE, > could you setup remote debugging environment mentioned in the > following URL? > http://people.freebsd.org/~yongari/remote_debugging.txt > > Given that dc(4) works fine with Dell machines I guess the issue > may be in pci(4) which can't correctly handle device sits behind > PCI-PCI bridge. > > Note, Holland Consulting's document does not apply to FreeBSD. > dc(4) can handle multiple instances of dc(4) and should be able to > support dual/quad port dc(4) controllers. > > > Responsible-Changed-From-To: freebsd-net->yongari > Responsible-Changed-By: yongari > Responsible-Changed-When: Thu May 30 01:11:55 UTC 2013 > Responsible-Changed-Why: > Grab. > > http://www.freebsd.org/cgi/query-pr.cgi?pr=179033