From owner-freebsd-net@FreeBSD.ORG Tue Jan 11 07:40:35 2011 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 08F661065670 for ; Tue, 11 Jan 2011 07:40:35 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from mail-wy0-f182.google.com (mail-wy0-f182.google.com [74.125.82.182]) by mx1.freebsd.org (Postfix) with ESMTP id 6C8A88FC0A for ; Tue, 11 Jan 2011 07:40:34 +0000 (UTC) Received: by wyf19 with SMTP id 19so20591476wyf.13 for ; Mon, 10 Jan 2011 23:40:33 -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=dGmhYF7sHxvygItOliX5sKJXiqqbJrNeTByxmCTa+NM=; b=MyEpCotl8SgMI5nNvmA2BaW2l2HgxloZpLiWIGyFPFNlk8r9x4+YK6dx97NGkdLJwL eVkbSj5bLLs4g13uu1lYiMMj4KYs2wDLm2Mn9DDwDhiUH/cDnhG1JLy9IjPfRiF3RlAV TVndMokxMMFDiCe8tACrRB9EQz0Vj+xtyZEs8= 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=VLAHAmaIFNaBOPTjqXyd6IUgcPmpLqmUYRTE7+P95yCZXizYr/t4FU6+hqeGXzOaj2 Cx3NHoCP0nuG8QIbtkm6oii29XfQ6TuoogoeESQBEGvW1CYDNAb6aMInRtCi/XUQW7zI UgmdohUjDylqyfqg1ei4HTO5Qj0meTwig2IVo= MIME-Version: 1.0 Received: by 10.216.180.77 with SMTP id i55mr4108387wem.76.1294731633281; Mon, 10 Jan 2011 23:40:33 -0800 (PST) Received: by 10.216.254.194 with HTTP; Mon, 10 Jan 2011 23:40:33 -0800 (PST) In-Reply-To: References: Date: Mon, 10 Jan 2011 23:40:33 -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-net@freebsd.org, freebsd-amd64@freebsd.org Subject: Re: tx v2 error 0x6204 - is this a new feature? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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 Jan 2011 07:40:35 -0000 On Mon, Jan 10, 2011 at 11:10 PM, wrote: > Greetings, > =A0I 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 > nfe0: tx v2 error 0x6204 > nfe0: tx v2 error 0x6204 > nfe0: tx v2 error 0x6204 > nfe0: tx v2 error 0x6204 > nfe0: tx v2 error 0x6204 > nfe0: tx v2 error 0x6204 > nfe0: tx v2 error 0x6204 > nfe0: tx v2 error 0x6204 > nfe0: tx v2 error 0x6204 > nfe0: tx v2 error 0x6204 > nfe0: tx v2 error 0x6204 > nfe0: tx v2 error 0x6204 > nfe0: tx v2 error 0x6204 > nfe0: tx v2 error 0x6204 > nfe0: tx v2 error 0x6204 > nfe0: tx v2 error 0x6204 > nfe0: tx v2 error 0x6204 > nfe0: tx v2 error 0x6204 > nfe0: tx v2 error 0x6204 > nfe0: tx v2 error 0x6204 > nfe0: tx v2 error 0x6204 > nfe0: tx v2 error 0x6204 > nfe0: tx v2 error 0x6204 > nfe0: tx v2 error 0x6204 > nfe0: tx v2 error 0x6204 > nfe0: tx v2 error 0x6204 > nfe0: tx v2 error 0x6204 > nfe0: tx v2 error 0x6204 > nfe0: tx v2 error 0x6204 > nfe0: tx v2 error 0x6204 > nfe0: tx v2 error 0x6204 > nfe0: tx v2 error 0x6204 > nfe0: tx v2 error 0x6204 > nfe0: tx v2 error 0x6204 > nfe0: tx v2 error 0x6204 > nfe0: tx v2 error 0x6204 > nfe0: tx v2 error 0x6204 > nfe0: tx v2 error 0x6204 > nfe0: tx v2 error 0x6204 > nfe0: tx v2 error 0x6204 > nfe0: tx v2 error 0x6204 > nfe0: tx v2 error 0x6204 > nfe0: tx v2 error 0x6204 > nfe0: tx v2 error 0x6204 > nfe0: tx v2 error 0x6204 > nfe0: tx v2 error 0x6204 > nfe0: tx v2 error 0x6204 > nfe0: tx v2 error 0x6204 > nfe0: tx v2 error 0x6204 > nfe0: tx v2 error 0x6204 > nfe0: tx v2 error 0x6204 > nfe0: tx v2 error 0x6204 > nfe0: tx v2 error 0x6204 > nfe0: tx v2 error 0x6204 > nfe0: tx v2 error 0x6204 > nfe0: tx v2 error 0x6204 > nfe0: tx v2 error 0x6204 > nfe0: tx v2 error 0x6204 > nfe0: tx v2 error 0x6204 > nfe0: tx v2 error 0x6204 > nfe0: tx v2 error 0x6204 > nfe0: tx v2 error 0x6204 > nfe0: tx v2 error 0x6204 > nfe0: tx v2 error 0x6204 > nfe0: tx v2 error 0x6204 > nfe0: tx v2 error 0x6204 > 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 server 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. > Thank you for all your time and consideration. > > --Chris