From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 11:53:35 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 449B71065671 for ; Wed, 2 Apr 2008 11:53:35 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from rn-out-0910.google.com (rn-out-0910.google.com [64.233.170.189]) by mx1.freebsd.org (Postfix) with ESMTP id D77188FC24 for ; Wed, 2 Apr 2008 11:53:34 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by rn-out-0910.google.com with SMTP id s46so1548446rnb.3 for ; Wed, 02 Apr 2008 04:53:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:received:received:date:from:to:cc:subject:message-id:reply-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; bh=oKz1vvY6MlQkeMFqPe01N+0CSWLTmnz8U3jFvLQ+dhE=; b=RWwtuXYJIC+i1oQ2TXeyGuvLmvkyIjhXJ01i3bC4jwIXwywJ1pAR5Gr0gzoSFvT4vHz51G4c338QsrfeW9QhXNJ0tebiheZJTY6PUDbZHLLlin7Xf7UEdsuhSSiCNFH7Ei80yzcdHZFvavUYceEYe8Z3fipILEWBO/IcUnX/ii0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=date:from:to:cc:subject:message-id:reply-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; b=IIGmpvdeyjROS+NlCSZe0RML3ekRXgTwUhKj0WwMgB8ocnBzuGjgqK31nkSuvW6BENbyBFffcf2fQBQJlmEoxOG0Jb4Wl/S7+1UQUp8FZIhOMdGuFItY5k/UIeSlVV5YasUYgDsup7U5wn3veiYyESxy3SWzXroZImdV+y+q7v8= Received: by 10.151.8.8 with SMTP id l8mr4891129ybi.41.1207137213176; Wed, 02 Apr 2008 04:53:33 -0700 (PDT) Received: from michelle.cdnetworks.co.kr ( [211.53.35.84]) by mx.google.com with ESMTPS id g7sm1772652wra.16.2008.04.02.04.53.30 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 02 Apr 2008 04:53:31 -0700 (PDT) Received: from michelle.cdnetworks.co.kr (localhost.cdnetworks.co.kr [127.0.0.1]) by michelle.cdnetworks.co.kr (8.13.5/8.13.5) with ESMTP id m32BrQ19020713 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 2 Apr 2008 20:53:26 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.13.5/8.13.5/Submit) id m32BrPsG020712; Wed, 2 Apr 2008 20:53:25 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Wed, 2 Apr 2008 20:53:25 +0900 From: Pyun YongHyeon To: Stuart Fraser Message-ID: <20080402115325.GD20215@cdnetworks.co.kr> References: <0fc501c893c7$dfbf99b0$9f3ecd10$@net> <20080402002729.GA18494@cdnetworks.co.kr> <483f01c89493$4b8d8b90$e2a8a2b0$@net> <20080402081643.GC18494@cdnetworks.co.kr> <48a901c8949b$d88166e0$898434a0$@net> <20080402085207.GD18494@cdnetworks.co.kr> <48bc01c894b5$39a22c20$ace68460$@net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <48bc01c894b5$39a22c20$ace68460$@net> User-Agent: Mutt/1.4.2.1i Cc: freebsd-current@freebsd.org Subject: Re: vge(4) driver not working at 1G speeds X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Apr 2008 11:53:35 -0000 On Wed, Apr 02, 2008 at 12:32:20PM +0100, Stuart Fraser wrote: > Afraid, that didn't do it. > > The patch files didn't work at first but a did it by hand adding the > relevant lines. It compiled and installed fine. > > So what we see is that things have changed but are not yet working, if not > actually worse. Here are my findings (all using the vge driver compiled into > kernel) > > -first we fail if ifconfig media is set to auto, ifconfig reports media > Ethernet autoselect (none), status: active. No difference if LINK0 set. > > -100BaseTX-FDX appears not to send, if I try to ping any other than the > local IP I 'ping: sendto: No buffer space available'. If I tcpdump on the > interface I see the traffic I would expect on the local subnet. Since vge(4) failed to detect correct link state you just see ENOBUFS. > > -1000BaseTX, still no carrier > This should be fixed in vge(4). > The detailed dmesg snip shows that ip1000phy did connect rather than ukphy > > pcib3: slot 0 INTA hardwired to IRQ 28 > vge0: port 0xe800-0xe8ff mem > 0xfeaffc00-0xfeaffcff irq 28 at device 0 > .0 on pci3 > vge0: Reserved 0x100 bytes for rid 0x14 type 3 at 0xfeaffc00 > miibus0: on vge0 > ip1000phy0: PHY 22 on miibus0 > ip1000phy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, > 1000baseTX-FDX, auto > vge0: using obsoleted if_watchdog interface > vge0: bpf attached > vge0: Ethernet address: 00:40:63:f3:7e:28 > ioapic1: routing intpin 4 (PCI IRQ 28) to vector 49 > vge0: [MPSAFE] > vge0: [ITHREAD] > > > thanks again for the help, what next? > Maybe the next thing is try to fix bugs in vge(4). But I guess it would take very long time as it needs more clean up. I also have a old vge(4) hardware that exhibits the same issue you've seen. I guess I wrote very minimal patch to make it detect link state but can't find it. I'll let you know if I find that old patch in my box. -- Regards, Pyun YongHyeon