From owner-freebsd-net@FreeBSD.ORG Tue Jun 11 00:28:56 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 1D0B8215; Tue, 11 Jun 2013 00:28:56 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from mail-pa0-x231.google.com (mail-pa0-x231.google.com [IPv6:2607:f8b0:400e:c03::231]) by mx1.freebsd.org (Postfix) with ESMTP id E0AAD1C7E; Tue, 11 Jun 2013 00:28:55 +0000 (UTC) Received: by mail-pa0-f49.google.com with SMTP id ld11so2049858pab.8 for ; Mon, 10 Jun 2013 17:28:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:date:to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=Lticocb2qNSMIBGi8giouOd8XwHaBcM4oXJKsyCQWGo=; b=HNv5vymutrnJfz9rq9L2VQxItbfMZx8q7j0c8c6OmmDHbWH93vIxmFEP5jRqQ/1cW+ RZeBGi1D42k39MVVkVFjCvK8fbt0+c59cT5nmSp6BlCfbTG4TJ26te/mDewsImeMC1Xh oDKnidiYelAbS2JGdE+dk23AAWE2I9dsmkEeX3htQeEHDXn9bqOXzNh06DTiDOZ6sELd lvVhIu0eg+jY7rhIDrfcdcMnphEt0So/lxKWF/5QnXZo163Wt9U3ufeGjSWGfNYOSnKO Mg4qTQGr903BzyQ0VNJHhI6ylmhjmuH6rZWLjc1zU150Tyinzlfks6KlQ+wkiil6X9Ea awzw== X-Received: by 10.66.169.42 with SMTP id ab10mr11586612pac.14.1370910535697; Mon, 10 Jun 2013 17:28:55 -0700 (PDT) Received: from pyunyh@gmail.com (lpe4.p59-icn.cdngp.net. [114.111.62.249]) by mx.google.com with ESMTPSA id z19sm3122243paf.12.2013.06.10.17.28.51 for (version=TLSv1 cipher=RC4-SHA bits=128/128); Mon, 10 Jun 2013 17:28:54 -0700 (PDT) Received: by pyunyh@gmail.com (sSMTP sendmail emulation); Tue, 11 Jun 2013 09:28:48 +0900 From: YongHyeon PYUN Date: Tue, 11 Jun 2013 09:28:48 +0900 To: "Mr. Clif" Subject: Re: misc/179033: [dc] dc ethernet driver seems to have issues with some multiport card and mother board combinations Message-ID: <20130611002848.GA1519@michelle.cdnetworks.com> References: <201305300113.r4U1DRGp089692@freefall.freebsd.org> <51A6CE52.20501@eugeneweb.com> <20130530051214.GA1530@michelle.cdnetworks.com> <201305300929.31872.jhb@freebsd.org> <51B62547.5000207@eugeneweb.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <51B62547.5000207@eugeneweb.com> User-Agent: Mutt/1.4.2.3i Cc: freebsd-net@freebsd.org, John Baldwin , yongari@freebsd.org X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Jun 2013 00:28:56 -0000 On Mon, Jun 10, 2013 at 12:13:11PM -0700, Mr. Clif wrote: > Hi John and Pyun, > > Ok got the new kernel installed and tested. Yes it works! :-) Maybe that Thanks, probably John can fix PCI-PCI bridge code. > will also fix a simular problem with the sun cards (cas[03]), except I > don't see a define like that in if_cas.c. Suggestions? Cassini does not support I/O port BARs so I guess you're seeing different issue. Would you start a new thread that explains cas(4) issues you're suffering from? > > Thanks, > Clif > > > John Baldwin wrote: > >On Thursday, May 30, 2013 1:12:14 am YongHyeon PYUN wrote: > >>On Wed, May 29, 2013 at 08:58:10PM -0700, Mr. Clif wrote: > >>>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 > >>Ok, I'd like to fix that. > >Hmmm, the dc(4) driver is using the I/O port BARs rather than the > >memory BARs for its registers and this bug seems to be that the dc(4) > >device can't properly access its registers on dc0 and dc1 on the > >Atom box. The one thing I see is that the BIOS on the Atom box assigns > >addresses in the 0x1100-0x11ff range for dc0 and dc1. Those addresses > >conflict with ISA I/O aliases for the 0x100-0x1ff range. The Dell BIOS > >is more careful to avoid these ranges. > > > >I think the fix is that I need to fix the PCI-PCI bridge to reject these > >resource ranges if the ISA enable bit is set in the bridge's control > >register. However, for the time being you can change dc(4) to use the > >memory BAR instead of the I/O port BAR as a workaround: > > > >Index: if_dc.c > >=================================================================== > >--- if_dc.c (revision 251132) > >+++ if_dc.c (working copy) > >@@ -128,7 +128,7 @@ __FBSDID("$FreeBSD$"); > > #include > > #include > > > >-#define DC_USEIOSPACE > >+//#define DC_USEIOSPACE > > > > #include > > > > > >If this fixes it then I can take this PR as a test case for handling the > >ISA > >enable bit in the PCI-PCI bridge code. > > >