From owner-freebsd-amd64@FreeBSD.ORG Tue Jan 11 08:42:43 2011 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E31B2106564A for ; Tue, 11 Jan 2011 08:42:43 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from mail-ww0-f50.google.com (mail-ww0-f50.google.com [74.125.82.50]) by mx1.freebsd.org (Postfix) with ESMTP id 748D58FC08 for ; Tue, 11 Jan 2011 08:42:43 +0000 (UTC) Received: by wwf26 with SMTP id 26so20168099wwf.31 for ; Tue, 11 Jan 2011 00:42:42 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:reply-to :in-reply-to:references:date:message-id:subject:from:to:cc :content-type:content-transfer-encoding; bh=rEtVMPQWPYj2gqQ58G3dWouCkHyvRtRONMX/ot4mxKY=; b=Il7p+UAJ6tnxRBv12QusX6DCnhTFJ31+MQqHsSIA8h4rRJIv8UCU5fvW3wCz3ZursP ouTe1mr//UWPEC57HCqdAWR+uV4wAkAUVXCHio7shGNS8LniQE44Ov+2BBPDouMT4LWj +S/cC2OocNZuNFJp5TYenPte9s6iYAjXNZ7pg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:cc:content-type:content-transfer-encoding; b=WJfKFppgT5U+TaQPpJiH6V0g5DNxZBZcvWp+AqpEdLilk6nhAIu9Jt0vJ6pcu0CdaC GQuwt5YH7rOxL58aB5ezAbs7GpKxi4tTUAjPoWISzba0UDxkH33+sp2xB5eP3ZHFFK2k xuuHFvR2sbYOjevJFgxipIMu4XI+BXXg4Istg= MIME-Version: 1.0 Received: by 10.216.63.81 with SMTP id z59mr27030878wec.91.1294735362247; Tue, 11 Jan 2011 00:42:42 -0800 (PST) Received: by 10.216.254.194 with HTTP; Tue, 11 Jan 2011 00:42:42 -0800 (PST) In-Reply-To: References: Date: Tue, 11 Jan 2011 00:42:42 -0800 Message-ID: From: Pyun YongHyeon To: fbsdmail@dnswatch.com Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-amd64@freebsd.org Subject: Re: tx v2 error 0x6204 - is this a new feature? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Jan 2011 08:42:44 -0000 On Tue, Jan 11, 2011 at 12:28 AM, wrote: > Greetings Pyun YongHyeon, and thank you for your reply. > On Mon, January 10, 2011 11:40 pm, Pyun YongHyeon wrote: >> On Mon, Jan 10, 2011 at 11:10 PM, =A0 wrote: >> >>> Greetings, >>> I have been receiving these messages on a recent 8.1/AMD64 install. >>> src/ports && world/kern about a week ago. Here is a block from the most >>> recent output: nfe0: tx v2 error 0x6204 >>> nfe0: tx v2 error 0x6204 [...] >>> nfe0: tx v2 error 0x6204 >>> >>> >>> It appears to only occur when transmitting largish amounts of data >>> across an NFS mount. I'm not sure where the MIN-threshold lies. But >>> appears to be >=3D1.5Mb. This fresh 8.1/AMD64 is part of a largish serv= er >>> farm comprised of 7+ - 8.0 i386 servers. This one is the only AMD64. It >>> is also the only AMD64. I experience this when mounting an 8.0/i386 >>> server from this 8.1/AMD64. The i386 also has mounts on this 8.1/AMD64. >>> relevant info: ### 8.0/i386 >>> 8.0-STABLE FreeBSD 8.0-STABLE #0: /usr/obj/usr/src/sys/UDNS01 =A0i386 >>> Tyan 2-CPU MB >>> 2 NIC's: fxp0 (only one in use) >>> ### 8.1/AMD64 >>> FreeBSD 8.1-RELEASE-p2 #0: /usr/obj/usr/src/sys/XII amd64 >>> MSI K9N4 Ultra >>> CPU: AMD Athlon(tm) 64 X2 Dual Core Processor 4200+ (3511.34-MHz >>> K8-class >>> CPU) >>> 1 NIC nfe0 >>> ### common to both: >>> rc.conf nfs_client_enable=3D"YES" nfs_reserved_port_only=3D"YES" >>> nfs_server_enable=3D"YES" >>> >>> NIC's on both boards are 10/100's @100mbps >>> >>> >>> Can anyone provide any insight as to why I should be receiving these >>> messages on a fresh 8.1/amd64 install. Is 8.1 INcompatible with earlier >>> versions? >>> >> >> No, I guess you're seeing one of unresolved nfe(4) issues. >> By chance, are you using forced media configuration instead of >> auto-negotiation? Posting both dmesg and "ifconfig nfe0" output would be >> useful. > > As dmesg(8) goes, I have no dmesg.boot on either box, and bouncing them > is not an immediate option. > > ifconfig nfe0 (the 8.1/amd64) follows: > # ifconfig nfe0 > nfe0: flags=3D8843 metric 0 mtu 1= 500 > =A0 =A0 =A0 =A0options=3D8010b > =A0 =A0 =A0 =A0ether 00:19:db:22:74:87 > =A0 =A0 =A0 =A0inet XXX.XXX.XXX.26 netmask 0xffffffe0 broadcast XXX.XXX.X= XX.31 > =A0 =A0 =A0 =A0inet6 fe80::219:dbff:fe22:7487%nfe0 prefixlen 64 scopeid 0= x1 > =A0 =A0 =A0 =A0nd6 options=3D3 > =A0 =A0 =A0 =A0media: Ethernet autoselect (100baseTX ) Does the link partner also agree on the resolved duplex(half-duplex)? It's not common to see half-duplex in these days. Please make sure link partner is also using auto-negotiation. > =A0 =A0 =A0 =A0status: active > > FWIW ifconfig fxp0 on the 8.0/i386 follows: > # ifconfig fxp0 > fxp0: flags=3D8843 metric 0 mtu 1= 500 > =A0 =A0 =A0 =A0options=3D2009 > =A0 =A0 =A0 =A0ether 00:e0:81:20:9d:66 > =A0 =A0 =A0 =A0inet XXX.XXX.XXX.20 netmask 0xffffffe0 broadcast XXX.XXX.X= XX.31 > =A0 =A0 =A0 =A0inet XXX.XXX.XXX.21 netmask 0xffffffff broadcast XXX.XXX.X= XX.21 > =A0 =A0 =A0 =A0inet XXX.XXX.XXX.22 netmask 0xffffffff broadcast XXX.XXX.X= XX.22 > =A0 =A0 =A0 =A0inet XXX.XXX.XXX.23 netmask 0xffffffff broadcast XXX.XXX.X= XX.23 > =A0 =A0 =A0 =A0inet XXX.XXX.XXX.24 netmask 0xffffffff broadcast XXX.XXX.X= XX.24 > =A0 =A0 =A0 =A0inet XXX.XXX.XXX.25 netmask 0xffffffff broadcast XXX.XXX.X= XX.25 > =A0 =A0 =A0 =A0media: Ethernet autoselect (100baseTX) > =A0 =A0 =A0 =A0status: active > > They're all on the same /24, and as you can see, there is no > forced media configuration. > > I /do/ have an old (pre-kern-build) dmesg.boot for the 8.1/amd64, if > you (or anyone else) thinks it would help. If the dmesg.boot is > absolutely required, I'll schedule an opportunity to bounce both of > them - I'll need to know, tho. > Then show me the output of "devinfo -rv" and "pciconf -lcbv". > Thank you again for your thoughtful reply. > > --Chris > > >> >>> Thank you for all your time and consideration. >>> >>> >>> --Chris >>> >> _______________________________________________ >> freebsd-amd64@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 >> To unsubscribe, send any mail to "freebsd-amd64-unsubscribe@freebsd.org" >> >> > > > -- > kern: > FreeBSD 8.1-RELEASE amd64 > > >